These forums are read-only and considered to be an archive. Please use the new Community for future interaction and posts.

SessionState hangs & will not end

Hello,

I have a problem with FileVista not ending a session unless the user clicks the logout button. I set the <sessionState mode="InProc" timeout="20" />, authentication set to “none” in the web.config file (both settings confirmed and registered with ASP Net 2.0). All of my other apps registered in Virtual Directory all work correctly with ending their sessions. That is, after a specific amount of time the user is redirected to the login screen and required to login again for those applications.

What is even more interesting with FileVista, is that even when a web browser window is closed and then re-opened, the session continues without the user ever being required to login again (for Firefox, Windows, and Safari). 

I’ve done a clean install of FileVista with a new user account / db / and all with completely different file and db names on the Windows 2003 server – running MS SQL.  I still have the same sessionState problem. Everything else in FileVista works without any problems.

Anyone have any thoughts on what I might be doing wrong with some setting somewhere or within FileVista?

Any suggestions will be greatly appreciated, thank you.
Shannon 7/7/2008 2:43 AM
Hi Shannon,
Thanks for your feedback, you have found another problem :) The problem was not about the session state, it was about the new feature "Remember me" option on the login page which sets a cookie for remembering the user. However the feature was not working as it was intended because of a small error in the javascript code. "Remember me" option was always being applied whether the checkbox was checked or not, that's why you could not see the login page after the session ended.

I have sent you the fixed javascript file which will remove the problem. Now, "Remember me" option will not be active as long as it's not checked.
Cem Alacayir 7/7/2008 5:12 PM
Hi Cem,

You’re the best – problem solved with your update. All is well again and thank you for the quick response.
Shannon 7/8/2008 12:37 AM