ASP.NET2.0 session issues

ASP.NET2.0 session issues

Post by greg » Sat, 07 Jul 2007 17:14:26


Our env is as follows:

BigIP F5 load balancing 2x ISA standard 2006 servers with perisistent
connections and using least connections
These then web publish to another F5 with 4x IIS6.0 web farm servers
which host ASP.NET2.0 applications.

Until recently, we have been running asp and Vb.NET code with very
little problem. Since upgrading we have noticed many man errors in our
applications and event viewer with something like this:

Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 06/07/2007 08:51:45
Event time (UTC): 06/07/2007 07:51:45
Event ID: 9659ee7ad5d845dfbd54f08d9df7b513
Event sequence: 115
Event occurrence: 1
Event detail code: 0

Application information:
Application domain: /LM/W3SVC/1109917911/
Root-1-128281738213006250
Trust level: Full
Application Virtual Path: /
Application Path: D:\AppWin32\Websites\name of site\
Machine name: servername

Process information:
Process ID: 3180
Process name: w3wp.exe
Account name: NT AUTHORITY\NETWORK SERVICE

Exception information:
Exception type: Application Exception
Exception message: IP address does not match the session IP
address. Request IP address is ISA1, Session IP address is ISA 2.


We have many other environments, but the only difference is that we
are using round robin connections on them. Could this be to blame?

Our thoughts are looking at the possibilty of user sessions somehow
timing out and then switching to the other ISA server and then we get
a mismatch on the cookie/session
 
 
 

1. ASP.NET2.0 cookieless vs cookie sessions

2. LostFormatter asp.net1 > asp.net2 no longer works

i use the losformatter to serialise a hashtable and the store in the
database. (i save some urls so they can be reconstructed)

we have moved the project from asp.net1 to asp.net2

now whenever i try and deserialize a token that was saved to the db
before the move to asp.net2 it fails with error 'unable to deserialise'

i am also noticing that the serialised values look completely
different.

does this mean the serialisation/deserialisation method has changed,
and my old data (asp.net1) is now unable to be deserialise via asp.net
2

thanks for any advice

db

3. Can't open http:\\192.168.1.x\test\test.asp after ASP.NET2.0 insta

4. difference between asp session state and asp.net session state.

5. ASP session vs. ASP.NET session

6. Accessing ASP Session from ASP.NET via Session cookie

7. printing issues (.NET2.0 issue perhaps?)

8. Session State - What does it take to establish one single ASP.NET session per "browser session"

9. Session Time Out Issue In ASP.NET hosted in Windows 2003 Enterprise Edition

10. sessions and asp.net timeout issues due to host's pool application shutdown

11. Session Time Out Issue In ASP.NEtT hosted in Windows 2003 Enterprise Edition

12. User Session issue with ASP.NET Forms authentication & Windows 2003

13. asp.net 1.1 mobile control session state issue

14. ASP.NET Session Management Performance issue