After enabled TLS 1.2 Exchange 2016 ECP and OWA inaccessible to authentification HTTP 500

Question

Hi,

I recently deployed TLS 1.2 in Exchange Server 2016 after this, ECP and OWA could not be reached in authentication error HTTP 500

help, please.

Answer 1

Hi @Anonymous ,

Are there any logs in Event Viewer after you got the HTTP 500 error?
And what is your Exchange CU version? Because in my Exchange 2016 CU19 lab, i tested the e-mail flow and analyzed the message header and found it's already TLS1.2

If you could, please share more information about how you deployed TLS 1.2 and if any setting changes in your Exchange server.

A common workaround for the Error Http 500:

• Check the Application Pools in IIS for MSExchangeECPAppPool and MSExchangeOWAAppPool, make sure they are running and the physical path is right:
  
  

• Reset the ECP and OWA virtual directories(replace ex2016.contoso.com with your server FQDN): Remove-OwaVirtualDirectory “ex2016\owa (Default Web Site)”
  New-OwaVirtualDirectory -InternalUrl “https://ex2016.contoso.com/owa” -ExternalUrl “https://ex2016.contoso.com/owa”
  Remove-EcpVirtualDirectory -Identity “ex2016\ecp (Default Web Site)”
  New-EcpVirtualDirectory -InternalUrl “https://ex2016.contoso.com/ecp” -ExternalUrl “https://ex2016.contoso.com/ecp”
• Check the certificate bindings in IIS, make sure the https is using the correct certificate. It's Exchange self-signed certificate by default.
  
• Run this command to mount the unmounted database: Get-MailboxDatabase -Server SERVERNAME | Mount-Database
  About the HTTP 500 error: Fixed Exchange Server HTTP 500 Internal Error - 2016 | 2013 | 2010

Regards,
Lou

---

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.