none
Using ReportViewer in ASP.NET with SessionState mode SQLServer gets error "Unable to serialize the session state"

    Question

  • I'm on .net 4, using asp.net running against a SQL Server 2008 R2 database.

    We are changing our session state over from InProc to SQLServer, and a ReportViewer page that was working fine now gives this error.

    There appears to be a straight-forward solution to this, for example explained here

    (had to remove link as I got the message "Body text cannot contain images or links until we are able to verify your account." - but it is pretty easy to find)

    Referencing this page:

    (had to remove link as I got the message "Body text cannot contain images or links until we are able to verify your account." - but it is pretty easy to find)

    However I have done everything described on the page and I'm still getting the same problem.

    This may be because my setup is slightly different.

    1. In the example above it sets processing mode to remote, but my processing mode is local. If I just change the processing mode to remote and don't make any of the other changes, I no longer get the error but my report doesn't display.

    2. I don't have a ReportServerUrl - we load the SSRS template and report the data directly from the database, so I'm not sure what to put for this parameter.

    I'd appreciate any suggestions on how we can work around this problem. Here is the full error:

    Unable to serialize the session state. In 'StateServer' and 'SQLServer' mode, ASP.NET will serialize the session state objects, and as a result non-serializable objects or MarshalByRef objects are not permitted. The same restriction applies if similar serialization is done by the custom session state store in 'Custom' mode.

    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.Web.HttpException: Unable to serialize the session state. In 'StateServer' and 'SQLServer' mode, ASP.NET will serialize the session state objects, and as a result non-serializable objects or MarshalByRef objects are not permitted. The same restriction applies if similar serialization is done by the custom session state store in 'Custom' mode.

    Source Error: 

    An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

    Stack Trace: 

    [SerializationException: Type 'System.Runtime.Remoting.ServerIdentity' in Assembly 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' is not marked as serializable.]
       System.Runtime.Serialization.FormatterServices.InternalGetSerializableMembers(RuntimeType type) +9474853
       System.Runtime.Serialization.FormatterServices.GetSerializableMembers(Type type, StreamingContext context) +247
       System.Runtime.Serialization.Formatters.Binary.WriteObjectInfo.InitMemberInfo() +160
       System.Runtime.Serialization.Formatters.Binary.WriteObjectInfo.InitSerialize(Object obj, ISurrogateSelector surrogateSelector, StreamingContext context, SerObjectInfoInit serObjectInfoInit, IFormatterConverter converter, ObjectWriter objectWriter, SerializationBinder binder) +491
       System.Runtime.Serialization.Formatters.Binary.ObjectWriter.Write(WriteObjectInfo objectInfo, NameInfo memberNameInfo, NameInfo typeNameInfo) +388
       System.Runtime.Serialization.Formatters.Binary.ObjectWriter.Serialize(Object graph, Header[] inHeaders, __BinaryWriter serWriter, Boolean fCheck) +444
       System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Serialize(Stream serializationStream, Object graph, Header[] headers, Boolean fCheck) +133
       System.Web.Util.AltSerialization.WriteValueToStream(Object value, BinaryWriter writer) +1762

    [HttpException (0x80004005): Unable to serialize the session state. In 'StateServer' and 'SQLServer' mode, ASP.NET will serialize the session state objects, and as a result non-serializable objects or MarshalByRef objects are not permitted. The same restriction applies if similar serialization is done by the custom session state store in 'Custom' mode.]
       System.Web.Util.AltSerialization.WriteValueToStream(Object value, BinaryWriter writer) +1847
       System.Web.SessionState.SessionStateItemCollection.WriteValueToStreamWithAssert(Object value, BinaryWriter writer) +34
       System.Web.SessionState.SessionStateItemCollection.Serialize(BinaryWriter writer) +638
       System.Web.SessionState.SessionStateUtility.Serialize(SessionStateStoreData item, Stream stream) +244
       System.Web.SessionState.SessionStateUtility.SerializeStoreData(SessionStateStoreData item, Int32 initialStreamSize, Byte[]& buf, Int32& length, Boolean compressionEnabled) +67
       System.Web.SessionState.SqlSessionStateStore.SetAndReleaseItemExclusive(HttpContext context, String id, SessionStateStoreData item, Object lockId, Boolean newItem) +140
       System.Web.SessionState.SessionStateModule.OnReleaseState(Object source, EventArgs eventArgs) +807
       System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +148
       System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +75

    Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.547
    Thursday, November 08, 2012 12:35 PM

All replies