Forum Discussion
Exchange 2016 EAC redirects to OWA
Hi All
Hope everyone is keeping safe. Please can someone assist me with the following issue. For some reason I can no longer access the EAC on my Exchange 2016 server. I have tried different browsers and PCs but the result is still the same. I can get to the login screen and enter my details but then it gives an error. Refer to the attached images. Now I recently made a change to the OWA and ECP virtual directories because onboarding mailboxes to Office 365 was a problem. Not too sure if that broke something. I have rebooted the server since making those changes to the virtual directories.
- Hello Navishkar,
These are from the EWS but could you check them for the OWA and ECP directories?
And do they match with IIS?
Also, could you recycle the IIS sites?
- BemmelenPatrickIron ContributorHello Navishkar,
I would suggest to set the correct permissions on the ECP and OWA virtual directory:
https://docs.microsoft.com/en-us/exchange/clients/default-virtual-directory-settings?view=exchserver-2019
And then recycle the ECP and OWA app pool via Application Pools in IIS, you can refer to this article on where to find App Pools.
Of course you shouldn't set a schedule for this.
https://docs.microsoft.com/en-us/iis/configuration/system.applicationhost/applicationpools/add/recycling/#how-to
It's also strange that onboarding didn't work properly, I would advice you to use the Office 365 ECP (outlook.office365.com/ecp) to create migration batches as the ECP within Exchange doesn't work properly sometimes (experienced this myself as well). - Navishkar SadheoSteel ContributorI forgot to add the most important bit. Currently in coexistence with Exchange 2010.
- BemmelenPatrickIron ContributorHello Navishkar,
On which server is the mailbox of the admin account homed?
If it's placed on the Exchange 2010 server then it could be possible that Autodiscover or the back end virtual directory is not functioning properly.- Navishkar SadheoSteel Contributor
Hi there. I moved the admin mailbox to the 2016 server however that still didn't solve the problem. Been doing a lot of reading and it seems like definitely the authentication settings on the OWA and ECP virtual directories I changed recently.