I have installed Exchange 2013

3 Servers - EX2013MBXA and EX2013MBXB (Mailbox Role only on each Server - DAG setup) on Win 2012, and EX2013CASA (CAS Role) on Windows 2008 R2

EX2013CASA Server has SSL Cert form internal PKI (URL is https://owamail.Domain_Namr/owa)

All was OK and then suddenly when accessing EAC from Internet Explorer type in URL as above and logon as Domain Admin and then just get a blank page.

I have tried New-ecpVirtualdirectory and New-OWAVirtualDirectory as suggested on some sites to reset ecp in IIS.

Get-ClientAccessServer shows my CAS Server (EX2013CASA)

Worryingly

Test-ecpConnectivity -ClientAccessServer EX2013CASA reports

"The specified computer isnt a Client Access Server"

Any Ideas on blank EAC and the above error message ?

Many thanks in advance

Try this,

• Ensure Exchange Services are running on CAS & MBX servers
• Try https://<CASServerFQDN/ECP to access EAC
• Ensure that user account has mailbox on Exchange 2013 mailbox server. you can use Get-Mailbox command let (http://technet.microsoft.com/en-us/library/bb123685.aspx) to check this

Thanks

I ensured all services were running on the Mailbox and CAS Servers using the Services section of the Windows Admin Tools and also using the EMS cmdlet Test-ServiceHealth.

I have tried https://CASServerFQDN/ecp and https://CASServerFQDN/owa and both give a blank screen

I log into CAS Server as Domain Administrator and from EMS can see via Get-Mailbox that the Administrator has a mailbox

I Did think the Remove-ecpVirtualDirectory and New-ecpVirtualDirectory would fix the issue (and similar for OWAVirtualDirectory), but to no avail.

Thus unfortunately still stuck.

Also tried re-importing SSL cert (without and change to my problem), but this should not be an issue as even with an invalid cert you simply should just get warnings and can press continue on the web browser anyway.

Also should the Test-ecpconnectivity -ClientAccessServer CASServerFQDN give a response that CASServerFQDN is not a Client Access Server even when Get-ExchangeServer output clearly show it is ?

I am getting to the stage where I might simply un-install and then re-install all the Exchange Servers.

Note - I did install another CAS Server to see if that might resolve the problem, but even with https://NewCasServer/ecp, still get a blank screen after logging into EAC  as Domain Admin. Thus I think it may be a mailbox server issue.

Any other ideas ?

Any errors like the below in the System Log (EventID: 15021)?

An error occurred while using SSL configuration for endpoint 0.0.0.0:444.  The error status code is contained within the returned data.

I used to have that and found the solution here

Thanks Martina

I do not have any errors relating to Exchange or certs in the Event Log (System or Application)

I gave had to manually start some Exchange services sometimes (due to limited RAM I think in my units resulting in timeouts). CAS Server I know needs 4GB RAM, Mailbox Servers 8 GB RAM.

Also I have not changed the certificate I have been using (internal Windows 2008R2 PKI)

I may try creating and importing a new certificate.

Surely though even with certificate issues the EAC will still open after a warning about Certificate problems anyway ?

Pity there is still no Console based admin tool like EMC anymore.

Many Thanks for your response and help

If the above fails I think I will re-install the servers.

My test was working correctly for a couple days.  It's been almost a week since install and now OWA and EWC return blank pages after logging in.

I did recall rebooting the DC earlier this week for some additional patches.

I rebooted the exchange server, cleared my browser cache, and started a new session (IE 10 InPrivate browsing) and was able to get in again.

Thanks for the information and suggestion

In the end I simply backed up the database and logs and re-created my Exchange Servers and all is now well.

Your suggestion may have been an explanation though, I did not try simply clearing the browser cache.

Hi,

had same Problem. events:

found solution here: http://sumoomicrosoft.blogspot.de/2012/11/exchange-2013-emc-blank-page.html

After deleting or assigning other Exchange certificate, you can't open emc page (blank page).

netsh http show sslcert

save output

delete error causing cert:

netsh http delete sslcert ipport=0.0.0.0:444

assign right cert:

netsh http add sslcert ipport=0.0.0.0:444 certhash=4849849849884484884848 appid="{4dc3e181-e1445554554155455}"

-> you can copy certhash and appid from the other applied certs..

Thanks Schuetti3000.

Your solution works. I was able to re-create certificate and OWA looks fine now.

Thanks to you guys. This saved my issues!

Great post.  ICANN caused me to change my cert and after a reboot I had no mail flow due to this.  thanks for posting.  Fixed mine.

Same thing here after cert renewal and restart. Thanks so much for this post!

Hi,

had same Problem. events:

found solution here: http://sumoomicrosoft.blogspot.de/2012/11/exchange-2013-emc-blank-page.html

After deleting or assigning other Exchange certificate, you can't open emc page (blank page).

netsh http show sslcert

save output

delete error causing cert:

netsh http delete sslcert ipport=0.0.0.0:444

assign right cert:

netsh http add sslcert ipport=0.0.0.0:444 certhash=4849849849884484884848 appid="{4dc3e181-e1445554554155455}"

-> you can copy certhash and appid from the other applied certs..

You save my day :)

Way I can't  mark at answer?

Hi,

had same Problem. events:

found solution here: http://sumoomicrosoft.blogspot.de/2012/11/exchange-2013-emc-blank-page.html

After deleting or assigning other Exchange certificate, you can't open emc page (blank page).

netsh http show sslcert

save output

delete error causing cert:

netsh http delete sslcert ipport=0.0.0.0:444

assign right cert:

netsh http add sslcert ipport=0.0.0.0:444 certhash=4849849849884484884848 appid="{4dc3e181-e1445554554155455}"

-> you can copy certhash and appid from the other applied certs..

You save my day :)

Way I can't  mark at answer?

I had the exact issue. This fix worked like a charm... 

thanks!

the bugy exchange 2013 works again!

Thanks Schuetti3000.

Your solution works great!

Hi;

Logon to the correct back end mailbox server

Open IIS manager 
Browse to the "Exchange Back End" website
Click Bindings
Mark the "https" binding (normally on port 444) and click Edit...
Verify (or change to) the correct certificate
Click OK
Click Close
Restart IIS on the server (IISRESET /noforce)

Regards.