How to Fix “http 500 error” EAC/OWA Exchange Server

by

In this article, we will check the different methods to resolve the Exchange admin center HTTP 500 internal server error quickly.

Search extensively and end up with several possible solutions to resolve this issue.

Check the methods below to troubleshoot “Error 500” and resolve this issue:

Method 1:

A quick workaround to fix this issue, remove the computer object from the restricted group.
Check the groups below that denied the ms-Exch-EPI-Token-Serialization user right:

  • Domain Admins
  • Schema Admins
  • Enterprise Admins
  • Organization Management

Then restart the system that has the Exchange Server role assigned.

Method 2:

ADSI settings.
As we know, editing ADSI data is risky. So, before using this method, please take a system state backup.

Method 3:

Make sure to use the correct name for ECP virtual directories and configure virtual directories correctly.

The default URLs contain the FQDN of the server. For example, if your server name is “exchange006.domain.com”, then the default URL for OWA will be “https://exchange006.domain.com/owa“.

You can use the command below to modify, if you find it is incorrect:

Set-ECPVirtualDirectory -InternalURL < InternalUrl> -ExternalURL < ExternalUrl >

Method 4:

If the above option didn’t work, then recreatethe ECP virtual directory:

Remove-EcpVirtualDirectory -Identity "ServerName\ecp (Default Web site)"

New-EcpVirtualDirectory -Server -InternalURL < InternalUrl> -ExternalURL < ExternalUrl >

Reference: https://docs.microsoft.com/en-us/powershell/module/exchange/client-access-servers/New-EcpVirtualDirectory?redirectedfrom=MSDN&view=exchange-ps

Method 5:

Ensure all Exchange services are running.

Especially the MSExchangeADTopology and MSExchangeIS services.

Method 6:

Make sure all the Exchange server components are working fine:

Get-ServerComponentstate -Identity “servername”

If you find it Inactive, then run the below command to activate the relevant component:

Set-ServerComponentState -Component “component name” -Requester HealthAPI -State Active

Method 7:

Ensure that MSExchangeECPAppPool is running and check the physical path; for example, check the below image for configuration:

You may also get help from - Exchange Mailbox (.edb) Recovery Tools 

Method 8:

Check the Binding and Path for the Default Web Site and the Exchange Back End site.

For example, check the image below:

Method 9:

Some people find their solution by:

  1. Reinstalling:
    Setup /Mode:upgrade /IAcceptExchangeServerLicenseTerms
  2. Upgrade Net Framework
  3. Works when login to the ECP link in this form https:// servername/ecp? ExchClientVer=15