Session expired when trying to logon to OWA (Forms based auth)
Hello, I recently installed Exchange 07 and got OWA working like I thought it should using forms based authentication, however it seems since the other day I have been seeing "Your session has timed out..... Please re-enter your user name and password. ", when trying to login to any of the accounts. It happens on any machine that I try it from, onsite or off. I created a new account and got the same error. If I use Basic authentication (and I am sure any of the other standard based auth options) it works just fine. I am not 100% sure what this could be I thought it had something to do with cookies or maybe some session timeout limits in IIS but I cleared all my internet explorer related stuff and checked all the settings (and restarted) IIS. Are there any tips out there for what I could be missing? I thought on looking on how to run some powershell commands related to session limits but have not made much headwind.. Thanks for any help!
July 28th, 2007 11:38pm

Cory, you get this message WHEN you login? Or after you have been logged in for while and idle? Does this happen from the same workstation or any workstation? If it happens from any workstation, I would assume it is a CAS problem. My first thought was cookies, too, but if you cleared those then that is probably not the case. Have you tried rebooting the entire machine?
Free Windows Admin Tool Kit Click here and download it now
July 29th, 2007 10:47pm

Hello, thanks for the reply. This happens when attempting to login, from any machine, internally or externally with multiple machines. I have rebooted the Exchange machine a few times since then for this reason and it still remains an issue. Like I said it works if I use any of the standard auth methods. If you would like to see, RDC or via OWA,I have it up and running (as its a test lab setup) and any help that would solve this would be very nice. Thanks again.
July 30th, 2007 6:54pm

I know that this is an older post, but I am having pretty much the same issue (except that none of the authentication methods work). I was connected on OWA with no issues and then the next day it wasn't working. I can't figure out what the problem might be. I have tried recreating the OWA virtual dir and also uninstalled and reinstalled the CA role. Any chance you can remember what the issue was and what you did to fix it? Thanks for your help, Greg
Free Windows Admin Tool Kit Click here and download it now
April 14th, 2008 2:09am

Did anyone resolve this or figure out the issue? I am having the same problem. I reinstalled OWA in 2007 but am still getting the session timed out message on the Login page after it spins for a bit.
July 1st, 2008 11:38pm

i am haviung the same problem, at first OWA 2007was working ok, then it started timing out, wont let me log in at all, just says session timed out. anyone got a fix for this?
Free Windows Admin Tool Kit Click here and download it now
October 28th, 2008 6:16am

When Forms Based Authentication is used, Exchange 2003 OWA uses configurable cookie authentication time-out. If not configured correctly it can cause issues. Also, client browsers need to support cookies for the same reason. Default cookie time out is 15 minutes for public computer and 24 hours for private computer (as selected by user when logging in to OWA). The timeout values can be configured as described in the following article: http://support.microsoft.com/kb/830827 Please ensure your browser supports cookies and the cookie timeouts on Exchange server are configured correctly.
October 28th, 2008 7:02am

When Forms Based Authentication is used, Exchange 2003 OWA uses configurable cookie authentication time-out. If not configured correctly it can cause issues. Also, client browsers need to support cookies for the same reason. Default cookie time out is 15 minutes for public computer and 24 hours for private computer (as selected by user when logging in to OWA). The timeout values can be configured as described in the following article: http://support.microsoft.com/kb/830827 Please ensure your browser supports cookies and the cookie timeouts on Exchange server are configured correctly.
Free Windows Admin Tool Kit Click here and download it now
October 28th, 2008 7:02am

Thanks for the reply, however my issues is with OWA 2007 (not 2003), installed on win2K3 64-bit Enterpirse, clients machines are win XP sp2 with IE 7. i have also confirmed even if i enter incorrect credentials i still get the same session timed out error, so its not even authenticating it seams.
October 28th, 2008 7:52am

Do you have any third party products installed? i.e. Symantec Enterprise VAult?
Free Windows Admin Tool Kit Click here and download it now
October 28th, 2008 7:44pm

Do you have any third party products installed? i.e. Symantec Enterprise VAult?
October 28th, 2008 7:44pm

the only 3rd party product on the whole server is Sophos Anti Virus, this is also a pysical not virtual server. someone on a different forum suggested i reinstall IIS virtual directories, was hoping not need to do that, but it seams no1 has ever fixed this issue (ive found a few pople posting about having this issue but no fixes have been posted)
Free Windows Admin Tool Kit Click here and download it now
October 29th, 2008 12:48am

I recently ran into one such issue where iis seemed to be crashing every few minutes. Look for event 1000 in w3svc. Also check out the section for Setting the cookie authentication time-out in kb 830827 Satish
October 29th, 2008 7:55pm

Anyone ever find the solution for this? I'm having similar problems. Whatever i input as username and password I get session expired.
Free Windows Admin Tool Kit Click here and download it now
January 9th, 2009 11:04am

After hours of googling I found working solution: Deleting the owa virtual directories and creating them using the following shell commands:get-owavirtualdirectoryThis gave me the name of the owa virtual directory (owa (Default Web Site))remove-owavirtualdirectory -identity (owa (Default Web Site)"Removes the virtual directorynew-owavirtualdirectory -owaversion Exchange2007 -name "owa (default Web Site)"Created the directory againThis fixed the problem for me, hope this will help others with tha same problem.
January 9th, 2009 12:57pm

Same problem, Recreating Virtualdirs, or reinstalling the CA / IIS wont help.Auth seems to be fine (wrong credentials = error)Error in Applog : Der Watson-Bericht steht kurz vor dem Versenden an 'dw20.exe' fr die Prozess-ID: 4592, mit den Parametern: E12IIS, c-RTL-AMD64, 08.01.0240.006, OWA, unknown, unknown, M.E.Common.FailFastException, 0, unknown. ErrorReportingEnabled: FalseWarning in Systemlog : Schwerwiegender Kommunikationsfehler im Windows-Prozessaktivierungsdienst bei einem Prozess fr den Anwendungspool "MSExchangeOWAAppPool". Die Prozess-ID ist "4592". Das Datenfeld enthlt die Fehlernummer.
Free Windows Admin Tool Kit Click here and download it now
January 28th, 2009 7:21pm

Hi in the owa virtual server , try to disable auth ASP.NET Inpersonation. Regards, Leonardo AlonsoLeonardo Alonso CEO www.kerbbo.com.br leonardo.alonso@kerbbo.com.br Connect ! :-] IT& Business Care
June 8th, 2011 2:45pm

Can you confirm if you have made customizations to any OWA logon\logoff pages?James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com
Free Windows Admin Tool Kit Click here and download it now
June 8th, 2011 3:02pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics