Exchange Owa 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 error when attempting to log in to ECP:
The first question I ask when I getExchange 2010 Owa 500 Internal Server Error
these specific cases is "Does the admin account have a mailbox"? In pretty much every http/1.1 500 internal server error owa case that I can remember, the response is "No". And immediately, I know exactly where to look! A little history… As you
Owa Error 500 Exchange 2010
may know, because of 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 microsoft exchange forms based authentication service GUID, and is used for a number of reasons in Exchange 2013 connectivity. The most obvious, though, are: As mentioned above, so that 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 http 500 internal server error exchange 2013 ecp 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} Note: When pulling up the system mailbox(es) using Get-Mailbox you must specify the -Arbitration parameter or the command will not work. So how do I fix this? Typically, what I've found is that this is caused by either the database with the system mailbox is unavailable, or some attribute on the system mailbox account has become corrupt or is missing. Many times, this issue is accompanied by another - such as users unable to connect to Exchange, and the 500 error is discovered when the admin attempts to log in to ECP to try and figure out what is wrong. In this case, Exchange ManagePKI Service Identity Access Manager Shop Online Cyber Security Services Managed Security Services DeepSight Intelligence Incident Response Security Simulation Website Security SSL Certificates Complete Website Security Code Signing
Microsoft Forms Based Authentication Service Exchange 2013
Certificates Norton Shopping Guarantee Buy SSL Products A-Z Services Services Home exchange 2013 ecp 500 unexpected error Business Critical Services Consulting Services Customer Success Services Cyber Security Services Education Services Solutions Solutions Home Topics
Exchange 2013 Ecp Error 500
Encryption Everywhere Internet of Things Next Generation Endpoint Office 365 Industries Automotive Cyber Insurance Education Financial Services Global Service Providers Industrial Control Systems Healthcare Retail Government Federal Government https://blogs.technet.microsoft.com/brenle/2015/05/02/http-500-internal-server-error-when-logging-into-exchange-2013-exchange-control-panel-ecp/ State & Local Support Center Technical Support Symantec Connect Buying Programs Upgrades Maintenance & Renewals Training Security Center Security Center Home Blogs ISTR Threats Virus Definitions and Security Updates Removal Tools Partner Find a Partner Become a Partner Login Required Login into Partner Portal Partner Licensing Partner Renewals Partner Training Margin Builder Opportunity Registration Financial Benefits English https://support.symantec.com/en_US/article.TECH123340.html 中文(简体) 中文(繁體) Česká English Français Deutsch Magyar Italiano 日本語 한국어 Polski Português Pусский Español Site: Symantec Enterprise Small Business Norton United States Search Support Home Support Home MySymantec Licensing Products A-Z SYM16-015 Security Advisory Login Profile Subscriptions Logout Login Forgot Password? Don't have a SymAccount? Create a SymAccount now!' Outlook Web Access (OWA) Returns "500 internal server error" When Attempting to Attach Files Larger Than One (1) Megabyte with Symantec Mail Security for Microsoft Exchange (SMSMSE) Running TECH123340 May 6th, 2014 http://www.symantec.com/docs/TECH123340 Support / Outlook Web Access (OWA) Returns "500 internal server error" When Attempting to Attach Files Larger Than One (1) Megabyte with Symantec Mail Security for Microsoft Exchange (SMSMSE) Running Did this article resolve your issue? Thank you for your feedback! Provide feedback on this article Request Assistance Print Article Products Subscribe to this Article Manage your Subscriptions Search Again Situation Whenever I try to attach items larger than 1 megabyte to an Outlook Web Access (OWA) email and the Symantec Mail Security for Micros
»exchangeservercommentsWant to join? Log in or sign up in seconds.|Englishlimit my search to /r/exchangeserveruse the following search parameters to narrow your results:subreddit:subredditfind submissions in "subreddit"author:usernamefind submissions by "username"site:example.comfind submissions from https://www.reddit.com/r/exchangeserver/comments/40i9m5/exchange_2013_owaecp_500_internal_server_error/ "example.com"url:textsearch for "text" in urlselftext:textsearch for https://ril3y.wordpress.com/2014/03/25/exchange-2013-owa-and-ecp-logins-fail-with-500-error/ "text" in self post contentsself:yes (or self:no)include (or exclude) self postsnsfw:yes (or nsfw:no)include (or exclude) results marked as NSFWe.g. subreddit:aww site:imgur.com dogsee the search faq for 500 internal details.advanced search: by author, subreddit...this post was submitted on 11 Jan 20161 point (67% upvoted)shortlink: remember mereset passwordloginSubmit a linkSubmit a text postexchangeserversubscribeunsubscribe4,943 readers~6 users here nowSearching /r/ExchangeServer Posting Guidelines-PLEASE READ BEFORE POSTING Questions MS KB 500 internal server / Updates Exchange Blogs The Microsoft Exchange Team Blog MSExchange.org Exchange Server Pro Ashdrewness Blog Exchange Troubleshooting Blog Jetze Mellema Blog Exchange Clustering / DAG Blog Exchange & O365 Blog Tony Redmond Dave Stork's Blog Exchange Dev The EXPTA Blog 250 Hello Exchange Tips Exchange References Exchange 2010 Technet Videos Exchange Webcasts and Podcasts Technet Mag Exchange Queue and A Microsoft TechCenter - Exchange Exchange Technet Library Exchange Virtual Labs - Exchange 2010 free Exchange 2013 Hyper-V Best Practices Guide Exchange Deployment Assistant ISA / TMG / UAG References Exchange Podcasts Exchange Server
crash a few times while running diagnostics, OWA and ECP logons started showing an error. 500 Unexpected Error :( An error occurred and your request couldn't be completed. Please try again. Reseting 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: 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)