By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
449,278 Members | 1,142 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 449,278 IT Pros & Developers. It's quick & easy.

Losing Session State

P: n/a
I work as a IIS Admin for a company and we have migrated some ASP.NET apps
from IIS 5 to IIS 6. They worked fine under IIS 5. They had their session
state set to time out after 120 minutes and they were using InProc,
cookieless="false". The Machine.config file did not get analyzed before
migrating, before I started withthis company and that file is no longer
available via tape backup. The current machine.config has its session state
set identically to the web.config for this app. I can get the session state
to go less than 20 minutes by altering the web.config, but I can't get it to
exceed 20 minutes. The machine.config has its "allowoverride" set for "True".
I have done several file scans the web.config is getting parsed and there are
no hits on any files in the app folder from the rtvscan.exe process, so it
looks as though real time Norton scanning is not a factor here. In fact,
there does not appear to be anything accessing those files during the 20 plus
minutes that I sit and wait for the session state to timeout.

We are using .Net Framework v1.1.4322.573. I see where an upgrade to
servicepack to v1.1.4322.947 has been known to correct this issue when it
comes to using cookieless sessions,
http://support.microsoft.com/default...b;en-us;828330 , but does
anyone have any clue as to why this might be happening?

Thanks in advance
Nov 18 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
the idletime has to be greater then session timeout. if the appdomain is
unload (idle too long) then inproc session state is lost.

-- bruce (sqlwork.com)

"Jayhawktuba" <Ja*********@discussions.microsoft.com> wrote in message
news:BE**********************************@microsof t.com...
| I work as a IIS Admin for a company and we have migrated some ASP.NET apps
| from IIS 5 to IIS 6. They worked fine under IIS 5. They had their session
| state set to time out after 120 minutes and they were using InProc,
| cookieless="false". The Machine.config file did not get analyzed before
| migrating, before I started withthis company and that file is no longer
| available via tape backup. The current machine.config has its session
state
| set identically to the web.config for this app. I can get the session
state
| to go less than 20 minutes by altering the web.config, but I can't get it
to
| exceed 20 minutes. The machine.config has its "allowoverride" set for
"True".
| I have done several file scans the web.config is getting parsed and there
are
| no hits on any files in the app folder from the rtvscan.exe process, so it
| looks as though real time Norton scanning is not a factor here. In fact,
| there does not appear to be anything accessing those files during the 20
plus
| minutes that I sit and wait for the session state to timeout.
|
| We are using .Net Framework v1.1.4322.573. I see where an upgrade to
| servicepack to v1.1.4322.947 has been known to correct this issue when it
| comes to using cookieless sessions,
| http://support.microsoft.com/default...b;en-us;828330 , but does
| anyone have any clue as to why this might be happening?
|
| Thanks in advance
Nov 18 '05 #2

P: n/a
Thanks, I am trying that right now. Youare probably right.

Happy Thanksgiving!!

"bruce barker" wrote:
the idletime has to be greater then session timeout. if the appdomain is
unload (idle too long) then inproc session state is lost.

-- bruce (sqlwork.com)

"Jayhawktuba" <Ja*********@discussions.microsoft.com> wrote in message
news:BE**********************************@microsof t.com...
| I work as a IIS Admin for a company and we have migrated some ASP.NET apps
| from IIS 5 to IIS 6. They worked fine under IIS 5. They had their session
| state set to time out after 120 minutes and they were using InProc,
| cookieless="false". The Machine.config file did not get analyzed before
| migrating, before I started withthis company and that file is no longer
| available via tape backup. The current machine.config has its session
state
| set identically to the web.config for this app. I can get the session
state
| to go less than 20 minutes by altering the web.config, but I can't get it
to
| exceed 20 minutes. The machine.config has its "allowoverride" set for
"True".
| I have done several file scans the web.config is getting parsed and there
are
| no hits on any files in the app folder from the rtvscan.exe process, so it
| looks as though real time Norton scanning is not a factor here. In fact,
| there does not appear to be anything accessing those files during the 20
plus
| minutes that I sit and wait for the session state to timeout.
|
| We are using .Net Framework v1.1.4322.573. I see where an upgrade to
| servicepack to v1.1.4322.947 has been known to correct this issue when it
| comes to using cookieless sessions,
| http://support.microsoft.com/default...b;en-us;828330 , but does
| anyone have any clue as to why this might be happening?
|
| Thanks in advance

Nov 18 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.