Note that there are some explanatory texts on larger screens.

plurals
  1. POtimeout and auto logout in asp.net 2.0 with IIS 7 even after doing all the possible settings
    primarykey
    data
    text
    <p>I have an ASP.NET 2.0 web site hosted on Windows Server 2008 with IIS 7. I am using InProc session mode (specified in web.config). My client wants the timeout to be of 3 hours, meaning if the web site is idle, session should remain alive for 3 hours. Currently, what is happening is that if the web site is idle for 20-30 min. and if the user to tries to access any link, it redirects to login page.</p> <p>I searched on internet and did all the possible settings (as follows):</p> <ol> <li><p>In web config, session state, time out = 180 minutes.</p></li> <li><p>In web config, forms authentication, time out = 180 minutes.</p></li> <li><p>In IIS 7, Site->Features View->Session state - Session State Mode Setting: In Proc and Cookie Setting->Time out = 180 minutes</p></li> <li><p>In IIs 7, Site->Features View->ASP->Services->Session Properties->Time out = 03:00:00 hours</p></li> <li><p>In IIS 7, Application Pools->Site->Advanced Setting->Process Model->Idle Time-out = 180 minutes.</p></li> </ol> <p>Even after doing all these settings, timeout has not increased and still if the web site is idle for 20-30 mins. and user tries to access the link, it redirects to login page.</p> <p>Additional Information: Whenever it redirects to login page after idle of 20-30 mins., and if I check the event log on server, it says something like (I am not sure whether this error is related to this particular issue or not): "Forms authentication failed for request. Reason: The ticket supplied has expired"</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload