Open Archive Via OWA 2010 Working very slow

[Ronen_Tzimbel]

Hello,

We have Enterprise Vault 9 sp2 ,2 Mailbox Server with CAS\HUB (Exchange 2010)

when The customer install Service Pack 2 to Exchange server

it`s  take a lot of time to open archive  Via OWA 2010

what can I do to resolve the issues ?

Thx

Ronen

[JesusWept3]

Ok so are you talking about archive explorer or opening items from a shortcut? Has it ever been fast or has it always been slow? If you open up archive explorer and retrieve items, is it faster then?? Are the CAS servers on the same network as the EV servers or are they remote? Are there any EV related errors in either the CAS servers event logs or the EV servers event logs? Really I think would need a DTrace of ShoppingService and w3wp on the EV server and an OWA trace set in the web.config for a particular user or two

[Ronen_Tzimbel]

I`m talking about opening items from shortcut.

before the customer upgrade to sp2 it`s working fine (it`s take 3-7 sec to open item) now it`s take 10-15Sec

the cas server and Ev Server stay in same Network

we dont have any error in event log.

thx

[JesusWept3 · Accepted solution]

Ok you're going to have to get logs from the CAS server and a DTrace from the EV server Find a user that has the issue and then edit the OWA web.config files to enable logging for that user on the CAS server Then find the EV server that hosts the users vault store, and on that EV server start a DTrace of w3wp and ShoppingService and the reproduce the issue by going directly to the CAS server you enabled logging on If you have a load balancer for the CAS servers such as mail.mycompany.com that redirects to one of several CAS servers, if you go to http://mail.mycompany.com you may end up on a CAS server where logging isn't enabled So enable logging on say CASServer1.mycompany.com and then go to https://casserver1.mycompany.com Also if you don't DTrace on the correct EV server, the you won't see the requests for that user come in So from the log files you'd then want to look on OWA and look at the time the request to retrieve an item was made and then the time that it took to come back Then on the DTrace side of things you'd look at the same kind of things, looking to see if there are any large deltas between the request and the completion, for instance it could be asking for a GC server and taking 6 seconds to get an answer back etc Also like i said you need to check archive explorer and seeig whether retrieving items is any faster So if you try and open items in AE and it still takes ten seconds then youre looking at purely an EV issue And when testing the OWA retrievals do not use the same items to test with as they are hidden in the deleted items so the first time you open may take ten seconds, but if you open it again it will see its already in deleted items and will open that one instead so it will appear that it's far quicker So make sure to use new items So to recap 1. Check retrieval speeds through AE, is it slow? If so, concentrate on EV 2. Enable logging for a specific user through the OWA web.config file 3. Enable dtracing for w3wp and ShoppingService on the users EV server 4. Reproduce the issue going directly to the CAS server and using different items for each test 5. In the traces look for big gaps in time (deltas) and any 0x800 and 0xC00 errors

[Chris_Warren]

To tag onto JW2's suggestions, I would include Dtracing AuthServer as well (#3). Alot of times I see retrieval delays due to how long it takes for EV to trawl through the AD permissions of the user to confirm it has rights to the archive. Large numbers of AD groups associated with the user, or nested groups can slow this down.

Granted, this is most likely not the case, since the change was on the Exchange server, but you never know.

Hope this helps.

[Prone2Typos]

Did you fix this? If so can you please share how and mark it as solved?