A client with Exchange 2013 on premise server complained about not been able to access Outlook web access both internally and over the internet with “Access is Denied” error. We checked out the server and validated the issue exist, we also found that we are also not able to open ECP (Exchange Control Panel) URL with the same “Access is Denied” error.
Error while accessing OWA:
=== Server Error in ‘/owa’ Application. —————– Access is denied.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.ServiceModel.Security.SecurityAccessDeniedException: Access is denied. Source Error:
This error can only be revealed in debug mode and for that please add “Debug=true” directive at the top of the file that generated the error. Example:
<%@ Page Language=”C#” Debug=”true” %>
PS: Applications in debug mode are memory intensive, disable it as soon as you are done with the troubleshooting
Error while accessing ECP:
Server Error in ‘/ecp’ Application. ——————————————————————————– Access is denied. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.ServiceModel.Security.SecurityAccessDeniedException: Access is denied. Source Error: An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace: [SecurityAccessDeniedException: Access is denied.]
We troubleshoot the issue further and found that all the MSExchangeApplicationpool Identity set incorrectly, we followed the following steps to resolve the issue.
- Open IIS Manager.
- Go to Application pools
- Right click on the app pool name and pull up Advanced Settings
- Select Built-in account option and switch all the Exchange related applications pool to “Local System”
- Perform IISRESET
After this OWA and ECP were working OK for us and hopefully it will fix it for you too, else feel free to reach out to our paid support options Here
Latest posts by Shishir Chandrawat (see all)
- Exchange 2010 Std: Mailbox server has reached the maximum database limit of 5 Error RcrExceedDbLimitException - December 12, 2016
- Exchange 2010: Unable to add Mailbox Database copies on DAG member servers, Error: An error occurred while processing a request on server - December 12, 2016
- Unable to Mount Microsoft Exchange DAG Database, Error: Failed to determine the mount status of the active database copy - December 12, 2016
your magic…thanks
Beating my head against the wall with an Exchange 2016 rollout. Had some issues and was reviewing the IIS BPA and it recommended changing all of those Application Pools to run under the ApplicationPoolIdentity. I changed all of the MSExchange app pools to run under that. While I got one issue resolved it caused many others. Thanks for posting this.
Hello Marshall
Thanks for reaching out to us. What we provide on grishbi is best of our knowledge so far, if the given information is not enough to solve the issue, I request you to open a paid support incident with us by dropping an email at support@pledgetechnologies.com. We will be more than happy to resolve the issue for you
Regards
Shishir