System.Runtime.Serialization.SerializationException Intermittently Occurs Within ReportViewer Control in ASP.NET-Collection of common programming errors

Due to a vendor change, we had to move our production deployment to a new environment, and this was coincided with a lot of upgrades, e.g. Windows Server 2003 to 2012 and SQL Server 2005 to 2012. We managed to get all configurations updated for everything to work, but a bug was reported after this move.

We use ReportViewer (version 8.0.0.0) to display Reporting Services reports. Prior to the move this was working fine. Some time after, we get an intermittent server error (about 1 out of 5 attempts):

Member 'ViewStateValues' was not found. 
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: Member 'ViewStateValues' was not found.

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: Member 'ViewStateValues' was not found.]
   System.Runtime.Serialization.SerializationInfo.GetElement(String name, Type& foundType) +10242733
   System.Runtime.Serialization.SerializationInfo.GetValue(String name, Type type) +45
   Microsoft.Reporting.WebForms.ServerReport..ctor(SerializationInfo info, StreamingContext context) +425

[TargetInvocationException: Exception has been thrown by the target of an invocation.]
   System.RuntimeMethodHandle._SerializationInvoke(Object target, SignatureStruct& declaringTypeSig, SerializationInfo info, StreamingContext context) +0
   System.Runtime.Serialization.ObjectManager.CompleteISerializableObject(Object obj, SerializationInfo info, StreamingContext context) +660
   System.Runtime.Serialization.ObjectManager.FixupSpecialObject(ObjectHolder holder) +124
   System.Runtime.Serialization.ObjectManager.DoFixups() +227
   System.Runtime.Serialization.Formatters.Binary.ObjectReader.Deserialize(HeaderHandler handler, __BinaryParser serParser, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage) +380
   System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize(Stream serializationStream, HeaderHandler handler, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage) +326
   System.Web.Util.AltSerialization.ReadValueFromStream(BinaryReader reader) +1107
   System.Web.SessionState.SessionStateItemCollection.ReadValueFromStreamWithAssert() +73
   System.Web.SessionState.SessionStateItemCollection.DeserializeItem(String name, Boolean check) +347
   System.Web.SessionState.SessionStateItemCollection.get_Item(String name) +27
   System.Web.SessionState.HttpSessionStateContainer.get_Item(String name) +23
   System.Web.SessionState.HttpSessionState.get_Item(String name) +23
   Microsoft.Reporting.WebForms.ReportDataOperation..ctor() +234
   Microsoft.Reporting.WebForms.HttpHandler.GetHandler() +719
   Microsoft.Reporting.WebForms.HttpHandler.ProcessRequest(HttpContext context) +20
   System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +599
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +171

This member ‘ViewStateValues’ mentioned is found nowhere in the solution. There were reports of another member name aside from this, but I’ve never seen it myself.

This does not occur in our Test environment though. Test environment would have Windows Server 2008 R2 and SQL Server 2012. In both environments, the web server is a separate machine from the database server. The solution is using .NET Framework 3.5 (upgraded a few times over the years).

Since this is working in our Test environment, I’d prefer not to update the ReportViewer at this time, if possible, since our development database is still using SQL Server 2005 and still waiting to get an upgrade down the line (admittedly not the most ideal way to upgrade to begin with).

Any help would be greatly appreciate, thanks!