Owa 500 Error Exchange 2013
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 exchange 2013 ecp 500 unexpected error when attempting to log in to ECP:
The first questionExchange 2013 Ecp 500 Error
I ask when I get these specific cases is "Does the admin account have a mailbox"? In pretty
Exchange 2016 Ecp Error 500
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 the
Exchange 2016 Ecp 500 Unexpected Error
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 an Exchange 2013 exchange 2013 http 500 internal server error ecp 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} Note: When pulling up the| 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 exchange 2016 http 500 internal server error advantageous for both Administrator and clients. However, the users can encounter various issues with microsoft exchange forms based authentication service the Cumulative Updates. Issues With Cumulative Updates of Exchange Server 2013 With Cumulative or some other updates, the users can come across microsoft forms based authentication service exchange 2013 some difficulties after the installation. Some of the issues include: 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 https://blogs.technet.microsoft.com/brenle/2015/05/02/http-500-internal-server-error-when-logging-into-exchange-2013-exchange-control-panel-ecp/ with the certificate Improper updation or breakage of ASP.net In case of Cumulative update 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 http://www.blog.edbtopst.org/ecp-and-owa-login-fails-with-error-500-in-exchange-2013.html following errors will be generated: Event ID: 4 & 1309 : caused due to ASP.net Error 500: caused due to 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 f
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 http://www.msexchange.org/blogs/walther/news/exchange-2010-sp1-experiecing-an-owa-http-500-error-554.html credentials and then boom it throws an “HTTP 500” error instead 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 exchange 2013 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 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 exchange 2013 ecp instead 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