My case is quite different!
Although I set the timeout to 20 min, no session timeout happens. This
thing was working fine with IIS 5.0 but after an upgrade to Enterprise
Edition of Windows 2003 and IIS 6.0, session timeout property is not
functional.
Idle users are still conected for hours ....
Any reason why?
On Jul 16, 2:37 pm, campusr...@gmail.com wrote:
> My case is quite different!
>
> Although I set the timeout to 20 min, no session timeout happens. This
> thing was working fine with IIS 5.0 but after an upgrade to Enterprise
> Edition of Windows 2003 and IIS 6.0, session timeout property is not
> functional.
> Idle users are still conected for hours ....
>
> Any reason why?
solved ... it is a hotfix from microsoft ...
On Jul 16, 4:37 am, campusr...@gmail.com wrote:
> My case is quite different!
>
> Although I set the timeout to 20 min, no session timeout happens. This
> thing was working fine with IIS 5.0 but after an upgrade to Enterprise
> Edition of Windows 2003 and IIS 6.0, session timeout property is not
> functional.
> Idle users are still conected for hours ....
>
> Any reason why?
On upgrade IIS6 runs in IIS5 Compatibility Mode and does not do idle
timeout, so it looks like a bug behavior on the surface. However, I
cannot recall anyone with this issue for the past four years, and IIS6
ASP session state timeout tests haven't been failing... so it looks
like something mysterious and specific to your server. People have
tended to notice IIS6 timing out sessions earlier due to interaction
between process recycling and session timeout in IIS6 Worker Process
Isolation Mode, but that is not in effect here.
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//