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.
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.
Justin James wrote:
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.