Article ID: 312112 - View products that this article applies to.
This article was previously published under Q312112
When you use SQLServer session state mode, if you try to store an instance of a class that is not marked as serializable into a session variable, the request returns without an error. However, ASP.NET actually fails to save the session data and blocks subsequent requests in the same session.
This same behavior occurs when you use StateServer session state mode, but you also receive the following run-time error:
When session state is configured to be stored in Microsoft SQL Server, the thread that processes your request hangs, and the TempGetStateItemExclusive stored procedure in the ASPState database is called continuously with the same values in one-second increments. If session state is set to InProc, everything works as expected.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Runtime.Serialization.SerializationException: The type <namespace.classname> in Assembly <AssemblyName>, Version=1.0.676.30211, Culture=neutral, PublicKeyToken=null is not marked as serializable.
This problem occurs because the class is not marked as serializable.
To resolve this problem, add the [Serializable] attribute to mark the class as serializable. For example, use the following Microsoft Visual C# .NET code:
Or use the following Microsoft Visual Basic .NET code:
Note If the class uses other classes, you must mark each class as serializable. The problem in this article also occurs with some Microsoft .NET Framework classes such as the XmlDocument class. These classes cannot be marked as serializable, so the error will still occur.
Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.
This bug was fixed in ASP.NET (included with the .NET Framework) 1.1.
Article ID: 312112 - Last Review: August 3, 2003 - Revision: 3.2
Contact us for more help
Connect with Answer Desk for expert help.