Hi All,

I followed the Exchange help files to ensure that all forest, domain and local server pre-requisites were installed, in the correct order, with time being allowed for replication of changes across the forest. The install went well with no errors reported. I am however having an issue with accessing the ECP (OWA behaves the same) in that the URL changes to https://serverFQDN/owa/auth/logon.aspx?url=https%3a%2f%2fserverFQDN%2fecp&reason=0 ( originally entered as https://serverFQDN/ecp )and all that is produced is a blank page.

Environment:

Windows Server 2008 R2 (all updates applied) freshly installed in a child domain using a Domain Admin account granted Enterprise and Schema admin rights and added to the Organisation Management group. No previous Exchange organisation existed as this is a freshly configured (pre-production) environment that I intend to migrate into. Both the MAilbox and CAS server roles are installed, the server has 16 GB of RAM

Following research on the web I have already tried:

• Uninstalling and re-installing Windows Identity Foundation
• Checking the mailbox for corruption using the EMS. The mailbox seemed ok but to be sure I created a new user, ran the enable-mailbox command, added the user to the Organisation Management group but still get exactly the same issue
• Running %windir%\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -ir
• Using the EMS to perform a Test-EcpConnectivity, it failed even with the test user created with the supplied creation script

I can't find any consistent entries in the event logs. Any suggestions?

• Edited by Stuart Ramwell Monday, November 12, 2012 11:00 AM

Anyone? This is beginning to cost me too much time now. I can find other examples of the same issue on the internet but no resolutions offered.

• Edited by Stuart Ramwell Tuesday, November 13, 2012 8:54 AM

Did you managed to run IISRESET once and access ECP or OWA?

Hi  ,

Please check if you configured redirection on IIS for default web site. If so, please uncheck redirection, run iisreset, and test again.

Hi,

I had already tried the IISReset command. Fruitless.

I haven't configured any redirection on IIS either.

I got sick of waiting for a response on here so uninstalled Exchange completely, rebuilt the Server with 2012, reinstalled Exchange and have exactly the same issue. Time to go digging round the Internet again...

Hi,

Please try recreating ECP & OWA virtual directory

Reset Client Access Virtual Directories:

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

And is there any error on the page when you open ECP or OWA ? such as HTTP

I had this problem with OWA and ECP showing a login page but coming up with a blank page after that. Also, Outlook 2013 could not access Exchange 2013. It turns out that in IIS the Exchange Back End website SSL port 444 certificate was set to none for some reason. When I selected the Exchange certificate and restarted the Exchange Back End website, everything started working normally.

Had the same problem.  Turns out mine was caused by Exchange 2010 Rollup -This fixed mine perfectly.  Hope this helps!

http://xyfon.com/tech-tips/blank-page-owa-update-rollup-exchange-2010/

Hi

In my case on the CAS, the binding in IIS was set to 443 127.0.0.1.
I changed it to the real IP ex 172.16.0.211 and then all worked OK.

Regards
Robert

This was my issue - disabling redirection worked. Thanks for the tip.

I had redirection enabled to redirect / to /owa so that users did not have to type it in. I guess I'll have to find another way of accomplishing this.

Thanks a Million TechW, you saved my life after struggling for so long with the ECP / OWA blank page...

The problem was exactly as you said above... an IIS issue on the Exchange Back End site having no certificate selected for the https port 444.

Thanks again, you're a life saver.

In my case this happened when upgrading from cu4 to cu7.  We had only two databases both of which would not mount.  To fix this quickly I created a new database, and a new user.  Then put this user in the org admin role and use this for administration until we were able to mount the databases.