Need advice please on how to check OWA problems with a third-partymessage archiving system.

A

Alan

Hello,

Need some advice please on OWA performance problems with a third-party
message archiving system in Exchange 2003.

The archiving system has both a plug-in for Outlook and also an add-on
for OWA (which creates virtual directories in IIS). The Outlook
component works fine, message retrieval is fast. However, in OWA, it
takes a long time for some or all archived messages to open, depending
whether you're using a front-end or back-end server.

Using OWA on the FE, it always takes 30 seconds to open an archived
message.

Using OWA on the BE, the first time that you open an archived message,
it takes about 30 seconds. After that, archived messages open within a
few seconds. But that only lasts a while; after a couple of hours of
inactivity, the first message takes a long time to open again and the
cycle repeats.

The archiving system has its own server with its own web interface to
the archive and archived messges there always only take a few seconds
to open. The FE and BE are on the same internal network, no IIS server
or firewalls involved, using HTTP only, no SSL.

Could it be a problem with the authentication settings? I'd be
grateful if anyone can suggest what else to look for.

Unfortunately, the vendors haven't found any obvious problems yet...

Thanks,

- Alan.
 
M

Mark Arnold [MVP]

On Tue, 11 Aug 2009 00:11:47 -0700 (PDT), Alan <bruguy@gmail.com>
wrote:

>Hello,
>
>Need some advice please on OWA performance problems with a third-party
>message archiving system in Exchange 2003.
>
>The archiving system has both a plug-in for Outlook and also an add-on
>for OWA (which creates virtual directories in IIS). The Outlook
>component works fine, message retrieval is fast. However, in OWA, it
>takes a long time for some or all archived messages to open, depending
>whether you're using a front-end or back-end server.
>
>Using OWA on the FE, it always takes 30 seconds to open an archived
>message.
>
>Using OWA on the BE, the first time that you open an archived message,
>it takes about 30 seconds. After that, archived messages open within a
>few seconds. But that only lasts a while; after a couple of hours of
>inactivity, the first message takes a long time to open again and the
>cycle repeats.
>
>The archiving system has its own server with its own web interface to
>the archive and archived messges there always only take a few seconds
>to open. The FE and BE are on the same internal network, no IIS server
>or firewalls involved, using HTTP only, no SSL.
>
>Could it be a problem with the authentication settings? I'd be
>grateful if anyone can suggest what else to look for.
>
>Unfortunately, the vendors haven't found any obvious problems yet...
>
>Thanks,
>
>- Alan.


I suggest you keep on top of the vendor about this. Have them check
your topology for authentication issues.
 

Top