{"id":120245,"date":"2023-01-12T08:53:30","date_gmt":"2023-01-12T08:53:30","guid":{"rendered":"https:\/\/www.stellarinfo.com\/blog\/?p=120245"},"modified":"2025-10-07T06:38:49","modified_gmt":"2025-10-07T06:38:49","slug":"how-to-fix-cannot-access-ecp-on-new-exchange-2019-server-issue","status":"publish","type":"post","link":"https:\/\/www.stellarinfo.com\/blog\/how-to-fix-cannot-access-ecp-on-new-exchange-2019-server-issue\/","title":{"rendered":"How to Fix “Cannot Access ECP on New Exchange 2019 Server” Issue?"},"content":{"rendered":"

Exchange Server administration is done through the Exchange Admin Center (EAC), which is a web-based management console in the recent versions of Exchange Server. In order to administer the Exchange Server, all you need is a browser and access to the server with the right permissions. Sometimes, when accessing the Exchange Admin Center (EAC)<\/strong><\/a>, you are not be able to login and prompted with the configuration error, saying “Could not load file or assembly.”<\/strong><\/p>

When you try to access your Exchange Admin Center from a browser with the typical URL (https:\/\/<serveraddress>\/ecp)<\/strong>, the page doesn’t load and prompts the below error:<\/p>

\"This<\/figure>
Configuration Error
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.<\/code><\/code><\/pre>
The error shows the following details:<\/p>
Parser Error Message: Could not load file or assembly 'Microsoft.Exchange.HttpRedirectModules, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.<\/code><\/code><\/pre>
Source Error:
Line 36: <compilation defaultLanguage=\"c#\" debug=\"false\">
Line 37: <assemblies>
Line 38: <add assembly=\"Microsoft.Exchange.HttpRedirectModules, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35\" \/>
Line 39: <\/assemblies>
Line 40: <\/compilation><\/code><\/code><\/pre>
Source File: C:\\inetpub\\wwwroot\\web.config Line: 38
Assembly Load Trace: The following information can be helpful to determine why the assembly 'Microsoft.Exchange.HttpRedirectModules, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' could not be loaded.<\/code><\/code><\/pre>
=== Pre-bind state information ===
LOG: DisplayName = Microsoft.Exchange.HttpRedirectModules, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
(Fully-specified)
LOG: Appbase = file:\/\/\/C:\/inetpub\/wwwroot\/
LOG: Initial PrivatePath = C:\\inetpub\\wwwroot\\bin
Calling assembly : (Unknown).<\/code><\/code><\/pre>
Let’s see how to troubleshoot and resolve the issue.<\/h2>
Troubleshooting the ‘Cannot Access ECP on Exchange Server’ Issue<\/h3>
First, you need to check if the Exchange Admin Center (EAC) is the only thing which is not working. Check if the Outlook Web Access (OWA) is working on the server or not. If it’s working, then you can assume that the issue is specifically with the EAC.<\/p>
Now, check if the issue is being observed only from a laptop, other server, or the local server. This needs to be tested from a computer joined to the domain and from the server itself. You also need to confirm this with multiple browsers to ensure that there isn’t any specific configuration on the browser which is causing the problem.<\/p>
Permissions also need to be taken into consideration. Although the error says otherwise, it wouldn’t hurt to test it with a different user, which has administrative rights. It may happen that the user you are using to log into the Exchange Admin Center doesn’t have a pre-mailbox.<\/p>
For this, you can try the following:<\/strong><\/p>