Outlook Web Access 500 Error
Contents |
2, 20153 Share 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 owa 500 error exchange 2013 cases is "Does the admin account have a mailbox"? In pretty much every case that I owa error 500 exchange 2010 can remember, the response is "No". And immediately, I know exactly where to look! A little history… As you may know, because of microsoft forms based authentication service 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 forMicrosoft Forms Based Authentication Service Exchange 2013
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 Outlook profile for an Exchange 2013 mailbox: http 500 internal server error exchange 2013 ecp
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 Management Shell is your friend as you will need to determine whether the database is moVIP Managed PKI Service VIP Access Manager Small Business Endpoint Protection Cloud Ghost Solution Suite Endpoint Encryption SSL/TLS Certificates Code Signing Norton Shopping Guarantee SHOP ONLINE Website Security SSL Certificates Complete Website Security Code exchange 2013 ecp error 500 after login Signing Certificates Norton Shopping Guarantee Buy SSL Products A-Z Services Services Home Business
Exchange 2013 Ecp 500 Unexpected Error
Critical Services Consulting Services Customer Success Services Cyber Security Services Education Services Solutions Solutions Home Intelligent Solutions Intelligent Endpoint
Http 500 Internal Server Error Exchange 2016
Intelligent Cyber Operations Intelligent Data Protection Intelligent Email Intelligent SMB Blue Coat Solutions Topics Encryption Everywhere Internet of Things Office 365 Security Industries Automotive Cyber Insurance Education Financial Services Global Service Providers https://blogs.technet.microsoft.com/brenle/2015/05/02/http-500-internal-server-error-when-logging-into-exchange-2013-exchange-control-panel-ecp/ Industrial Control Systems Healthcare Retail Government Federal Government State & Local Support Center Symantec Support Blue Coat Support Symantec Connect Buying Programs Upgrading Products Maintenance & Renewals Training Security Center Security Center Home Updates Virus Definitions & Updates Threats, Risks & Vulnerabilities Security Advisories Publications ISTR Blogs Security White Papers Tools Removal Tools Spyware Removal English 中文(简体) 中文(繁體) Česká English Français Deutsch Magyar https://support.symantec.com/en_US/article.TECH123340.html Italiano 日本語 한국어 Polski Português Pусский Español Partner Find a Partner Enroll in a Partner Program Partner Programs Product Resources for Partners Blue Coat Partners Login Required Partner Resources Products A-Z Financial Benefits Partner Licensing Partner Renewals Partner Training United States / English Search Technical Support Support MySymantec Licensing Products A-Z 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 Exchange (SMSMSE) service is run
| My Forums | Address Book | Member List | Search | FAQ | Ticket List | Log Out OWA - http://forums.msexchange.org/OWA_-_HTTP_500_Internal_Server_Error/m_1800390336/tm.htm HTTP 500 Internal Server Error Users viewing this topic: none Logged in as: Guest Tree Style Printable Version All Forums >> [Microsoft Exchange 2003] >> Outlook Web Access >> OWA - HTTP 500 Internal Server Error Page: [1] Login Message << Older Topic Newer Topic >> OWA - HTTP 500 Internal Server Error - 12.Nov.2005 9:56:46 exchange 2013 PM tolinrome Posts: 3 Joined: 12.Nov.2005 Status: offline I am unable to get into Outlook Web Access in Exchange Server 2003. All the Exchange 2003 services start fine. This is our setup: We have 1 Exchange 2003 Server installed as Front End with SSL Certificate. We have another Exchange Server Back End in a Cluster with exchange 2013 ecp all the mailboxes/Public Folders on the backend server. All are running on Windows Server 2003 Enterprise SP1. Exchanger Servers have SP2. OWA works fine on the backend servers no problem. We get the SSL login prompt ok, but then get the "HTTP 500 Internal Server Error". We downloaded and performed every step in the MS KB Article 823159 which addresses this issue but nothing has resolved the problem. We've read almost every post on this problem and cant seem to figure it out. I unmounted the mailboxes and remounted. There is no DMZ, everything is on the same network and subnet and pingable. Remember backends are on a clustrer. Any suggestions Please? THANKS! Post #: 1 Featured Links* RE: OWA - HTTP 500 Internal Server Error - 12.Nov.2005 10:35:04 PM consultOz Posts: 926 Joined: 11.Mar.2005 From: Virginia, USA Status: offline I am not sure if you guys have seen this http://support.microsoft.com/kb/841561 =========================================== This problem is caused by some of the security enhancements that are included with Windows Server 2