Session Is being overwriiten

[awziegler]

I'm a newbie with asp.net so please bear with me. Thanks.

 

I have a web app, uses session inProc. My app is being used by multiple users simultaneously. It seems as though the correct session is not being returned to the correct user. For example: User A hits enter and returned to their screen is User B's response. This is an intranet site and cookies are enabled on all desktops. The users are logging in using a separate domain account.

 

I can't for the life of me figure out what is going wrong.

 

Any clues would be greatly appreciated.

 

Thanks in advance.

 

Annmarie

[PlausiblyDamp]

What kind of things are you storing in the Session collection and how are you accessing it?

[awziegler]

Saving session data; such as userName, userID, etc...

 

Accessing

 

string userName = Session["userName"].ToString();

string userID = Session["userID"].ToString();

 

 

setting:

Session["userName"] = blah;

 

Annmarie

[bungpeng]

Session is automatic handle by IIS and it should be no problem...

 

What do you mean by "The users are logging in using a separate domain account"?

 

Your application using one IIS web server or more than one?

[awziegler]

I mean that the users are logging on to the physical machine with a separate domain account.

 

I double checked all the machines to be sure that cookies were enabled.

 

We are using a single-processor, single-server running IIS. I'm going to check the .net framework version on the server.

 

The web.config has session enabled.

 

I am going for the obvious and am also going to set session enabled in the header of all my aspx files (although MS says you don't need to do this if it's set in the web.config).

 

This is the oddest error I've seen.

 

I appreciate all the help.

 

Annmarie

[bungpeng]

I don't think there are any affect if you use separate domain, because web application basically is use by public from any domains...

 

Actually last time I faced the same problem, it is because we run our web application in R&D machine with evaluation copy of windows2000. After that we move it to other machine, it works fine. So, maybe you can try to run in other machine.