none
OWA not loading

    Question

  • Hi guys,

    today we patched our Exchange server 2013 with the latest updates.

    however now the owa and outlook users are not able to connect.

    Outlook cant connect with exchange.

    OWA we get the log in page we add username and password after the page is not loading " Blank ", is the same for ECP.

    nothing really changed on the virtual directory. on the https 443 is the correct certificate configured on the server.

    powershell is not connecting either.

    I want to use those commands to reset everything but can't even connect using powershell

    Set-OWAVirtualDirectory -Identity "adminsrv\OWA (Default Web Site)" -FormsAuthentication $False -BasicAuthentication $True

    Set-OWAVirtualDirectory -Identity "adminsrv\OWA (Default Web Site)" -FormsAuthentication $true -BasicAuthentication $True

    please advise how to fix this.



    • Edited by Julien.AG Monday, November 30, 2015 2:44 AM
    Monday, November 30, 2015 2:34 AM

Answers

  • I assume it is just Nov 2015 MS security updates. Can you check for the update with KB number KB3097877 got installed today? If so, then uninstall the patch and reboot the server.

    After reboot, please try OWA and ECP link.

    Thank you Br0209

    I managed to fix it .

    somehow the patch reset the virtual directory.

    the back end exchange page didn't had a certificate assign to it.

    Monday, November 30, 2015 10:27 AM

All replies

  • Hi,

       Did you get any certificate error while the initial login page got loaded? 

    Cab you please check:

    IIS bindings for OWA and ECP in IIS? [ for both http and https]

    Are you able to browse the sites internally from mail server?

    Worth reseting the virtual directories.

    Monday, November 30, 2015 2:42 AM
  • Just checking did you run the below command before updating MS exchange

    Also can you please tell me which updates did you install?

    Setup.exe /PrepareAD /IAcceptExchangeServerLicenseTerms

    Monday, November 30, 2015 2:47 AM
  • Recently I experienced an issue with a blank page loading after attempting to sign in to  the Enterprise Control Panel (ECP) and Outlook Web App (OWA) websites on an Exchange 2013 server. After troubleshooting I figured out that after updating the certificate and deleting the old expired cert IIS needed a manual change. I’m not certain if this is a bug in the script Exchange uses to update the certificates from the ECP, but it is easy enough to resolve manually.

    1. Login to the Exchange 2013 server and open Internet Information Services (IIS) Manager
    2. Expand your server name, then sites, right-click Exchange Back End, and choose “Edit Bindings…”
    3. Select the entry using port 444 and click the Edit… button
    4. Select the new SSL certificate in the SSL Certificate… drop-down. This drop-down was set to “Not Selected” in my instance. I simply changed it to the cert I had just installed in the ECP and everything worked fine.
    5. Click OK, then Close when finished. Feel free to do an IISRESET as well just to be thorough. I didn’t have to do this, but it never hurts after making changes in IIS.

    Once I did that I was able to load OWA and the ECP again. This was a particularly tricky issue to figure out since I didn’t see any errors in the Application logs on the Exchange server. Hopefully this will help out anyone seeing the same issue.

    • Edited by Julien.AG Monday, November 30, 2015 3:00 AM
    Monday, November 30, 2015 2:52 AM
  • I assume it is just Nov 2015 MS security updates. Can you check for the update with KB number KB3097877 got installed today? If so, then uninstall the patch and reboot the server.

    After reboot, please try OWA and ECP link.

    Monday, November 30, 2015 3:02 AM
  • I assume it is just Nov 2015 MS security updates. Can you check for the update with KB number KB3097877 got installed today? If so, then uninstall the patch and reboot the server.

    After reboot, please try OWA and ECP link.

    Thank you Br0209

    I managed to fix it .

    somehow the patch reset the virtual directory.

    the back end exchange page didn't had a certificate assign to it.

    Monday, November 30, 2015 10:27 AM