Last post Dec 07, 2011 10:04 AM by jncueto
Dec 05, 2011 03:49 PM|jncueto|LINK
Currently, we host several dozen copies of an application, each of which is used by one of our customers. For the past few weeks we've been seeing fifteen or twenty Invalid Viewstate errors coming from a specific instance of the website each day, whereas
I might see one or two invalid viewstate errors from every other copy of the application combined per week.
- In terms of traffic, this copy of the site is one of the least busy that we host, so I've ruled out an application error that's visible due to volume.
-The program version and web.config for this application are identical to every other application.
- I've deleted all of the application's files and ASP.NET temporary files and forced it to rebuild.
- I read that XHTML errors can cause this occasionally, so I've run every page getting the errors through the W3C validator and they all passed as XHTML Transitional.
- The ViewState is very small on any of the pages getting the error. The biggest of any of the pages is ~300 bytes.
- I've gone through all of Microsoft's troubleshooting steps for Invalid Viewstate errors except for setting the Machine Key. But if it was a Machine Key issue, why would it only show up on a single copy of the site and not the other 50+?
- Turning off View State MAC isn't an option and again, if it was a MAC problem, why would it only show up on a single copy of the site?
- I added the browser version to my error log. Over the past two weeks since I started watching this, the error has occured on IE 7 - 9 and a few iPads. I have not seen Firefox or Chrome get this error yet. I know unpatched versions of IE8 have a glitch
in how they handle the ViewState field, but it would be a statistical impossibility that it's only the visitors to this copy of the site who are using an unpatched browser and everybody else is all patched up.
Any ideas? Thanks in advance!
Dec 06, 2011 01:58 AM|Boere|LINK
do you use viewstate compression to the session object
Dec 06, 2011 06:15 AM|gopalanmani|LINK
Invalid viewstate can happen for a variety of reasons.
Whatever you do do not turn off viewstate or event validation.
and check this thread,
Dec 06, 2011 08:34 AM|jncueto|LINK
I might have found the problem. I was checking all of the site's configuration information and saw that they were the only one still using the old synchronous Google Analytics. I switched it to the new async version about 14 hours ago and haven't had a single
error since, even though traffic has been steady. I'll give it another 24 - 36 hours and post a follow up if this seems to have done it.
Dec 07, 2011 10:04 AM|jncueto|LINK
I wanted to follow up - this seems to have done the trick. It's been about 36 hours now and not a single error yet.