Exchange 2013 EAC / ECP Blank Screen
When trying to log in into the new Exchange 2013 EAC / ECP you encounter a plain blank screen and get no options at all. The URLs you may see this error on are below.You must attach to these addresses on the CAS server so you need the CAS role installed.
https://ServerName/owa
Ive seen this with two seperate issues, one is SSL cert related and one is corruption. If it is SSL related you will see this error in event viewer.
To resolve this drop to command line and enter the following.
netsh http show sslcert
This will show all certs, make a note of the certs HASH and the APPID.
Delete the erroring cert with this command.
netsh http delete sslcert ipport=0.0.0.0:444
Now we assign the cert with the hash and the appid you noted.
netsh http add sslcert ipport=0.0.0.0:444 certhash=123123123123123 appid="{123123123123-1231231235}"
Restart the server and you will now see the ECP
In my situation it was because one of the virtual directories in IIS have become corrupt, we need to recreate them, to do so run the following commands.
To remove and recreate the ecp (Default Web Site)
Remove -OwaVirtualDirectory -Identity Servername\ecp (Default Web Site)
new-OwaVirtualDirectory -InternalUrl https://ServerFQDN/ecp -WebSiteName Default Web Site
To remove and recreate the OWA (Default Web Site)
Remove -OwaVirtualDirectory -Identity Servername\owa (Default Web Site)
new-OwaVirtualDirectory -InternalUrl https://ServerFQDN/owa -WebSiteName Default Web Site
This resolved my Exchange 2013 OWA and ECP blank screen issue
http://technet.microsoft.com/en-us/library/ff629372.aspx
Loading ...
Jonathan Franklin
| #
Since first installing Exchange 2013 we have continually returned to Allen’s site for guidance. His cutting edge implementation and sharing of information about the process has proven invaluable to us. We again had to turn to Allen yesterday because we encountered the very error discussed here. Not surprisingly, Microsoft’s tech support had left us in a pickle. Within minutes we were able to successfully sort through this with Allen’s help. We can’t begin to say enough complimentary comments about his dogged determination to help! Allen is a real gem in today’s world of tech.
What a great site, Allen! And thanks for all of your help!!!!
j
Reply
Jason Charnov
| #
On this issue, I found that the bindings had become garbled in IIS. I had double or triple entries for the default web site (front end CAS). Removing those extra entries and verifying that the existing ones were bound to all unassigned allowed me back into the ECP and OWA.
Reply
Yar
| #
i have install on clean windows 2012 server Exchange 2013 with CU1, but i cant find cmdlets that you are using in this post.
is it possible to upload them all somewhere?
Reply
Allen White
| #
When you start to type the cmdlet press “tab” to see all the cmdlets.
Reply
Mike Cusumano
| #
Thanks so much for the post Allen. This version of Exchange will take some time to get used to. Glad I found the fix on this site. Keep up the great posts!
Best, Mike
Reply
Najam
| #
Thanks so much for the post Allen.
After Installing SSL certificate I cannot view EA c or owa …Its a blank whitescreen.
I tried the above command and it says
SSL Certificate add failed, Error: 1312
A specified logon session does not exist. It may already have been terminated.
Reply
Boubakar
| #
Salut Allen,
Franchement je te dis grand merci. Ton aide m’a été très précieuse pour résoudre mon problème. Encore merci.
Boubakar
Reply
Mollet
| #
you saved my day too ! somehow the add command only worked when typed in cmd field not by copy it from notepad, maybe because of the ” “format or the {}…. write it in the cmd field and only copy the hash and the appid. the appid is the same as from the false certificate..
Reply
Mike
| #
I am having the same issue as Najam:
Attempting to add the ssl cert results in:
SSL Certificate add failed, Error: 1312
A specified logon session does not exist. It may already have been terminated.
I tried typing the command, as Mollet suggested, no luck. What I had to do was find the certificate by thumbprint/CertHash and move it from Trusted Root CA to Personal in the Certificate MMC and then re-run the add command.
Now the command executed AND Exchange ECP works!
Reply
Jon
| #
Excellent solution(s). Thanks for the expert advice. Was able find the info in the event logs and then blow away and re-add the cert. Thank you!
Reply
Jeff
| #
The above didn’t help. Mike’s option didn’t help either, even after I copied all the Exchange certificates (mail.*, [server_name], and Microsoft Exchange Server Auth Certificate) from Trusted Root to Personal and vice versa.
What fixed ECP and OWA all at once was:
Open IIS manager
Click on “Exchange Back End” under “Sites”
Click Bindings
Select the “https” binding (normally on port 444) and click Edit…
The ‘SSL certificate’ field was blank, so I entered the UCC certificate
Clicked OK
Clicked Close
Restart IIS at a command prompt: IISRESET /noforce
Voila! ECP and OWA and Outlook clients started working again.
Reply