Outlook Web Access Error 500 Internal Server Error
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeOnline20132010Other VersionsLibraryForumsGalleryEHLO Blog Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: OWA brings up logon screen but after login gives http 500 internal server error Exchange Server > Exchange Server 2013 - Outlook, OWA, owa 500 error exchange 2013 POP, and IMAP Clients Question 0 Sign in to vote We have 2 Exchange 2010 owa error 500 exchange 2010 servers that have been in place and working great for about 15 months. We have 1 Windows 2008 Domain Controller and 2 microsoft forms based authentication service older Windows 2003 Domain controllers. Earlier today we had power go out in our area and so all equipment had to be shut down. After power was restored I began to power everything back up. I power
Microsoft Forms Based Authentication Service Exchange 2013
on the DC's first and on down the line. After powering everything back up I began to check everything. Email works fine using Outlook but I noticed that I could not logon thru OWA. I get to the logon screen fine but after entering my credentials I immediately get "HTTP 500 internal server error". I don't see any errors or issues. I don't know where to start looking. Can someone help me out? http 500 internal server error exchange 2013 ecp HELP!! thanks Thursday, February 07, 2013 10:07 PM Reply | Quote Answers 16 Sign in to vote Solved Sorry for the bother. I found some other posts that led to the fix. Solution: Make sure the Microsoft Forms Based Authentication service is running on all Exchange servers. Marked as answer by Poly Admin Thursday, February 07, 2013 10:21 PM Thursday, February 07, 2013 10:21 PM Reply | Quote All replies 16 Sign in to vote Solved Sorry for the bother. I found some other posts that led to the fix. Solution: Make sure the Microsoft Forms Based Authentication service is running on all Exchange servers. Marked as answer by Poly Admin Thursday, February 07, 2013 10:21 PM Thursday, February 07, 2013 10:21 PM Reply | Quote 0 Sign in to vote Hi Poly Admin, Thanks for sharing. This is very helpful. If you have any feedback on our support, please click here Frank Wang TechNet Community Support
Friday, February 08, 2013 4:38 AM Reply | Quote 0 Sign in to vote Solved Sorry for the bother. I found some other posts that led to the fix. Solution: Make sure the Microsoft Forms Based Authentication service is running on all Exchange servers. Thanks - fixed my problem too! Friday, November 29, 2013 4:52 AM Reply | Quote 0| 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 microsoft exchange forms based authentication service missing both Administrator and clients. However, the users can encounter various issues with the Cumulative Updates.
Http 500 Internal Server Error Exchange 2016
Issues With Cumulative Updates of Exchange Server 2013 With Cumulative or some other updates, the users can come across some difficulties after the
Exchange 2013 Forms Based Authentication Service Missing
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 with the certificate Improper updation or https://social.technet.microsoft.com/Forums/exchange/en-US/8cf6886f-a96f-44f1-88ee-bd3a42349fa9/owa-brings-up-logon-screen-but-after-login-gives-http-500-internal-server-error?forum=exchangesvrclients 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 following errors will be generated: Event ID: 4 http://www.blog.edbtopst.org/ecp-and-owa-login-fails-with-error-500-in-exchange-2013.html & 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 from executing the request. Functioning Of Canary Tokens In Normal Condition And At The Time Of Error
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 http://www.msexchange.org/blogs/walther/news/exchange-2010-sp1-experiecing-an-owa-http-500-error-554.html 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 of the servers is a very exchange 2013 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 of opening the mailbox. You tried forms based authentication 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 the Outlook Web App 2010 URL 11 Sept. 2009 Henrik Walther Office 365: ADFS - S