asp.net Problem Overview
Every now and then (once every day or so) we're seeing the following types of errors in our logs for an ASP.NET 3.5 application
- Invalid viewstate
- Invalid postback or callback argument
Are these something that "just happens" from time-to-time with an ASP.NET application? Would anyone recommend we spend a lot of time trying to diagnose what's causing the issues?
Solution 1 - asp.net
Well it depends. Invalid viewstate can happen for a variety of reasons.
- Viewstate is too big and has not finished rendering before a user causes a postback on the page. The fix is generally to disable all controls that trigger postbacks and enable them client side once the page has finished loading - see http://blogs.msdn.com/tom/archive/2008/03/14/validation-of-viewstate-mac-failed-error.aspx
- You are using viewstate MACs (and you should be, for security reasons) but you have not set a machine key and the application pool has recycled generating a new one. Don't forget to set a ViewStateUserKey.
- Someone is using an old version of IE on the mac where it truncates hidden form fields. In this case you'll need to move viewstate out of the page into session state.
- Viewstate MAC issues generally indicate you're on a web farm and have forgotten to set a machine key in web.config. However if you have done this then it is probably someone trying to do bad things (bots posting comments, someone trying to trigger events for disabled controls etc.) The cause of these should be tracked down if only to rule out potential security issues.
Whatever you do do not turn off viewstate or event validation.
Solution 2 - asp.net
One issue can be to do with users routers truncating form fields. The way around this is to set the MaxPageStateFieldLength to a smallish number (like 100) in web.config and the ViewState gets broken up into small chunks. It's very simple to do, and this article explains it fully.
Solution 3 - asp.net
Exceptions don't "just happen" from time to time. They always occur for valid reasons, some of which are already listed in the other answers.
However, to alleviate problems with ViewState consider disabling it altogether. As ASP.NET developers we often tend to use ViewState in all sort of places where it isn't needed because its the default. I usually think about using static html before I consider using a control. If you do decide to use a control think about if it really needs ViewState to be enabled. Disabling it often lead to better page load times, so if you can, do it.
I wish it were disabled by default so people were forced to think this way, but it isn't.
Update to answer comment:
Of the top of my head I come up with 3 opportunities to turn off ViewState.
Disable ViewState if data is loaded on every postback. This will often be the case if you're building AJAX enabled sites (that's real AJAX not that UpdatePanel kind ;) ), where you usually load data on the first load and then reload/update data using AJAX requests. In some cases you might even load data on every visit for the sole purpose of disabling ViewState, and then cache the data on the server instead.
You can also consider disabling ViewState if you databind to content which is really static. Sometimes I find a list which is databound to a small static basedata table in the database or something like that. Now, this can be dangerous, but if I'm convinced that the data wont change I might move the data into the page as static content (you could wrap it in a separate control so you won't have several static copies of the data). But if the data then DO change, you will have to change it manually.
Simple controls such as Labels are often good candidates for disabling ViewState.
Finally you could switch to ASP.NET MVC framework and wave goodbye to these problems forever, that's what I'm planning to do even if I will face some other problems. ;)
Solution 4 - asp.net
BlowDart has the right answer for the Invalid Viewstate problem. It's probably your app pool being recycled and changing the encryption key.
See these posts for support:
Solution 5 - asp.net
invalid view state don't have any value for your logger or for users or for your website,End users never sees those errors. to avoid this error try to add the following In Global.ascx:
void Application_Error(object sender, EventArgs e)
if (ex is HttpException && ex.InnerException is ViewStateException)
for more info check the following link:
Solution 6 - asp.net
There's not much you can do about the former - I trap such exceptions and bounce the user to an error page with a message along the lines of "The page you were on has expired. This normally happens when you try to revisit a page where you had already entered data."
Again, there's not much you can do about them except show a suitably friendly message on your error page.
Solution 7 - asp.net
I had this kind of exception being thrown in my logs and had a very different cause from the others listed here. I did have a very large ViewState, which is part of the problem. But that was combining with another issue to cause these exceptions (and possibly occasional bad responses from IIS).
I know I should really be drastically decreasing the size of the ViewState, but this is a large legacy code base and a change like that would be very invasive.
Solution 8 - asp.net
It's probably not a good idea to ignore this error. In addition to all the above answers you may want to consider looking into how large your viewstate is. A large viewstate can be truncated by a proxy server.
If your view state is large then it might be a good idea to use a ASP.net trace to see what controls are using viewstate, and where you can turn this off.
Solution 9 - asp.net
According to Wayne Walter Berry in this blog post another culprit can be using the XHTML doctype in IE8 without having XHTML compliant markup on the page. This can cause IE8 to send scrambled parameters to scriptresource.axd and throw the invalid viewstate exception.
// <![CDATA]> or simply changing the doctype (which could cause other css/styling problems on your page).
Solution 10 - asp.net
Update: Microsoft announced that the following bug fix for IE 8 fixes this problem: