Session variable problem

Greetings!

We are having a problem with Session variables in our .net application
that I hope someone can assist with.

our application stores UserIDs in a session variable at login. We have
an "inbox" aspx page that store user's messages in SQL Server. The
stored procedure uses to populate inbox uses the Session("UserID") to
pull the user's messages. Somehow UserA is bringing back UserB's
messages.

This problem isn't limited to the inbox aspx page, but to any page that
uses Session variables.

Any help would be much appreciated. If you need more info, please let
me know.

Best Regards,
Gene

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!Are you using a clustered environment by any chance?

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
http://www.takempis.com
The more I learn, the less I know.

"Gene" <mooola@.yahoo.com> wrote in message
news:OYuKV80aDHA.3360@.tk2msftngp13.phx.gbl...
> Greetings!
> We are having a problem with Session variables in our .net application
> that I hope someone can assist with.
> our application stores UserIDs in a session variable at login. We have
> an "inbox" aspx page that store user's messages in SQL Server. The
> stored procedure uses to populate inbox uses the Session("UserID") to
> pull the user's messages. Somehow UserA is bringing back UserB's
> messages.
> This problem isn't limited to the inbox aspx page, but to any page that
> uses Session variables.
> Any help would be much appreciated. If you need more info, please let
> me know.
> Best Regards,
> Gene
> *** Sent via Developersdex http://www.developersdex.com ***
> Don't just participate in USENET...get rewarded for it!
No web farms or anythign like that. We have a single box that has 4
CPUs.

Best Regards,
Gene

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
Futhermore, I was talking to our Sys Admin and he said the problem could
be caused because the client may be running a proxy server. This sounds
like a viable reason, but we are using cookieless sessions so the URL is
always unique.

Best Regards,
Gene

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!