In this article, we see how to resolve the Exchange 2013/2016 Cannot Login to ECP or OWA Error.
While working on the system, it’s quite natural to have such an issue; this error may be due to accessing Outlook multiple times in a network. But mostly this happens because of entering an incorrect method for “OWA” and “ECP” Virtual directories.
You might interested in - Exchange Mailbox (.edb) Recovery Tools
How to Rebuild ECP Virtual Directory
Follow the points below:
First, use Remove-ECPVirtualDirectory to remove Exchange Control Panel virtual directories.
Then use New-ECPVirtualDirectory for creating an Exchange Control Panel virtual directory.
To overcome such an issue, follow the workarounds below:
#1. Solution for OWA Virtual Directory
Firstly, open EMS (Exchange Management Shell), after this, run the below given command to change from the authentication method of the OWA Virtual directory to Windows authentication
Second, you have to run the below command on both the application Client Access as well as Mailbox Servers for restarting the Internet Information Services (IIS):
iisreset /noforce
#2. Solution for ECP Virtual Directory
First, open Windows PowerShell.
Then type the command below and then click enter.
After that, again run the below command on both applications, i.e,. Client Access and Mailbox Servers to restart the Internet Information Services, i.e., IIS.
iisreset /noforce
Also, you should avoid performing any changes to the back-end Exchange IIS directories.
However, if required, only the changes that you need to make are for the front-end (CAS) portion of Exchange.