Owa Http 500 Internal Server Error Exchange 2010
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 owa 500 error exchange 2013 server error Exchange Server > Exchange Server 2013 - Outlook, OWA, POP, and microsoft forms based authentication service IMAP Clients Question 0 Sign in to vote We have 2 Exchange 2010 servers that have been in restart owa service exchange 2010 place and working great for about 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
What Services Does Owa Use
area and so all equipment had to be 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 microsoft forms based authentication service exchange 2013 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? 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 her
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 http 500 internal server error exchange 2013 ecp error when attempting to log in to ECP:
The firstExchange 2010 Owa Err_response_headers_truncated
question I ask when I get these specific cases is "Does the admin account have a mailbox"? In
Exchange 2013 Ecp Error 500 After Login
pretty 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 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 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 for a number of reasons in Exchange 2013 connectivity. The most obvious, though, are: As mentioned above, so that https://blogs.technet.microsoft.com/brenle/2015/05/02/http-500-internal-server-error-when-logging-into-exchange-2013-exchange-control-panel-ecp/ 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 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}Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow http://serverfault.com/questions/226055/error-when-using-owa-access-to-mail-server-exchange-2010/226422 the company Business Learn more about hiring developers or posting ads with us Server Fault http://www.winsysadminblog.com/2011/05/blank-page-auth-owa-http-500-when-logging-into-outlook-web-access-running-on-exchange-2010/ Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top error when using OWA access to exchange 2013 mail server exchange 2010 up vote 0 down vote favorite Suddenly it will come out the below error when accessing the exchange 2010 mail server using OWA after clicking sign in button on initial page? ***The website cannot display the page HTTP 500 Most likely causes: •The website is under maintenance. •The website has a programming error. What you can try: Refresh the page. Go back to the previous page. More information This http 500 internal error (HTTP 500 Internal Server Error) means that the website you are visiting had a server problem which prevented the webpage from displaying. For more information about HTTP errors, see Help.* Any suggestion? Thanks! exchange-2010 share|improve this question asked Jan 24 '11 at 8:19 e0594cn 631513 add a comment| 4 Answers 4 active oldest votes up vote 2 down vote On the exchange server, check the services list to check if all related services are running. If not, check the event log as to why they won't run. share|improve this answer answered Jan 24 '11 at 23:40 DutchUncle 1,185715 1 You could also try the brilliant Test-ServiceHealth cmdlet. –Ben Pilbrow Jan 24 '11 at 23:43 add a comment| up vote 2 down vote I was having this same issue and the Microsoft Exchange Forms-Based Authentication Service failed to automatically start. As soon as I started up this service, OWA started working again. share|improve this answer answered Apr 19 '12 at 15:15 Ben Swift 211 add a comment| up vote 2 down vote Most likely, you are running SBS Server. Go to Services and start Microsoft Exchange Forms-Based Authentication service. Hope this helps, from some one who has the same problem. share|improve this answer edited Oct 18 '12 at 8:52 itsbruce 1689 answered Oct 16 '12 at 22:55 igroek24
Http 500) when logging into Outlook Web Access running on Exchange 2010 Recently had to restart a client's server after running some Windows Updates. A few hours after the restart the client contacted me stating that they couldn't access their e-mails via the web. I quickly had a look, the login page presented itself, so I logged in and after clicking Sign in I was presented with a blank page pointing to auth.owa. This was a little puzzling as there were no updates for Exchange so why did it break? Checking the IIS logs, I found that the error was 500 which indicated some kind of authentication error. A little powershell cmdlet you can run is Test-OWAConnectivity. So I ran the cmdlet and recieved WARNING: An unknown failure occurred during logon. So I checked IIS and ensured that all of the authentication was set correctly and indeed it was. So after some poking around on the web I found out Exchange 2010 palms off the Forms Based Authentication to a seperate Service called Microsoft Exchange Forms-Based Authentication Service. Starting this service fixed the blank page issue and allowed clients to authenticate correctly. Share this post with others:EmailLinkedInFacebookGoogleTwitterRedditMorePrintTumblrPinterest Related 71,003 views Posted on May 8, 2011June 19, 2011 by John 74 Comments Posted in Exchange Server, Office 2010 Post navigation How to Switch from IDE to AHCI without repairing/reinstalling Windows How to reset the Search Index in Exchange 2010 Search 74 thoughts on “Blank page (auth.owa Http 500) when logging into Outlook Web Access running on Exchange 2010” ananda says: Thank you very much! [Reply] Reply July 2, 2011 at 4:49 am Andrew says: Thank you for the post. It helped me! [Reply] Reply July 17, 2011 at 1:53 am Jordan says: Worked for me as well….that service it set to start automatically but it wasnt started??? [Reply] Reply July 18, 2011 at 1:26 pm C