Thursday, 28 January 2016

OWA blank page | Exchange 2013, 2016

Symptoms


You try to log into Outlook Web App (or now called Outlook on the Web) using Exchange 2013 or 2016. You’re presented with a login screen then after you sign in, you are presented with a blank screen. This often happens after a restart or an upgrade. See below:

image

After logging in:

image


Cause


The cause of this is that the Exchange Back End site in IIS on your MBX server is no longer bound to a certificate (SSL certificate “Not Selected”). See below:

image

Resolution


To resolve this issue, open up IIS Manager on your Exchange server:

image

Then right click on Exchange Back End and click on Edit Bindings. You’ll be presented with a list of site bindings.

image

Double click on the https entry in the list. You should now see the below window:

image

In the SSL certificate drop down, select the Microsft Exchange certificate:

image

Click OK then click Close.

You should now be able to log into OWA:

image

Repeat for your other servers if needed.

10 comments:

  1. http://unproduced.screenplay.mobi/hollywood-manger/459.html ONLY NEWS XXX

    ReplyDelete
  2. This comment has been removed by the author.

    ReplyDelete
  3. Didn't worked for me :( ECP opens just fine, OWA is blank page. System is windows XP so i guess there is a problem. Other computers open OWA just fine...

    ReplyDelete
  4. I think this is very interesting and knowledgeable information. I appreciate your great stuff about the windows migration.

    sccm migration
    windows migrations

    ReplyDelete
  5. Had this problem, but there was a certificate bound so there must be another cause of this problem.

    ReplyDelete
  6. Had this problem, but there was a certificate bound so there must be another cause of this problem.

    ReplyDelete
  7. My problem that caused the blank page turned out to be the Exchange server's clock was 20 minutes behind because it had been shut off for a while and was hosted on ESX. Getting the time synced fixed the problem.

    ReplyDelete
  8. Another thing that can cause this problem other than the SSL certificate issue is having a system time that is way off from what it should be.

    ReplyDelete