Read time: 5 minutes
The Exchange admin center (EAC) is the modern-day web-based management console for managing recent versions of the Exchange Server. It replaces the Exchange Control Panel (ECP), which allows you to control your mail settings. There are times when you try to launch EAC, and you’re stopped by a message saying, “Could not load file or assembly.”
This means you ‘cannot access ECP on new Exchange 2019 server,’ and further communication won’t be possible.
In many cases, this ECP issue appears after a cumulative update, Exchange migration, certificate replacement, or IIS configuration change. The error may also stop access to EAC and OWA, which directly affects Exchange administration tasks.
There are chances that errors can crop up when you migrate or update the previous version of your Exchange Server to the recent one. One such errors we found while running EAC after the update is mentioned here:
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.
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>
In this blog, we’ll give the best approaches for efficient Exchange database recovery and the reasons why this error occurs while working on Exchange Server.
Why does the ‘’Cannot access ECP on new Exchange 2019 Server’’ error occur?
Several things can result in this ECP inaccessibility error. Some common reasons include:
- Admin mailbox missing: Either the administrator doesn’t have any mailboxes in Exchange 2019, or there’s an issue with the configuration of Arbitration mailboxes.
- Certificate issues: The OAuth/Auth certificate assigned to your Exchange mailbox has expired.
- Security updates: Recent security updates and bug fixes can also cause errors with the ECP.
- Corrupt configuration file: Corruption in the configuration file can cause cannot access ECP error.
- IIS services stopped: Exchange IIS application pools or related services may stop after updates or server restarts.
Methods to Fix “Cannot Access ECP on New Exchange 2019 Server” Error
When you find an issue like this, there is never a single cause behind it. You need to check what the actual issue is with different approaches and then find a solution to fix cannot access ECP on new Exchange 2019 Server and repair EDB files. Here are the conditions you must verify to resolve the issue:
Check Whether OWA Works Properly
Outlook Web Access, or Outlook on the Web, is a web-based email client that allows users to send and receive email messages just like MS Outlook. Before you proceed to find a solution to fix the error, validate if OWA in your MS Office 365 is working.
Sometimes, OWA and EAC become inaccessible after a Cumulative Update (CU) or migration to an updated version. However, if OWA is working completely fine, there is a problem with the EAC mainly.
Test ECP Access with Another Browser and Admin Account
Try accessing the Exchange admin center with other admin accounts, different web browsers, and local servers in your organization. It will provide a clear picture of the issue, showing if the error is in one single account or the EAC of your Office 365 account.
Check EcpVirtualDirectory
If the virtual directory appears corrupted, recreate it with Exchange Management Shell and run IISRESET afterward. Also, verify authentication settings and SSL bindings in IIS Manager.
The ECP Virtual Directory works for the on-premises Exchange. Use the command “Get-EcpVirtualDirectory” to view the ECP Virtual Directory used in the Internet Information Services of Microsoft Exchange.
The Exchange Control Panel Virtual Directory is used in EAC. The EAC virtual directories and the connected cmdlets in Exchange Server 2013 and Exchange Server 2016 still have ECP in the name. You can use the cmdlets for ECP virtual directory management on Exchange 2010, 2013, and 2016 servers.
Run the following syntax in the Power management shell:
The command won’t provide output if you do not have the required permissions assigned to your account, so make sure to have them before running it.
Did you migrate from Exchange 2013 to Exchange 2019?
Sometimes, when you migrate from Exchange 2013 to Exchange 2019, the arbitration mailboxes remain untouched. This can become a hurdle to access the admin center in the updated Exchange.
Arbitration mailboxes are the system mailboxes that require migration before moving to the recent version of the Exchange server. These mailboxes store organizational data, such as audit logs and unified messaging data. Move your arbitration mailbox to Exchange 2019 or create a local mailbox on Exchange 2019 and make it the organization admin.
Check Exchange Services and IIS Application Pools
Sometimes, ECP becomes inaccessible because Exchange-related IIS services stop automatically after updates or failed configuration changes. Verify that the following services are active:
- World Wide Web Publishing Service
- IIS Admin Service
- MSExchangeServiceHost
- MSExchangeFrontEndTransport
- MSExchangeIS
Also, check whether the MSExchangePowerShellAppPool runs properly in IIS Manager.
Limitations of Manual Methods
- Require advanced Exchange Server technical knowledge.
- Incorrect changes may break Exchange services.
- An IIS reset may create temporary mailbox access issues.
- Manual troubleshooting consumes significant admin time.
- PowerShell commands may fail due to permission errors.
- Certificate configuration mistakes may create new errors.
- High risk of data accessibility problems during troubleshooting.
Professional Solution to Recover Exchange Database and Restore Access
When manual methods fail, or Exchange databases become inaccessible after ECP errors, a professional Exchange recovery tool helps restore mailbox data without complex PowerShell commands. Kernel for EDB to PST Converter supports Exchange recovery, mailbox export, and migration to live Exchange or Microsoft 365 environments.
Recover or migrate your data with the help of an advanced EDB to PST Converter tool. The tool supports easy data migration from one Exchange Online to another, converts EDB to PST and other destinations, and recovers lost databases and mailboxes. Also, this tool is the perfect choice for migration of corrupt EDB files with 100% accuracy.
Conclusion
The “Cannot access ECP on new Exchange 2019 Server” error usually appears because of IIS issues, certificate problems, broken virtual directories, or incomplete Exchange migration. Start with basic checks like OWA access, Exchange services, browser validation, and ECP virtual directory verification. If the issue continues after manual troubleshooting, use a professional Exchange recovery solution to restore mailbox access and migrate Exchange data safely without downtime.
Frequently asked questions
Ans. Exchange cumulative updates may change IIS settings, authentication configuration, or Exchange services. This can block ECP and OWA access until services, certificates, or virtual directories are corrected.
Ans. Yes. An expired, invalid, or incorrectly assigned SSL certificate can stop ECP and EAC access. Verify IIS bindings and Exchange certificate assignments through Exchange Management Shell.
Ans. Recreating the ECP virtual directory helps when configuration files become corrupted. However, take a backup before changes and verify IIS authentication settings after recreation.
Ans. Open Services.msc and confirm Exchange and IIS-related services are active. Restart stopped services and recycle IIS application pools if ECP fails to load properly.
