Exchange Owa Http 500 Internal Server Error
Contents |
2, 20153 0 0 0 Over the past several months, I've seen an increased number of Exchange 2013 cases where certain admin users received a 500 status http 500 internal server error exchange 2007 owa error when attempting to log in to ECP:
The firstHttp 500 Internal Server Error Exchange 2013 Owa
question I ask when I get these specific cases is "Does the admin account have a mailbox"? In http 500 internal server error exchange 2013 ecp pretty much every case that I can remember, the response is "No". And immediately, I know exactly where to look! A little history… As you may know, because of http 500 internal server error iis7 the design of Exchange 2013 - the CAS role simply locates your mailbox, then proxies the request back to your mailbox server - an "anchor mailbox" is used. This anchor mailbox is simply your Exchange GUID, and is used for a number of reasons in Exchange 2013 connectivity. The most obvious, though, are: As mentioned above, so that
Http 500 Internal Server Error Apache
an Exchange 2013 CAS knows what mailbox server to proxy a request to To prevent the 'Your administrator has made a change so you must restart Outlook' message that you get when a mailbox is moved to a different site. You can see evidence of the anchor mailbox when you configure an Outlook profile for an Exchange 2013 mailbox:
Notice the ExchangeGuid is used as the 'Server' in the outlook profile, instead of an actual server name. OK that's great and all, but what does that have to do with thisstatus 500that I'm getting? Well, let's think about it. If the Exchange 2013 CAS needs to know where to proxy a request, but the request is coming from an account that has no mailbox, and thus no ExchangeGuid associated with it, how does Exchange know which mailbox server to proxy? In instances like this, Exchange 2013 uses the ExchangeGuid of system mailboxes to determine where to proxy the requests. In this specific scenario, Exchange uses the system mailbox SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c} Ncrash a few http 500 internal server error iis times while running diagnostics, OWA and ECP logons started showing an
Http 500 Internal Server Error Iis 6
error. 500 Unexpected Error :( An error occurred and your request couldn't be completed. Please try again. Reseting https://blogs.technet.microsoft.com/brenle/2015/05/02/http-500-internal-server-error-when-logging-into-exchange-2013-exchange-control-panel-ecp/ IIS, restarting the servers, clearing cookies etc had no effect. Event 4 appears in the Application log at the time of the login. Current user: 'Example.com/Test User' Request for URL 'https://server01.example.com:444/ecp/default.aspx(https://server01/ecp/)' failed with the following error: System.NullReferenceException: https://ril3y.wordpress.com/2014/03/25/exchange-2013-owa-and-ecp-logins-fail-with-500-error/ Object reference not set to an instance of an object. at Microsoft.Exchange.Clients.Common.Canary15.Init(Byte[] userContextIdBinary, Byte[] timeStampBinary, String logonUniqueKey, Byte[] hashBinary, String logData) at Microsoft.Exchange.Clients.Common.Canary15..ctor(String logonUniqueKey) at Microsoft.Exchange.Clients.Common.Canary15Cookie.TryCreateFromHttpCookie(HttpCookie cookie, String logonUniqueKey, Canary15Profile profile) at Microsoft.Exchange.Clients.Common.Canary15Cookie.TryCreateFromHttpContext(HttpContext httpContext, String logOnUniqueKey, Canary15Profile profile) at Microsoft.Exchange.Management.ControlPanel.CanaryExtensions.CheckCanary15(HttpContext context, Boolean shouldRenew, String canaryName) at Microsoft.Exchange.Management.ControlPanel.CanaryExtensions.CheckCanary(HttpContext context) at Microsoft.Exchange.Management.ControlPanel.RbacModule.Application_PostAuthenticateRequest(Object sender, EventArgs e) at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) at Microsoft.Exchange.Clients.Common.Canary15.Init(Byte[] userContextIdBinary, Byte[] timeStampBinary, String logonUniqueKey, Byte[] hashBinary, String logData) at Microsoft.Exchange.Clients.Common.Canary15..ctor(String logonUniqueKey) at Microsoft.Exchange.Clients.Common.Canary15Cookie.TryCreateFromHttpCookie(HttpCookie cookie, String logonUniqueKey, Canary15Profile profile) at Microsoft.Exchange.Clients.Common.Canary15Cookie.TryCreateFromHttpContext(HttpContext httpContext, String logOnUniqueKey, Canary15Profile profile) at Microsoft.Exchange.Management.ControlPanel.CanaryExtensions.CheckCanary15(HttpContext context, Boolean shouldRenew, String canaryName) at Microsoft.Exchange.Management.ControlPanel.CanaryExtensions.CheckCanary(HttpContext context) at Microsoft.Exchange.Management.ControlPanel.RbacModule.Application_PostAuthenticateRequest(Object sender, EventArgs e) at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at Syste
Neal (Exclaimer) Sales & Marketing Manager GROUP SPONSORED BY EXCLAIMER See more RELATED PROJECTS Wintel To deploy, troubleshoot and administer Windows Servers https://community.spiceworks.com/topic/371754-exchange-owa-http500-internal-server-error and maintain 15 sites at different locations. Handle deployment of security patches via SCCM 2007 r2. Taking care of 250+ Servers and 6 domains. Increase Email Database Registering Canadians to be Organ https://exchangequery.com/2015/05/13/exchange2013-unable-to-access-ecp-encounter-500-unexpected-error/ Donors and representing a Canadian Registered Charity. This Project This is a project I worked on and liked TECHNOLOGY IN THIS DISCUSSION Microsoft Exchange Server 2010 Join the Community! http 500 Creating your account only takes a few minutes. Join Now Urgent problem here. Everything was working fine this morning until around 1130am when owa went down. Users are able to connect to their mailboxes through outlook and smartphones correctly. When I attempt to login to the owa website, it brings up the login page, enter my username and password, and it immediately goes http 500 internal to a "The website cannot display the page" screen. The error is for "HTTP 500 Internal Server Error". I have already tried resetting my virtual directory for owa with the same error. I don't know what to do to fix this problem. Reply Subscribe View Best Answer RELATED TOPICS: 500 internal server error 500 Internal Server Error 500 Internal Server Error   8 Replies Datil OP Sean Donnelly Aug 19, 2013 at 6:02 UTC What version of Exchange are you running? Also any Exchange related errors in the App or System Event Logs? 0 Anaheim OP Best Answer Ford_TX Aug 19, 2013 at 6:13 UTC LaConterra HelpDesk is an IT service provider. Make sure that the Microsoft Exchange Forms Based Authentication service is started. You may also want to restart the MS Exchange System Attendant and Information Stor services along with the IISadmin service. 1 Anaheim OP JayOKeefe Aug 19, 2013 at 6:41 UTC Thanks guys. Simple answer.. Forms Authentication service stopped.. 0 Anaheim OP Ford_TX Aug 19, 2013 at 6:46 UTC LaConterra HelpDesk
ecp through an admin delegated account and got the below error. I thought of writing up a blog with few general checklists that can be performed if we come across this kind of issues. Below are the troubleshooting steps that can be performed in this order if we come across issues with accessing the ECP virtual directory. 1) Check if there is any issue with the XAML file type Find the file located in C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\ecp\DDI\RemoteDomains.XAML If you have any staging servers with the same version where it is working just copy this XML file or if you could find this file from the setup just replace with the existing one do an iis reset and see the results 2) Check on the Application Pools to view whether OWA and ECP Application Pool is running on .NET Framework v4.0. It maybe the incompletely or corrupted installation of Framework that causes this error. You might come across the above if you recently made any recent upgrade or its a new fresh installation. If that's the case try to run the following command as Administrator: %windir%\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -i Change the MSExchangeECPAppPool from .NET Framework from v4.0 to v2.0. Then restart IIS and check the results. 3) Check the bindings of the default website to confirm to Microsoft recommended settings: ({http port 80 *}{http port 80 127.0.0.1} {https port 443 *}{https port 443 127.0.0.1}) 4) If none of the above steps works try recreating the ecpvirtualdirectory and see the results In EMS, please run the following command: Remove-Ecpvirtualdirectory –Identity “CAS\Autodiscover (xxxxx)” New-Ecpvirtualdirectory –Identity “CAS\Autodiscover (xxxxx)” There are more cases where even recreating the ECP virtual directory or any virtual directory