Help, Strange Session Problem

[fizbang]

This should be impossible, but for some reason, people are not getting
individual sessions.

They start a session. I set the session("application") variable to the
unique number generated by an identity column on our sql server. I
only set session("application") at the begiinning and it should stay
the same as they fill out the application. But session("application")
is not staying the same. When another user starts the application, and
session("application") is set for them, it overwrites everyone elses
session("application"). So session("application") which must remain
unchanged, is changed!

I do use cookieless session state, but cookieless sessions were working
for months before the problem started. The application that worked
fine for months before the problem started. We have made changes to
the sql server and web server and application code, but I can't figure
out how these changes could affect the application in such a way. You
shouldn't be able to cross sessions even if you wanted to.

Anything come to mind?

 

[Marina]

Do you take the value out of the session and store it in some local
variable? Or you always refer to it via session("applicaton")?

I am wondering if you have static/shared variables that are being used to
locally refer to session data. Since there would be only one instance of
those variables, all users would share the same one. Just a thought.

Does rolling back the code fix the problem? What about using a different
application server?

 

[fizbang]

What we wound up doing is removing the application from the webserver,
deleting the directory, virtual directories and web application pool,
and then reinstalling the application. That fixed the problem. Still
don't know what the exact cause was. A corrupted binary is our best
guess.