Error Deserializing ViewState

Error Deserializing ViewState

  
Hi all,

I'm having errors in Service Center in 2 different eSpaces, but error is the same : "Error Deserializing ViewState"; Detail: "
Error Deserializing ViewState
Stack:
[1] Error Deserializing ViewState
at ssAoExterno.Flows.FlowMainFlow.ScrnRequestEdit.FetchViewState()
at ssAoExterno.Flows.FlowMainFlow.ScrnRequestEdit.Page_Load(Object sender, EventArgs e)
at System.Web.UI.Control.OnLoad(EventArgs e)
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

[2] Object reference not set to an instance of an object.
at ssAoExterno.Flows.FlowMainFlow.ScrnRequestEdit.recListListRecords1_Restore()
at ssAoExterno.Flows.FlowMainFlow.ScrnRequestEdit.FetchViewState()
 
"

This error coincided with the migration to version 7, because before it this error never appeared and the application has not changed since then.
I search on google and try one solution that modified the file web.config and add "viewstateencryptionmode=never" but didn't work.

Does any one have a clue about what could be the problem or how it can be solved?

Thanks.

Hugo Castro
Solution
Hi Hugo,

The issue is due to an incompatibility between the objects that were cached in the ViewState (in the browser) and the new version of those objects in the server.
You can workaround that error by publishing the full solution.

I hope that helps!

Cheers,
Davide
Solution
Hi,

I've detected the same error after deployment a new release of an application. Should the end-users have to reload the previously opened application pages after each new deployment?

Cheers,
José Martins

It's common to see this immediately after a deployment, one-time issue per user/screen they have open.

J.Ja

Hey guys,


is there any way to prevent this error type to happen?

We have this every time we release a new version of our app. We release new versions every 2 weeks and we have millions of users, so this error will not go away ever. 


Best Regards,

Nelson Freitas

There is no way to make this not happen. As stated, it is a side effect of things on screens changing. The user's browser has a viewstate with one particular version of variables, structures, etc., you deployed a change which alters the structures, variables, etc. in use, they do a postback with the outdated viewstate and the server does not know what to do with it.


J.Ja

Justin James wrote:

There is no way to make this not happen. As stated, it is a side effect of things on screens changing. The user's browser has a viewstate with one particular version of variables, structures, etc., you deployed a change which alters the structures, variables, etc. in use, they do a postback with the outdated viewstate and the server does not know what to do with it.


J.Ja


Ok Justin,

just wanted to confirm. Would like to have a "clean" error log. Maybe this shouldn't be logged at all to the error logs for the platform. Or maybe we can remove them manually from the tables with our DBA's help (pretty nasty solution)


Thanks for the help.