Monday, March 3, 2014

Exchange 2013- Blank ECP / OWA screen, event ID 15021 HttpEvent in system event log.

You have an exchange 2013, after some unknown event nobody can get to OWA or ECP (or any other IIS based resource including outlook.)  Instead, users get a login screen then a blank page.  In the system event log, you see hundreds of id 15021 on the source HttpEvent that say “An error occurred while using SSL configuration for endpoint 0.0.0.0:444.  The error status code is contained within the returned data.” 

-          Open the Command Prompt
-          Run-
netsh http show sslcert
-          This will show the certs, copy and paste this information into notepad.  Under     IP:port   : 127.0.0.1:443, note the certificate hash and application ID.
-          Run this command-  (Yes, I know there is no :444 listed in the output from the earlier command.)
netsh http delete sslcert ipport=0.0.0.0:444
-          Run this command.  Replace certhas with the certificate hash and appid with the application ID you saved in notepad.
netsh http add sslcert ipport=0.0.0.0:444 certhash=123123123123123 appid="{123123123123-1231231235}"

-          Reboot the server.

42 comments:

  1. Excellent info. Thank you. Solved it right away.

    ReplyDelete
  2. You're a life saver. It worked for me too.

    ReplyDelete
  3. Thanks, you saved us from hours and hours...Great!

    ReplyDelete
  4. As with the guys above, I cannot THANK you enough for this info. After upgrading my cert from a self-signed to a purchased, and then rebooting, it nurfed my SSL and in turn all the Exchange services. This is exactly what I needed to recover. Thanks a million for this.

    ReplyDelete
  5. Good job, you helped me a lot ! Thanks !!!

    ReplyDelete
  6. Where do we send the checks? Another one saved after a longer than I'd l'd like to admin troubleshooting and chasing my own tail!

    ReplyDelete
  7. Excellent article. Spot on. Thank you.

    ReplyDelete
  8. as an addition - our 'unknown event' was installing security update kb3011140. Installed CU7 after that and still the same issue. This solution did fix our problem.

    ReplyDelete
  9. "as an addition - our 'unknown event' was installing security update kb3011140. Installed CU7 after that and still the same issue. This solution did fix our problem. "

    Ditto for me

    ReplyDelete
  10. we had the same after installing security updates.

    ReplyDelete
  11. we then went into IIS manager to the sites. looked at exchange back clicked on "bindings" then opened HTTPS to see that the SSL cert entry was blank. We simply re-selected the "Microsoft Exchange" cert APPLIED and then all cam back to life after about 5 mins.

    kevin.haydon@norsa.co.uk

    ReplyDelete
  12. WOW for once someone who knows what they are doing!! No pages filled with me too I have the same problem. Just a good solid answer. You saved me a ton of work. Thank you

    ReplyDelete
  13. Thanks... did not need to delete mine, just had to point to the right certificate... thanks for point it out.

    ReplyDelete
  14. Big Thanks saved my ass! I had the problem after the patchday feb 2016

    --Yes, I know there is no :444 listed in the output from the earlier command.)

    For me there was an entry for 0.0.0.0:444 when i used the command but you steps still worked fine.

    ReplyDelete
  15. Like John, for me there was an entry for 0.0.0.0:444. And also like John, this nevertheless fixed it. Thanks so much - it's late, this is fixed, and now I can shut down the computer and go to beddddd!

    ReplyDelete
  16. me too get working using this fix great :D
    freakin microsoft whats wrong there? Situation for hack?

    ReplyDelete
    Replies
    1. problem occured after installing updates and rebooting server

      Delete
  17. worked for me as well. I had just installed exchange 2013 cu12, after the restart white screens on all the web based apps. this fixed it for me as well. thanks man!

    ReplyDelete
  18. Thank you so much! You saved my day

    ReplyDelete
  19. hi, just handled this issue by issuing a new certificate through external CA. you just need to mention the new CA name in your IIS default and backend config.

    ReplyDelete
  20. can't believe crap like this is still happening. thanks for the quick fix. :)

    ReplyDelete
  21. Thanks Adam1115, you saved me hours of work. Much appreciated!

    ReplyDelete
  22. Thank you very much. Was about to reinstall exchange.

    ReplyDelete
  23. You are the man! Fixed it right away.

    ReplyDelete