> Check the number of processes for your Application Pools. If your app pools
> are using more than one process, you might "randomly" loose session objects.
[quoted text clipped - 39 lines]
> >
> > Dave
Ben,
I am such an idiot. I ran some tests displaying a value from the Session
object. It would appear, disappear, then reappear. So the Session object
was not getting reset. The behavior implied that it existed in a particular
section of memory managed by a worker process.
After closer examination, I found that I was looking at the properties of
the wrong application pool in my initial response. The application pool
configured for the website was set to 5 worker processes.
This explains the behavior I saw. Depending how many times I click the
refresh button, I would get a different worker process. When I hit the
worker process with the Session object, it would appear. Otherwise it would
the value for the Session object would not appear.
Setting the worker processes to 1 resolved the problem. Obviously using a
different SessionState like SQL Server or StateServer would also have
resolved the problem. But I didn't want to go through and serialize all of
my objects before saving them.
Is there any way that this little tip can be added to online help for a
future release? It's isn't documented anywhere.
Thank you for your assistance.
Dave
> Ben,
>
[quoted text clipped - 50 lines]
> > >
> > > Dave
Ben Strackany - 07 Feb 2005 19:25 GMT
Hi Dave, glad to hear my tip helped.
As far as it being online somewhere, I think it's buried somewhere in MSDN
about the Cache or Session object. Not sure if it's in IISfaq, tho.

Signature
Ben Strackany
www.developmentnow.com
> Ben,
>
[quoted text clipped - 39 lines]
> > >
> > > For more info:
http://www.developmentnow.com/blog/2005/01/randomly-loosing-session-state-on-iis.aspx
> > > > Hi,
> > > >
[quoted text clipped - 33 lines]
> > > >
> > > > Dave