none
The server operation timed out. Please try again later

    Question

  • Just this week we have started to get the following error when trying to open e-mails on OWA.

    The server oepration timed out. Please try again later

    Here is a screenshot: http://i52.tinypic.com/2mc8saa.jpg

    In addition this, OWA will occassionaly freeze when checking the spelling.

    So far we have about 5 or 6 reported cases of this but I would like to try and get it fixed before it becomes more of a problem.

    I have increased the diagnostic logging properities of MSExchange OWA\Core and MSExchange OWA\Configuration to Expert level but there is nothing ovbious appearing in the event logs.

    We are running Exchange 2010 SP1 UR2 on Windows Server 2008 R2 Enterprise.  The clients are all Windows XP SP3 using IE 8 as the browser.

    Does anybody have any ideas what might be causing this?

    Cheers

    Adam.

    • Edited by adamf83 Tuesday, March 08, 2011 12:48 PM
    Tuesday, March 01, 2011 12:24 PM

Answers

  • To solve this issue we had to get staff using our internal OWA url.  Since doing this there has been no more occurances of the error.
    • Marked as answer by adamf83 Sunday, April 03, 2011 10:54 AM
    Sunday, April 03, 2011 10:53 AM

All replies

  • Did you take a look through your IIS logs to see if you can locate the HTTP request and perhaps an HTTP status code that generated this error? If you can get an HTTP status code, then I would set up a IIS trace log to generate a debug log when this occurs again.


    James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com
    Tuesday, March 01, 2011 4:41 PM
  • The log file I am looking at has a mixture of status codes (all captured today) including:

    200, 206, 301, 302, 304, 400, 401, 401.1, 401.2, 403.4, 404, 440, 500, 500.19

    Which would be generated during a server timeout?

    How do I setup an IIS trace log?

    Cheers

    Adam.

    Tuesday, March 01, 2011 7:01 PM
  • Hi adamf83,

    Do you have a CAS Array?

    Please check whether the issue will be occured both in Internal or External connection.

    Please run the Exbpa in the Toolbox.

    If possible, please reset the OWA VD using EMC:

    Server Configuration->Client Access->Actions->Reset Virtual Directory.

    Please also temp disable the Anti-Virus software to test.

    Frank Wang

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contact tngfb@microsoft.com  


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Wednesday, March 02, 2011 6:47 AM
  • Hi adamf83,

    Any updates?


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Friday, March 04, 2011 1:29 AM
  • Frank,

    No CAS array

    It appears to effect the external connection more.

    Exbpa didn't highlight any problems

    I have reset the OWA VD and the issue seems to have improved slightly but users are still getting the error messages

    We have no on-access anti-virus scanning on any servers.  Just scheduled scans out of hours.

    Cheers

    Adam.

    Friday, March 04, 2011 3:17 PM
  • Frank (or anybody else),

    Just wondering if you have any more idea what might be causing the problem.  The error message below has appeared a couple of times in the application event log on the CAS server:

    Watson report about to be sent for process id: 8716, with parameters: E12, c-RTL-AMD64, 14.01.0218.015, OWA, unknown, unknown, System.InvalidOperationException, 0, unknown.
    ErrorReportingEnabled: True

    Does that shed any light?

    Cheers

    Adam.

    Tuesday, March 08, 2011 12:47 PM
  • This is also happening when users try and spell check e-mails.  See the screenshot in the link below.

    http://i55.tinypic.com/28hopl4.jpg

    Does anybody have any ideas?

    Thursday, March 10, 2011 1:19 PM
  • Still having problems with this... A couple of new fixes I've tried.

    I've uninstalled our Anti-Virus product from the CAS server - no change

    Applied Ex2010 SP1 RU3 to both servers - no change

    I created a new authorative dns zone (for our external OWA URL), added an A record with no name and pointed it at both of our CAS servers (seperatly) - this has made no difference.

    Does anybody have any suggestions? I'm now really stuck with this...

    Cheers

    Adam.

     

    Thursday, March 17, 2011 11:18 AM
  • And now this error message has started to appear on clients (see screenshot)

    http://i51.tinypic.com/ddgab4.jpg

    Cheers

     

    Adam.

    Thursday, March 17, 2011 7:49 PM
  • To solve this issue we had to get staff using our internal OWA url.  Since doing this there has been no more occurances of the error.
    • Marked as answer by adamf83 Sunday, April 03, 2011 10:54 AM
    Sunday, April 03, 2011 10:53 AM
  • Hi Adam or Anyone

     

    Did anyone get a fix for this?

    We have EXACTLY the same issue, Exchange 2010 SP1 on SBS 2011....

     

    Using the internal OWA url isnt an option as they are accessing OWA from home and not via a VPN.


    Any ideas?

    Ashley

    Tuesday, September 06, 2011 12:50 AM
  • Hi

    I have the same configuration as Ashley. Has there been any solutions for this issue?

    Thanks

    Mahesh

    • Proposed as answer by K.Winters Tuesday, July 10, 2012 9:13 PM
    • Unproposed as answer by K.Winters Tuesday, July 10, 2012 9:13 PM
    Monday, November 14, 2011 12:02 PM
  • Hi all,

    I have the same error on an Exchange 2010 SP3 machine, I have contacted MS Support to know what might be causing the problem and still waiting for an answer ....!

    Tuesday, May 21, 2013 6:22 AM
  • We have exactly the same issue. Started today.
    Wednesday, June 19, 2013 12:22 AM
  • Did any one found an answer for this? I have the same issue on my 2010 Exchange server

    Friday, October 11, 2013 5:44 AM
  • hi, I have the same error message in owa.

    I have dual servers with cas, mbx and hub on each machine.

    internal and external url are the same in my case as servers are published in dmz.

    exchange 2010sp3.

    Tuesday, October 22, 2013 5:21 AM
  • I'm completing a server migration and just had this issue. In my case, the external URL for OWA was configured the same for the old Exchange 2007 owa and the new Exchange 2010 owa. This was a small migration, so we did not have ongoing coexistence with a second valid url for Exchange 2007 owa.

    After removing the external URL for Exchange 2007 owa, the error was resolved and mail opened properly.

    I expect that if we just had a different external URL for Exchange 2007 owa it would also have resolved the issue.


    Byron Wright (http://byronwright.blogspot.com)

    Wednesday, November 13, 2013 1:48 PM