Exchange Webmail Error 500
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 get these specific cases isOwa Error 500 Exchange 2010
"Does the admin account have a mailbox"? In pretty much every case that I can remember, exchange 2013 owa error 500 the response is "No". And immediately, I know exactly where to look! A little history… As you may know, because of the design of exchange 2013 owa error 500 after login 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
Owa 2003 Error 500
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 Outlook profile for an Exchange 2013 mailbox:
Notice the ExchangeGuidOutlook Web Access Error 500
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 Management Shell is your friend as you will need to determine whether the database is mounted via shell. In other instances, I've found that system mailbox, foseen this issue a couple of times after applying Exchange 2010 SP1 on Client Access servers. I’m presented with the OWA FBA page and enter my http error 500 owa credentials and then boom it throws an “HTTP 500” error instead of opening
Microsoft Exchange Forms Based Authentication
the mailbox. You tried to issue an “IISReset /NoForce” and even rebooted the server and still see the symptom.So the microsoft forms based authentication service exchange 2013 issues is typically caused by the “Microsoft Exchange Forms-Based Authentication” service being in a stopped state. Starting the service immediately fixes the issue. Why it sometimes doesn’t start automatically after a reboot of https://blogs.technet.microsoft.com/brenle/2015/05/02/http-500-internal-server-error-when-logging-into-exchange-2013-exchange-control-panel-ecp/ the servers is a very good question. I’ll do some more research in order to find the root cause.Until later,Henrik WaltherTechnology Architect/WriterMCM: Exchange 2007 | MVP: Exchange Architecture I’ve seen this issue a couple of times after applying Exchange 2010 SP1 on Client Access servers. I’m presented with the OWA FBA page and enter my credentials and then boom it throws an “HTTP 500” error instead http://www.msexchange.org/blogs/walther/news/exchange-2010-sp1-experiecing-an-owa-http-500-error-554.html of opening the mailbox. You tried to issue an “IISReset /NoForce” and even rebooted the server and still see the symptom. So the issues is typically caused by the “Microsoft Exchange Forms-Based Authentication” service being in a stopped state. Starting the service immediately fixes the issue. Why it sometimes doesn’t start automatically after a reboot of the servers is a very good question. I’ll do some more research in order to find the root cause. Until later, Henrik WaltherTechnology Architect/WriterMCM: Exchange 2007 | MVP: Exchange Architecture See Also Review and Comments Name * Email address * URL * Comment * If you enter anything in this field your comment will be treated as spam * * Required field Kenny K Sun, 12 July 2015 00:17 1000 thank you's your suggestion totally worked. How many times we're looking for the issue in the most complicated places only to find a service failed to start. I feel like an intern right about now... -Ken mgaytan Wed, 24 June 2015 22:51 did you find a root cause? yotks! Sat, 28 Feb. 2015 22:15 tks! it worked! Bahloul Wed, 10 Dec. 2014 10:31 thanks Henrik. See Also Simplifying
| general In November 2013, Cumulative Update 3 was released for Exchange Server 2013. This update resolved many issues with Exchange Server and proved to be advantageous for both Administrator and clients. http://www.blog.edbtopst.org/ecp-and-owa-login-fails-with-error-500-in-exchange-2013.html However, the users can encounter various issues with the Cumulative Updates. Issues With Cumulative Updates of Exchange Server 2013 With Cumulative or some other updates, the users can come across some difficulties after the installation. Some of the issues include: https://support.symantec.com/en_US/article.TECH123340.html Powershell shortcuts get omitted. Virtual Directories Missing of Powershell dll’s OWA, ECP or Active sync do not work properly Missing of reference from the registry Issues with the certificate Improper updation or breakage of ASP.net In case of Cumulative update error 500 3 and above version, the basic functionalities that get hindered are: OWA ECP Indication of the issue On installing Cumulative Update with Exchange Server 2013 and above versions either in DAG or non DAG mode, access to OWA or ECP is denied but it is found that Outlook is working effectively. If case of such scenarios either of the following errors will be generated: Event ID: 4 & 1309 : caused due to ASP.net Error 500: caused due to owa error 500 login failure of OWA or ECP However, both the above mentioned errors can prevail in Exchange Server environment but we will focus on "ECP And OWA Logins Fail With Error 500 in Exchange 2013″ . Let’s now move to the reason due to which this error occurs. Cause Of The Error 500 in Exchange 2013 The main reason behind the log in failure of OWA and ECP is the mismatch of canary tokens between the client and server A canary is usually a secret token between client and Server in OWA, ECP or some other web services that is stored in the cookie collection of the browser and gets submitted with various requests which the browser sends. For each request the value of GUID stored in the URL is compared with the one stored in session state. If the value of GUID stored in these location do not match or if the value of GUID is lost from the URL, the request becomes malicious and it is blocked. As a result of it, the users will encounter “http error message 500: Internal Server Error” and the Server will come across an unexpected condition that stops it from executing the request. Functioning Of Canary Tokens In Normal Condition And At The Time Of Error Generation As mentioned above that the mismatch of canary tokens between the client and the Server is responsible for the generation of error 500. Let
PKI 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 Certificates Norton Shopping Guarantee Buy SSL Products A-Z Services Services Home Business Critical Services Consulting Services Customer Success Services Cyber Security Services Education Services Solutions Solutions Home Topics 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 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 中文(简体) 中文(繁體) Č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 Microsoft Exchang