Hi, hoping someone with more experience might have a quick win on this. We recently had big issues with one of our 2003 exchange servers which resulted in a lot of mounting and unmounting of the mailstores, server restarts and other admin actions. The server came back but has been running pretty slow and overloaded since. The real problem we have though is with a remote c# app running on an automation server that runs a mailbox scrape to detect emails and move them. To do this it logs into OWA using a default account. However, since the reboot this job now times out whenever it runs (with a generic: System.Net.WebException: The operation has timed out at System.Net.HttpWebRequest.GetResponse().) If I browse to the exchange URL the app is targeting and log in manually, it takes a very long time to get any response from the server (pretty sure this is where the app timeout and user time out must differ). Once I have connected manually on the machine, the automated job will successfully do the scrape and make the move. I have tried IIS resets on both boxes and have verified that there's nothing funky going on with the permissioning and it all looks good. So my questions are: - Does anybody know if OWA gets in a funny state post reboots/mail store actions? (as far as I'm aware it was mounting/unmounting/defragging/re-initialising and more, but not 100% what was done unfortunately) - if so, is there an OWA "restart/cycle" procedure I could follow? Any feedback would be most appreciated! Thanks,

As far as OWA concer, it shouldn't get affected when you dismount and mount the store. Reseting OWA virtual directory means recreating the directory. http://support.microsoft.com/kb/883380 I guess you should open up this thread with Developers team also, they might be able to help on that application. http://social.technet.microsoft.com/Forums/en-US/exchangesvrdevelopment/threads Gulab | MCITP: Exchange 2010-2007 | Skype: Gulab.Mallah | Blog: www.ExchangeRanger.Blogspot.com

What page is it when it takes long time to get the response? The certificate warning page? The time zone region page or any other? What app do you mean? What edition Exchange server do you use? Does the OWA response slow if you logon via IE with your credentials? To fast troubleshoot this issue, I’d suggest you verify the IIS log to see if there is any clue on the issue you are encountering. Hope it is helpful. Fiona

Thanks for the feedback guys To pad this out a little more: we are running Exchange 2003 v 6.5.7638.1 the time-outs occur even when you attempt to log in via IE/other browsers, not just the app it's a connection to the root of a team inbox the app is in-house, it is just an email scraper that uses WebDav once one connection is made to teh inbox,..it seems to cache and further connections from other clients are quick It seems to be an IIS caching thing, I've seen some info on IIS worker processes reloading so am looking into that, will check the IIS logs now.

Ok, I think this is resolved now, I figured I'd retry another iisreset for giggles, this unfortunately messed up the OWA royally which was then giving me 503 Service Unavailable errors. To resolve this, we: stopped the Microsoft Exchange Information Store ran another iisrest restarted the information store, then IMAP4 service, then POP4 verified all the mailbox stores where remounted This got OWA back and,..as a plus point, it resolved the timeouts/super slow connection, it's back to being fast again. Prior to doing this, we looked into the HTTP traffic around the OWA sessions, it seemed to be hanging up on the initial Authentication. Obviously taking all mail stores offline is not a great solution to this problem, so if anyone knows why this may have fixed it, would be great to know a lower impact resolution for future reference. Thanks for the help, will re-post if the timeouts come back.

Ok, I think this is resolved now, I figured I'd retry another iisreset for giggles, this unfortunately messed up the OWA royally which was then giving me 503 Service Unavailable errors. To resolve this, we: stopped the Microsoft Exchange Information Store ran another iisrest restarted the information store, then IMAP4 service, then POP4 restart SMTP service verified all the mailbox stores were remounted This got OWA back and,..as a plus point, it resolved the timeouts/super slow connection, it's back to being fast again. Prior to doing this, we looked into the HTTP traffic around the OWA sessions, it seemed to be hanging up on the initial Authentication. Obviously taking all mail stores offline is not a great solution to this problem, so if anyone knows why this may have fixed it, would be great to know a lower impact resolution for future reference. Thanks for the help, will re-post if the timeouts come back.