none
The server operation timed out. Please try again later RRS feed

  • Question


  • Hello,

    For some days now we are struggling with the OWA for our internet clients. Internally OWA with a server certificate is working fine. Externally we have a digicert certificate for OWA. If i do anything in the OWA i get ' The server operation timed out. Please try again later'. I can login in just fine and even browse, read and delete emails at first but if i keep on browsing on then the error comes. Its very irritating as i have to close the whole windows and relogin.

    I thought some recent framework updates had caused this so i removed it but still same issue. Then i recreated the OWA directory again and still same problem.

    The error logs in the event viewer show nothing. All exchange events are clean no errors.

    I tried it on different browser IE, Firefox and Chrome but still same issue also with different user accounts. I have no idea what to do with this issue.

    Sheldon.


    Side Note: We had transactions logs fill up our harddisk and exchange did stop. But after taking a backup its started to work. (I doubt that this could be the problem as exchange is working fine)
    Saturday, October 15, 2011 9:39 AM

Answers

  • Hi Sheldon,

    1 Try to disable AV if you have and test.

    2 Please try this KB:

    http://support.microsoft.com/kb/2540222

    3

    Install ASP.net

    Exchange 2010 CAS, on EWS Virtual Directories (VDir), remove Basic authentication and keep only Anonymous and Integrated authentication

    On ECP and OWA VDir, selecte SSL & run IISRESET command on the CAS.

     


    Best Regards!
    • Marked as answer by Rowen-Xu Friday, October 21, 2011 6:41 AM
    Monday, October 17, 2011 1:54 AM

All replies

  • 1. Which version of Exchange ?

    2. How OWA published to External ? through TMG/ISA ?

     

    if internal access is fine, you need to think from Exrternal publishing perspective,

    1. check the Rule from TMG ,

    2. Verify with Internet tools like MXtoolbox site,

    • Proposed as answer by sumesh vasu Saturday, October 15, 2011 7:37 PM
    Saturday, October 15, 2011 12:39 PM
  • OWA 2010 SP1, OWA is not published through ISA. Another company has done it for us by Nating IP to it.
    MVI - Most Valuable Indian
    Saturday, October 15, 2011 1:05 PM
  • How about reachability of public IP ?  MXtoolbox tests ?

     

    Check with the ISP too.

    Moreover enable diagnostic logging at Exchange level to find if any events.

     


    • Edited by sumesh vasu Saturday, October 15, 2011 7:43 PM
    Saturday, October 15, 2011 7:42 PM
  • Hi Sheldon,

    1 Try to disable AV if you have and test.

    2 Please try this KB:

    http://support.microsoft.com/kb/2540222

    3

    Install ASP.net

    Exchange 2010 CAS, on EWS Virtual Directories (VDir), remove Basic authentication and keep only Anonymous and Integrated authentication

    On ECP and OWA VDir, selecte SSL & run IISRESET command on the CAS.

     


    Best Regards!
    • Marked as answer by Rowen-Xu Friday, October 21, 2011 6:41 AM
    Monday, October 17, 2011 1:54 AM