Exchange SE Hybrid mode ECP page gives 500 error

Question

Trying to remove old Exchange 2016 server (EXCH2016 15.1.2507.6). New Exchange SE server (EXCHSE 15.2.2562.17) https://localhost/ECP page does not load (error 500) unless EXCH2016 is powered on.I've followed the steps from this page https://www.petenetlive.com/kb/article/0001472

This is Hybrid mode Exchange SE, all mailboxes are at Microsoft365.

Any suggestions appreciated!

Answer 1

Hi @Mike Sulser

Thank you for sharing your concerns. 

First, I’d like to clarify that this is a user‑to‑user support forum. Moderators participating here do not have access to backend systems, nor can we directly intervene in Microsoft product functionality. Our role is limited to providing technical guidance and sharing best‑practice recommendations based on reported issues, requests, and scenarios.      

Based on your description, looks like the Exchange SE ECP page only works when the legacy Exchange 2016 server is powered on. When that server is offline, you encounter an HTTP 500 error. This behavior strongly indicates that the new Exchange SE server is still dependent on components hosted on your Exchange 2016 server.  

You could start by validating arbitration mailboxes. Based on my research, in hybrid environments, Exchange management components (such as ECP) rely on system mailboxes and internal proxy routing. If these components (for example, arbitration mailboxes or organization mailbox) are still associated with the old Exchange 2016 server, the new server will not be able to process the request independently and will return a HTTP 500 error. You could also verify the organization mailbox, as ECP depends on it as well. 

You can begin by running the following command: 

Get-Mailbox -Arbitration | Format-Table Name, ServerName, Database -AutoSize 

Check the ServerName column carefully. If any of the arbitration mailboxes are still showing EXCH2016, this can cause the issue you are experiencing. 

If so, you can resolve this by moving the arbitration mailboxes to EXCHSE. First, ensure that you have a mailbox database on Exchange SE. If one does not already exist, create a small on‑premises mailbox database, as at least one database is required to host system mailboxes. 

Once the database is available, move all arbitration mailboxes by running: 

Get-Mailbox -Arbitration | New-MoveRequest -TargetDatabase "SystemDB" -BatchName "ArbitrationMove" 

Monitor the move requests until all of them show Completed status: 

Get-MoveRequest | Get-MoveRequestStatistics | Format-Table DisplayName, Status, PercentComplete, TargetDatabase -AutoSize 

After the moves have completed, clean up the completed move requests: 

Get-MoveRequest -Status Completed | Remove-MoveRequest 

Next, restart the ECP application pool, or simply perform an IIS reset: 

Restart-WebAppPool MSExchangeECPAppPool 

After completing these steps, power off EXCH2016 and test again https://localhost/ecp (as well as the external ECP URL) directly on EXCHSE. ECP should load successfully without returning an HTTP 500 error. 

I have also found some relevant articles that may be helpful for further reference. You can refer to them here: 

HTTP server error status (500) when signing in to EAC - Exchange | Microsoft Learn 

Unable to Login to ECP on First Exchange 2019 in Exchange 2013/2016 org – Learn Tech Future 

How to Fix HTTP ERROR 500 in ECP/EAC after Login 

Note: This information is provided as a convenience to you. These sites are not controlled by Microsoft, and Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please ensure that you fully understand the risks before using any suggestions from the above link. 

Please let me know if this helps. If you have any additional concerns, feel free to comment below. I would be more than happy to assist. 

---

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. 

Answer 2

The HTTP 500 on the ECP of the new Exchange Server is a symptom, not the root cause. From the provided context, there are three Exchange 2016/2013 ECP/OWA-related 500-error patterns and their resolutions that should be checked on the new server before decommissioning the old one:

1. Missing or damaged SharedWebConfig.config
   • If SharedWebConfig.config is missing or corrupt, ECP/OWA can fail with 500 errors after installation or updates.
   • Verify that SharedWebConfig.config exists in both of these paths on the new server:
     1. C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy
     2. C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess
   • If either file is missing, recreate it by following the guidance in the article about Event ID 1309 and missing SharedWebConfig.config.
2. HTTP 500 after Exchange security or cumulative updates
   • If the issue started after installing a CU or security update on the new server, a failed or partial update can cause 500 errors in ECP/OWA.
   • In that case, reinstall the most recent security update at an elevated command prompt on the new server:
     1. Open Command Prompt as Administrator.
     2. Run the .msp for the latest Exchange security update from its full path.
     3. Restart the server after the update completes.
   • This specifically addresses errors where required assemblies (such as Microsoft.Exchange.Common) are not properly registered after an update.
3. Known ECP defects fixed by later CUs
   • Some ECP issues in Exchange 2016 are resolved only by installing specific or later cumulative updates:
     • ECP redirection failures across AD sites when using the same external URL are fixed by Exchange 2016 CU9 or later.
     • Regional Settings in ECP returning HTTP 500 on Windows Server 2016 are fixed by Exchange 2016 CU10 or later.
   • Ensure the new Exchange server is on a CU level that includes these fixes (or later). If it is not, plan to update it to at least those CU levels.
4. General approach before decommissioning the old server
   • Confirm that ECP and OWA work on the new server with the old server powered off only after:
     • Verifying SharedWebConfig.config is present in both required directories.
     • Reinstalling the latest security update if 500 errors started after patching.
     • Ensuring the server is on a supported and up-to-date CU that includes the ECP fixes mentioned above.
   • After these checks and fixes, retest https://localhost/ecp on the new server with the old server powered off.

If any of these checks fails (missing SharedWebConfig, outdated CU, or failed update), correct that on the new server first; otherwise, ECP will continue to depend indirectly on components that are only working correctly while the old server is online.

---

References:

• Event ID 1309 and you can't access OWA and ECP after you install Exchange Server 2016 or Exchange Server 2013
• Fix failed Exchange Server updates
• Exchange Control Panel (ECP) redirection fails in Exchange Server 2016
• HTTP 500 error when an administrator tries to manage regional settings in ECP on Windows Server 2016