{"id":173,"date":"2016-04-13T02:28:56","date_gmt":"2016-04-13T08:28:56","guid":{"rendered":"http:\/\/www.cmadix.com\/?p=173"},"modified":"2016-04-13T02:32:54","modified_gmt":"2016-04-13T08:32:54","slug":"event-id-15021-httpevent-%e2%80%9cerror-occurred-while-using-ssl-configuration-for-endpoint-0-0-0-0444%e2%80%b3-%e2%80%93-exchange-server-2013","status":"publish","type":"post","link":"http:\/\/www.stormbreaker.tech\/?p=173","title":{"rendered":"Event ID 15021, HTTPEvent \u201cerror occurred while using SSL configuration for endpoint 0.0.0.0:444\u2033 \u2013 Exchange Server 2013"},"content":{"rendered":"<p>Event ID 15021, HTTPEvent Error An error occurred while using SSL configuration for endpoint 0.0.0.0:444 \u2013 Exchange Server 2013<\/p>\n<p>Error Decription:<\/p>\n<p>An error occurred while using SSL configuration for endpoint 0.0.0.0:444. The error status code is contained within the returned data.<\/p>\n<p>You will find the multiple events are thrown every minute with similar description.<\/p>\n<p>This is a common error I observed in Exchange Server 2013. You will observe the all or few of the following,<\/p>\n<p>1. Exchange Administration Center (EAC) returns blank page<br \/>\n2. The OWA allows login, but returns blank similar to EAC result<br \/>\n3. Outlook or any other Exchange Clients will fail to connect.<br \/>\n4. Exchange Management Shell Fails to connect.<br \/>\nThis happens, I suppose, due to the usage of non-existed certificate. I have verified the ID of the certificate in question with the available certificate in my SSL store, however I did not find the one which was assigned to 0.0.0.0:444.<\/p>\n<p>How to Fix:<\/p>\n<p>1. View the certificate binding, and identify and delete the certificate assigned to IP:Port<br \/>\n2.  Assing (Add) a valid certificate to it which is used by IP:Port 127.0.0.1:443.<br \/>\nProcedure:<\/p>\n<p>Open Command Prompt (because EMS is broken)<\/p>\n<p>1. Run \u201cnetsh http show sslcert\u201d<\/p>\n<p>    Note down the Certificate Hash and Application ID of the certificate assigned to IP:Port 127.0.0.1:443.<\/p>\n<p>2.  Run the below command to delete certificate assigned for IP:Port 0.0.0.0:444<\/p>\n<p>    netsh http delete sslcert ipport=0.0.0.0:444<\/p>\n<p>3. Run the below command to add the noted certificate to ipport=0.0.0.0:444<\/p>\n<p>    netsh http add sslcert ipport=0.0.0.0:444 certhash=1234ed434 appid=&#8221;{1010101010}&#8221;<\/p>\n<p>    Note \u2013 replace the certhash and appid with the value noted earlier.<\/p>\n<p>Wait for a while, and you will no longer observe the error events in the Event log and the Exchange will start functioning as normal. It is recommended to take a restart of the server post these changes.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Event ID 15021, HTTPEvent Error An error occurred while using SSL configuration for endpoint 0.0.0.0:444 \u2013 Exchange Server 2013 Error Decription: An error occurred while using SSL configuration for endpoint 0.0.0.0:444. The error status code is contained within the returned data. You will find the multiple events are thrown every minute with similar description. This &hellip; <\/p>\n<p class=\"link-more\"><a href=\"http:\/\/www.stormbreaker.tech\/?p=173\" class=\"more-link\">Continue reading<span class=\"screen-reader-text\"> &#8220;Event ID 15021, HTTPEvent \u201cerror occurred while using SSL configuration for endpoint 0.0.0.0:444\u2033 \u2013 Exchange Server 2013&#8221;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"sfsi_plus_gutenberg_text_before_share":"","sfsi_plus_gutenberg_show_text_before_share":"","sfsi_plus_gutenberg_icon_type":"","sfsi_plus_gutenberg_icon_alignemt":"","sfsi_plus_gutenburg_max_per_row":"","footnotes":""},"categories":[5],"tags":[8,6,7],"_links":{"self":[{"href":"http:\/\/www.stormbreaker.tech\/index.php?rest_route=\/wp\/v2\/posts\/173"}],"collection":[{"href":"http:\/\/www.stormbreaker.tech\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.stormbreaker.tech\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.stormbreaker.tech\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.stormbreaker.tech\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=173"}],"version-history":[{"count":1,"href":"http:\/\/www.stormbreaker.tech\/index.php?rest_route=\/wp\/v2\/posts\/173\/revisions"}],"predecessor-version":[{"id":174,"href":"http:\/\/www.stormbreaker.tech\/index.php?rest_route=\/wp\/v2\/posts\/173\/revisions\/174"}],"wp:attachment":[{"href":"http:\/\/www.stormbreaker.tech\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=173"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.stormbreaker.tech\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=173"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.stormbreaker.tech\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=173"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}