Sign In| Join
Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Member
64 Points
88 Posts
Apr 02, 2009 08:43 PM|LINK
I'm having an issue with custom session state providers to store the session in a sybase db and the Report viewer.
We have two variants using differnet drivers that we wrote here, everythign is working okay, but when we run SOME but not all
reports via the reprot viewer control we get this error.
System.Web.HttpException: The session state information is invalid and might be corrupted
System.Web.HttpException: The session state information is invalid and might be corrupted.
at System.Web.SessionState.SessionStateItemCollection.Deserialize(BinaryReader reader)
at JCDCHelper.Providers.JCDCSybaseSessionProvider.SybaseCustomSessionData.Deserialize(HttpContext context, String serializedItems, Int32 timeout)
at JCDCHelper.Providers.JCDCSybaseSessionProvider.SybaseCustomSessionData.GetSessionStoreItem(Boolean lockRecord, HttpContext context, String id, Boolean& locked, TimeSpan& lockAge, Object& lockId, SessionStateActions& actionFlags)
at JCDCHelper.Providers.JCDCSybaseSessionProvider.SybaseCustomSessionData.GetItemExclusive(HttpContext context, String id, Boolean& locked, TimeSpan& lockAge, Object& lockId, SessionStateActions& actionFlags)
at System.Web.SessionState.SessionStateModule.GetSessionStateItem()
at System.Web.SessionState.SessionStateModule.BeginAcquireState(Object source, EventArgs e, AsyncCallback cb, Object extraData)
at System.Web.HttpApplication.AsyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
If I goto inproc, the error goes away.
But my project needs the session stuff to be across multiple servers on our farm.
My guess is that the report viewer is putting somthing weird into the session, I treid preventing null and blakcn keys, after reading a
post about that, but no joy.
I tried serializing the entity objects consumed by the report viewer and they serialize and deserialize just fine... so it's something specific
to the report viewer, or to the RDLC files we're using.
Does anyone have any ideas or hints?
Thanks,
Eric-
caladin
Member
64 Points
88 Posts
System.Web.HttpException: The session state information is invalid and might be corrupted
Apr 02, 2009 08:43 PM|LINK
I'm having an issue with custom session state providers to store the session in a sybase db and the Report viewer.
We have two variants using differnet drivers that we wrote here, everythign is working okay, but when we run SOME but not all
reports via the reprot viewer control we get this error.
System.Web.HttpException: The session state information is invalid and might be corrupted
with this call stackSystem.Web.HttpException: The session state information is invalid and might be corrupted.
at System.Web.SessionState.SessionStateItemCollection.Deserialize(BinaryReader reader)
at JCDCHelper.Providers.JCDCSybaseSessionProvider.SybaseCustomSessionData.Deserialize(HttpContext context, String serializedItems, Int32 timeout)
at JCDCHelper.Providers.JCDCSybaseSessionProvider.SybaseCustomSessionData.GetSessionStoreItem(Boolean lockRecord, HttpContext context, String id, Boolean& locked, TimeSpan& lockAge, Object& lockId, SessionStateActions& actionFlags)
at JCDCHelper.Providers.JCDCSybaseSessionProvider.SybaseCustomSessionData.GetItemExclusive(HttpContext context, String id, Boolean& locked, TimeSpan& lockAge, Object& lockId, SessionStateActions& actionFlags)
at System.Web.SessionState.SessionStateModule.GetSessionStateItem()
at System.Web.SessionState.SessionStateModule.BeginAcquireState(Object source, EventArgs e, AsyncCallback cb, Object extraData)
at System.Web.HttpApplication.AsyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
If I goto inproc, the error goes away.
But my project needs the session stuff to be across multiple servers on our farm.
My guess is that the report viewer is putting somthing weird into the session, I treid preventing null and blakcn keys, after reading a
post about that, but no joy.
I tried serializing the entity objects consumed by the report viewer and they serialize and deserialize just fine... so it's something specific
to the report viewer, or to the RDLC files we're using.
Does anyone have any ideas or hints?
Thanks,
Eric-