{"id":197,"date":"2010-05-25T12:16:02","date_gmt":"2010-05-25T04:16:02","guid":{"rendered":"http:\/\/nick.workao.org\/?p=197"},"modified":"2010-05-25T12:16:02","modified_gmt":"2010-05-25T04:16:02","slug":"scriptresource-axd-invalid-viewstate-%e7%bb%8f%e5%b8%b8%e5%9c%a8-ie8-%e5%87%ba%e7%8e%b0%e7%9a%84%e8%a7%a3%e5%86%b3%e6%96%b9%e6%b3%95","status":"publish","type":"post","link":"https:\/\/nick.txtcc.com\/index.php\/win\/197","title":{"rendered":"ScriptResource.axd : Invalid viewstate \u7ecf\u5e38\u5728 IE8 \u51fa\u73b0\u7684\u89e3\u51b3\u65b9\u6cd5"},"content":{"rendered":"

This issue is caused when the ScriptResource.axd querystring parameters can not be decoded on the server. This error can be caused from multiple issues with server configuration or the Browser’s interaction with the server.<\/p>\n

The ScriptResource.axd contains all of the clientside javascript routines for Ajax. Just because you include a scriptmanager that loads a script file it will never appear as a ScriptResource.AXD – instead it will be merely passed as the .js file you send if you reference a external script file. In other words it is what the Microsoft Ajax libraries inject into your HTML to allow them to access their javascript functions they need for page manipulation.<\/p>\n

ASP.NET will use the machine key to encrypt the ScriptResource.axd (and webresource.axd) url’s parameters(in querystring), and by default the machinekey is a randomly generated one which may involve the current time. By default there is a different machinekey on every machine, and it changes when the application (w3svc.exe process) is recycled.<\/p>\n

If you are running a web farm you need to “hard code” the machinekey to be the same for every server. This way a response from one web server can be decrypted on another server. Like in the case one of your servers goes down for maintenance and the users traffic is routed to another server.<\/p>\n

You also need to “hard code” the machine key if you want to “survive” application recycles.<\/p>\n

Here is instructions for “hard coding” the machine key:\nhttp:\/\/msdn.microsoft.com\/en-us\/library\/ms998288.aspx<\/a><\/p>\n

BUT WAIT….<\/strong><\/p>\n

This error can be caused from a number of different issues. One of which is having the wrong DOCTYPE for the style of page you are writing. Especially with Internet Explorer 8.<\/p>\n

This error can be caused from having a DOCTYPE of XHTML. This is because with XHTML all special characters should be encoded or all content should be wrapped inside a CDATA section. In other words if you don’t have prefect XHTML in some cases the browser will not parse your XHTML correctly and the request to \/ScriptResource.axd will have scrambled parameters<\/p>\n

Converting the DOCTYPE to HTML can solve the Viewstate issue.<\/p>\n

\n<\/pre>\n
To This:<\/p>\n
<\/pre>\n
Why does this solve the issue? The browser uses a different parsing  algorithm which is “looser” and can handle the non-compliant XHTML that  you might be outputting.<\/p>\n
One trick mentioned on the Internet to prevent the “Error :  \/ScriptResource.axd : Invalid viewstate.” without having to change the  DOCTYPE is to wrap your javascript in CDATA tags like this:<\/p>\n