Owa Error 500 After Login
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 owa error 500 exchange 2010 > Exchange Server 2013 - Outlook, OWA, POP, and IMAP Clients Question 0
Microsoft Forms Based Authentication Service
Sign in to vote We have 2 Exchange 2010 servers that have been in place and working great for about http 500 internal server error exchange 2013 ecp 15 months. We have 1 Windows 2008 Domain Controller and 2 older Windows 2003 Domain controllers. Earlier today we had power go out in our area and so all equipment had to be microsoft forms based authentication service exchange 2013 shut down. After power was restored I began to power everything back up. I power 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
Exchange 2013 Ecp 500 Unexpected Error
internal server error". I don't see any errors or issues. I don't know where to start looking. Can someone help me out? 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 fo| general In November 2013, Cumulative Update 3 was released for Exchange Server 2013. This update resolved many issues with Exchange Server and exchange 2013 ecp error 500 proved to be advantageous for both Administrator and clients. However, the users can encounter http 500 internal server error exchange 2016 various issues with the Cumulative Updates. Issues With Cumulative Updates of Exchange Server 2013 With Cumulative or some other updates, the
Exchange 2016 Ecp Error 500
users can come across 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 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 reference from the registry Issues 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 http://www.blog.edbtopst.org/ecp-and-owa-login-fails-with-error-500-in-exchange-2013.html 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 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
To Tagged with application pool, CAS server, CPI Solutions, eas, ECP, error 500, Exchange 2013, Exchange Server, HTTP 500 Error, http://cpisolutions.com/blog/how-to-resolve-exchange-2013-http-500-error-for-users-in-owaecp/ iis, IT Consulting, Microsoft Exchange, Microsoft Exchange 2013, Microsoft Exchange Server, Microsoft Exchange Server 2013, Microsoft Solutions, Microsoft Support, Microsoft Technology, Microsoft Technology Solutions, owa, Troubleshooting Spread the love Exchange 2013 http http://www.networksteve.com/exchange/topic.php/Exchange_2013_error_500_by_accessing_ECP_as_admin/?TopicId=41047&Posts=18 500 error for some in OWA/ECP I had a client contact me and said there were a handful of users that were experiencing a 500 Error when logging into the OWA and/or error 500 ECP in 2013 Exchange. All other users were fine and had no issues. Exchange Server 2013 w/ SP1 Troubleshooting Let’s recreate the user experience. Checked to see if the user could access the OWA using IE – result error 500 Checked to see if the user could access the OWA using Firefox – result error 500/ blank screen Checked to see if the user exchange 2013 ecp could access the OWA using Chrome – Result user was able to login to owa sometimes Checked to see if the user could access the OWA using IE on another computer – result error 500 Checked to see if the user could access the OWA using Firefox on another computer – result error 500/ blank screen Checked to see if the user could access the OWA using Chrome on another computer – result error 500/ blank screen Application Pool Recycling Below is an exercise we will be go through that will refresh the IIS cache on the CAS server. Logged into the CAS server and opened the IIS MMC Navigated to the Application pools Right-clicked on the MSExchangeSyncAppPool and selected recycle Right-clicked on the MSExchangeSyncAppPool and selected stop Right-clicked on the MSExchangeOWAAppPool and selected recycle Right-clicked on the MSExchangeOWAAppPool and selected stop Right-clicked on the MSExchangeECPAppPool and selected recycle Right-clicked on the MSExchangeECPAppPool and selected stop Closed the IIS MMC Reopened the IIS MMC and waited a few minutes Right-clicked on the MSExchangeSyncAppPool and selected Start Right-clicked on the MSExchangeOWAAppPool and selected Start Right-clicked on the MSExchangeECPAppPool and selected Start ***NOTE:
and also the options-page is well available not so by accessing it as "admin" because of the "error 500". The same occurs by accessing ECP directly via https://cas/ecp: after passing of credentials the normal options-page occurs for each user not so for the admin. January 8th, 2015 9:31am Can you explain "admin" do you mean any domain admin? Try going to the ecp page locally on the cas server so you can get a detailed description of the 500 error. Free Windows Admin Tool Kit Click here and download it now January 8th, 2015 9:48am With "admin" I mean the domain administrator account which is the ECP-admin too. I see no special errors by accessing ecp page locally. Just "HTTP 500: internal Server error January 8th, 2015 10:10am Strange. After few hoursit worksagain on the CAS locally, but only locally. I have absolutely no idea what the problem is... Free Windows Admin Tool Kit Click here and download it now January 8th, 2015 10:30am Check your app event logs on your CAS server it should have something there regarding the failed login. January 8th, 2015 1:49pm I see several errors, e.g.: 1006: Der Postfachreplikationsdienst von Microsoft Exchange konnte Auftrge in einer Postfachdatenbank nicht verarbeiten. Datenbank: Fehlende Datenbank (a3634ca3-02bd-4072-bb02-a4e386f24b12) Fehler: Die Datenbank 'a3634ca3-02bd-4072-bb02-a4e386f24b12' ist nicht vorhanden. Looks like I had to check for the requests regarding this database and to suspend them appropriately..? Free Windows Admin Tool Kit Click here and download it now January 8th, 2015 2:06pm I don't think the 1006 errors have anything to do with it, you don't see any specific errors relating to login? January 8th, 2015 2:15pm No, I don't see any Login-Errors, but a lot of other onesregarding this no more existing database, e.g. 10002, 6002, 36888, 36874 etc. Allthough I don't know whetherthey caused my problem, I believe, my next steps should go to fix the last first. Any Idea how to find out and remove all the activities related to this GUID-database? Free Windows Admin Tool Kit Click here and download it now January 8th, 2015 2:22pm Just a sanity check, the admin account is a mailbox enabled user? January 8th, 2015 2:38pm Yes it is a mailbox enabled user. Sanity check - pls stand by... Free Windows Admin Tool Kit Click here and download it now January 8th, 2015 2:57pm There ist something very very strange and I have absolutely no idea what it