Funky Exchange OWA Issue
-
So we have two exchange servers set up now, the newest being Exchange 2016.
I did my best to mimic all of the DNS entries of the previously configured Exchange 2013 server, but when I go to Exchange2016serv.contoso.com/owa to access the web app, it’s a white screen.
Here’s the funky part: when you instead type in Exchang2016serv.contoso.com/ecp, you get the ecp like you are supposed to, but If you THEN change it to /owa, it works!
Of note: there seems to be a longer than usual redirect url at this point though.I check IIS>Bindings to double check certs for default and exchange backend, but everything looks fine. I feel like this is DNS issue, but haven’t been able to pinpoint exactly what. Any ideas?
-
This shouldn't be a DNS issue as the hostname isn't changing, but the path is.
-
There is a link to a cumulative update for Exchange 2013, not sure if the workaround will apply to Exchange 2016:
MS Support link -
@pirho99 Thanks. I’m not able to get as far as logging in, but I’ll still give this a read and check my current CU version.
-
Does the OWA screen populate even if you do not login to ecp? Is it the fact that you visited the /ecp first, or that you logged into /ecp that allows /owa to work?
-
@JasGot Yes. It populates even when I don't log into ecp. Just visiting /ecp seems to make /owa work.
-
@G-I-Jones said in Funky Exchange OWA Issue:
@JasGot Yes. It populates even when I don't log into ecp. Just visiting /ecp seems to make /owa work.
Where is the mailbox located? On the 2013 server or 2016?
Also I know you checked for the backend SSL too. What do the event logs show on the Exchange 2016 server?
https://markgossa.blogspot.com/2016/01/owa-blank-page-exchange-2013-2016.html
https://insidemstech.com/2016/08/15/exchange-20132016-eacecp-and-owa-blank-page-after-login/ -
I figured it out. In IIS>Default Web Site>SSL Settings>Client certificates was checked to Require. I moved it to ignore, and viola.
-
@G-I-Jones said in Funky Exchange OWA Issue:
I figured it out. In IIS>Default Web Site>SSL Settings>Client certificates was checked to Require. I moved it to ignore, and viola.
That's weird usually no one has that checked by default.
