G
Guest
Hi,
We are currently running an asp.net application where we are using sql
server to store session state. There are a couple of areas where we store
the state in a class that we then add to the session object. The classes in
question use the [Serializable] attribute. This seemed to work well, we can
put a bit of state into the session object, then cast it back into a class
and use it when needed.
Last week we had a user who was getting an "System.InvalidCastException:
Specified cast is not valid." error. This has only happened with one user so
far, and was intermittent.
Has anyone had similar problems? What sort of things on the client would
affect the way IIS is able to store state?
Environment
Operating System: Windows 2003
Web Server:IIS 6.0
Application:.NET Framework 1.1
Language: C#
Web Browser: Internet Explorer 6.0
Thanks,
Mike
We are currently running an asp.net application where we are using sql
server to store session state. There are a couple of areas where we store
the state in a class that we then add to the session object. The classes in
question use the [Serializable] attribute. This seemed to work well, we can
put a bit of state into the session object, then cast it back into a class
and use it when needed.
Last week we had a user who was getting an "System.InvalidCastException:
Specified cast is not valid." error. This has only happened with one user so
far, and was intermittent.
Has anyone had similar problems? What sort of things on the client would
affect the way IIS is able to store state?
Environment
Operating System: Windows 2003
Web Server:IIS 6.0
Application:.NET Framework 1.1
Language: C#
Web Browser: Internet Explorer 6.0
Thanks,
Mike