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.
74 thoughts to “Blank page (auth.owa Http 500) when logging into Outlook Web Access running on Exchange 2010”
Thank you very much!
Thank you for the post. It helped me!
Worked for me as well….that service it set to start automatically but it wasnt started???
Thanks, worked for me. The service was set to start Automatically but had not started as well.
This help me out a lot thanks!!!!
cool worked for me.. i check auth, bindings, recreacted vdir’s almost was thinking of installing latest roll up thinking that this is a themes issue..
Thanks! Very helpful.
Whoa, thank you very much! Same issue here, your solution saved my weekend.
Nice – saved me from digging.
I’ve been suffering this problem. Thanks a lot for the workaround. It helped me a lot. Any idea why it is not starting when booting the server.
Great post! Thanks so much!
You really did a good thing, you saved me 🙂
Thanks a lot
Thanks a lot, this helped. has anyone figured out why the service does not start automatically even though set to start automatically?
This happened again the other day on an SBS 2011 Standard Server. There wasn’t anything in the event log about the service not being able to start. I believe it could just be an issue in the way the services start-up. At the time we were removing Hyper-V which could have affected the start-up process.
I love you!!!!!!!!
I’ve reinstalled rollup for hours!
you are great!
Thank you very much. It is resolve my problem.
Thanks, just what I needed.
Thank you for the information, it worked perfectly for me too. Appreciate you sharing what you’ve learned.
Thx great it works!
Thanks for the great tip!
Thanks, it work for me!!!
Thank u, man!
It seems like the only way to resolve this is to set the service startup to automatic with delayed start. Worked for me! Thanks for the great find!
Hi Pete. I’ve actually tried this and it seems to be working fine at the one site this continually happens to me. Good find.
Bro, u really save my ass. thanx alot.!!!
Unfortunately I did not manage to see the service to restart it. I am running Windows Server 2008 R2, and installed Exchange 2010. Please help.
The Server must have the CAS roles installed for the service to be there.
Open up a command prompt window and type in sc query MSExchangeFBA and see what you get.
Saved me a bunch of time! thanks!
Brilliant ! Thanks
Saved my day! Thanks a lot!!
First google result for “outlook OWA http 500”
Thanks a lot man!
After a lot of reinstall/restart of IIS Have finally arrived at your post. Worked well!
THANK YOU!!!! YOU’RE THE MAN!!!
Thanks a lot
Excelente! Me funcionó de inmediato.
Live saver! Thanks!
Wow, I find this 2 years later and it worked for me. I checked all Exchange services, all working, then rebooted the server and the Forms Based Auth service was not running (even when it’s set to Automatic Start). Started the service, checked OWA and working again.
thank you very much this step solve my problem
Thanks So much!! We had an old 2003 server crash today, but shouldn’t have had anything to do with this and it didn’t…
Had me worried till I found this and tried it. Thank goodness for the tech community and sharing or we would all be much worse off and staying places all weekend, in my case at a school.
God Bless you.
Thank you for the post, saved the day
Thanks!!!! Just experienced this with our new Exchange 2010 environment after its first real update. The service was not running on one of our two CAS so OWA was working for some but not others. Thank you again!!!!
This was it! Thanks for the tip 🙂
Worked like a charm. Thanks
Work for me.Thanks !!!!!
THANK YOU! I have been scratching my head on this after a planned server reboot for an appassure agent install…how did I overlook that service? 😛
Thanks very much, it works!!
Thank you sooo much it worked like a charm
And Microsoft managed to screw this up again. There is no such service in Exchange 2013 and I still have the problem.
Thank you , it worked for me … that help me to save my troubleshooting time… Excellent job man
Very helpfull for Exchange 2010
This helped a ton! Not sure why the service stopped but after reading this and restarting the service all is well now 🙂
Thanks for this. Was getting irritated and you were top on the list for a google search.
This has been driving me nuts for days.
Thank you so much mate!!
thanks for the info !
I have since set that service to delayed start, rather than just automatically and it hasn’t not started again!
Thanks a lot !!
Muchas Gracias! Era esto! Despues de toda una mañana buscando por la red…
One of those tiny tips that resolves massive issues with minimum fuss.
It worked! Thank you
You saved my live!!!
Nice One ! saved a lot of messing about
Excellent , it saved my life
Thanks very much! This resolved the issue we were having!
You have no idea how thankful I am to your post, it saved the night.
Saved my day!! Thank you.
Thanks …its work for me
Happened to me after update rollup 15 on exchange 2010 SP3 on CAS server.
Thanks for lowering my blood pressure quick !!