Unanswered SSRS ReportView Error with SQL Session State

  • Tuesday, November 20, 2012 4:59 PM
     
     

    I'm running a local SSRS report in asp.net with SQL Server Session mode. The report works fine in InProc mode, and also fine when I run the page in a separate application, but dropping the page in my application website gives the error below. I should add using my application web.config file in my separate test application doesn't make any difference.

    My only solution currently is to add this to the web.config but it seems a bit extreme - is there a better solution?

    <trust legacyCasModel="true" level="Full"/>

    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

All Replies

  • Thursday, November 22, 2012 1:43 AM
     
     

    Hi,

    As far as i know, this is the only coultion for this issue. If you use Visual Studio 2010 to upgrade your application from ASP.NET 2.0 or ASP.NET 3.5, the tool automatically adds a setting to the Web.config file that preserves legacy rendering. However, if you upgrade an application by changing the application pool in IIS to target the .NET Framework 4, ASP.NET uses the new rendering mode by default.