OWA problem after upgrading to Exchange 2010 SP2

Answered OWA problem after upgrading to Exchange 2010 SP2

  • Wednesday, December 14, 2011 4:25 AM
     
     

    Hello,

    I've just upgraded Exchange Server 2010 to SP2. Before upgrading I can access OWA without SSL as usual, but now there's following problem after sign in successfully to OWA by http://servername/

    When click on Options, or many other places, an error message appear: "Your request couldn't be completed. This may have occurred for security reasons or because your session timed out".

    If access OWA by https://servername/, everything is ok.

    I unchecked "Require SSL" settings in IIS. Please help me to solve this problem.

    Thanks & regards,

    Anh Vo

All Replies

  • Wednesday, December 14, 2011 4:58 AM
     
     

    Hi,

    Make Sure the security settings of virtual directory of Exchweb,Authenticated Users have read access.

     

    Regards,

    RK

  • Wednesday, December 14, 2011 4:59 AM
     
     

    Redirect the traffic from Http to https,

    To redirect the website,

    Open IIS - navigate to Default Web Site -> Select HTTP redirect

    And redirect the traffic as per your need from http://server name to https://servername

     


    Viral Rathod Blog : http://viralr.wordpress.com
  • Wednesday, December 14, 2011 5:02 AM
     
     

    Please refer this article :

    http://social.technet.microsoft.com/Forums/en-US/exchangesvrclients/thread/821917f5-bdaa-4800-9a30-359e8404c5d9/


    Viral Rathod Blog : http://viralr.wordpress.com
  • Wednesday, December 14, 2011 5:04 AM
     
     Answered
    Hi Anh Vo,
    Have you change the setting in web.config as described in the "Simplify the Outlook Web App URL" found in the release notes for SP2?

    Outlook Web App
    If you’re using redirection for Outlook Web App and aren’t requiring Secure Sockets Layer (SSL), redirection will fail after the Client Access server is upgraded to Exchange 2010 SP2. To avoid this problem, after you’ve completed the upgrade to Exchange 2010 SP2, modify the Outlook Web App web.config file. For directions, go to “Use IIS Manager and Notepad to simplify the Outlook Web App URL when SSL isn’t required” in Simplify the Outlook Web App URL. You don’t have to make any changes in IIS Manager to prevent redirection from failing. You just have to modify the web.config file.

    Martina Miskovic - http://www.nic2012.com/
  • Wednesday, December 14, 2011 8:03 AM
     
     

    Hi Martina Miskovic,

    I haven't change the setting in web.config.

    "13. Find httpCookies httpOnlyCookies="false" requireSSL="true" domain="" and change the requireSSL flag to false."

    Thank you very much!

    Anh Vo

  • Wednesday, December 14, 2011 1:25 PM
     
     

    Thanks for everyone,I found the solution it is very easy,

    when I use https and require SSL checkbox and set the  binding for defaulth web site to All unassigned to http and https,OWA Worked well now. :)

  • Monday, December 19, 2011 1:01 PM
     
     

    I have the same problem. The strange thing is everything works fine with FireFox and IE8.

    When I try to access with IE9, I m getting error.

    "the windows couldn't be opened because your computer is low on memory.Please close some windows and try again."

     

    For the time being default site requires SSL, redirection is not active.

    OWA folder requires SSL. web.config key is requireSSL="true"

     

    I tried all the solutions given here. Am I missing something?

    please help

  • Friday, January 27, 2012 4:15 PM
     
     

    I have to assume that you found the answer since there are no other replies here. 

    Our situation is we use redirect as set up using the following article.

    http://www.techrepublic.com/blog/datacenter/exchange-2010-how-to-redirect-non-ssl-outlook-web-app-traffic-to-ssl/3319

    When you install SP2 it resets all of these settings back to redirect to the default web site for owa > https://email.yourdomain.com/owa and also sets all of the virtual directories to "require SSL".  
    I followed the instructions as posted by MS in the release notes:
    "simplify the outlook web url" article http://technet.microsoft.com/en-us/library/aa998359.aspx
    I don't know what modifying the web.config file does but it didn't appear to do anything for my case.
    To get back to where I only had to put "email.mydomain.com" in a browser for owa and ecp, I had to remove the SSL requirement for the default website and the ecp virtual directory.
    "simplify the outlook web url" article http://technet.microsoft.com/en-us/library/aa998359.aspx
    Make note of removing the redirect under the category:
    Use IIS Manager to remove redirection from a virtual directory
    Strangely enough, I did not have to remove the redirect for the ECP directory, just the SSL requirement.  (email.mydomain.com/ecp)
    For autodiscover I had to remove the redirect and the SSL requirement.  
    (outlook anywhere would not connect and the testexchangeconnectivity.com kept failing for autodiscover and outlook anywhere tests)
    For RPC I have to remove the redirect but get this, not the SSL requirement.  (outlook anywhere would not connect and the testexchangeconnectivity.com kept failing for autodiscover and outlook anywhere tests)
    You have to test out your own scenario's because this is obviously not very consistent but I come to expect this from some technet articles.  

  • Monday, March 19, 2012 10:33 PM
     
     

    As per release notes, you need to take care of web.config file changes prior to upgrade.

    If you’re using redirection for Outlook Web App and aren’t requiring Secure Sockets Layer (SSL), redirection will fail after the Client Access server is upgraded to Exchange 2010 SP2. To avoid this problem, after you’ve completed the upgrade to Exchange 2010 SP2, modify the Outlook Web App web.config file. For directions, go to “Use IIS Manager and Notepad to simplify the Outlook Web App URL when SSL isn’t required” in Simplify the Outlook Web App URL. You don’t have to make any changes in IIS Manager to prevent redirection from failing. You just have to modify the web.config file.

    Please find Release notes here.

    http://technet.microsoft.com/en-us/library/hh529928.aspx


    Abhijeet D