Exchange Server HTTP Error 500 via DAG Architecture

“localhost is currentle unable to handle this request http errror 500”

If you have an exchange server architecture with dag and you get the following error when trying to log in to your server from ecp & owa interfaces, we will have a few suggestions other than what is written on the internet.

The following steps should be checked in order to understand why this problem occurs.The problem I had was due to an installed windows update corrupting the database of the failover cluster manager, yours may be different.

1-When was last update installed?

2-When was your exchange server restared?

What is the status of the databases running on the servers, on which server does it appear, and what is the mount dismount status?

If I have two servers, I will return from my backup the database of the failover cluster manager on the server that is an “active on server”, which is the last server on which it runs.

Before restoring the following files, stop your failover service and back up your files to another area.
Then copy these four files (actually the important CLUSDB and CLUSDB.blf files) from the backup back to the same location.
Then start the “Cluster Service” from the services.
When you enter “FailoverCluster Manager” in the server manager, you will see that you can now configure and manage the Cluster Manager as before.

if you have a different situation, you can search the following topics on the internet.

1-Check Security update for exchange server.

2-If your iis files crash, you try the config files update the following below;

Run as administrator powershell and go to this path:

“C:\Program Files\Microsoft\Exchange Server\v15\Bin\UpdateConfigFiles.ps1”

“C:\Program Files\Microsoft\Exchange Server\v15\Bin\UpdateCas.ps1”

3-As a last resort you can apply the following

Downloding current exchange server cumulative update and reparing with powershell the following command.

Setup /Mode:upgrade /IAcceptExchangeServerLicenseTerms