You searched for the word(s): userid:118188

More Search Options

RSS Available

• Re: Validation of viewstate MAC failed

  Rick: I wanted to do some regression testing to explore your thoughts before I replied in further detail. We tested on a whitebox development server, as well as using VS development server. As I mentioned earlier, we thought we started to see this issue appear not long after the lastest patch to 3.5 SP1. We moved the white box forward applying MS updates and testing between updates. The basic configuration is a large commercial retail website running sqlserver and net 3.5 with URL rewriting. Clean

  Posted to State Management (Forum) by Bill_H on 11/23/2009

• Re: Validation of viewstate MAC failed

  Rick: Further update. Redmond has issues a hot fix for this "issue" and confirmed it is related specifically to .Net 3.5 SP1 and the update to that SP1. http://support.microsoft.com/kb/970459 Best, Bill

  Posted to State Management (Forum) by Bill_H on 11/23/2009

• Re: Validation of viewstate MAC failed

  Anyone found a decent resolution to this issue? I have spoken with tech support at a number of server farms, since 3.5 SP1 they are seeing tons of these errors on working websites that already have machine keys installed, with no server farm or garden. Some speculate it has to do with how SP1 changed handling the "action" attribute of web forms. This will also be found in the application logs as "Padding is invalid and cannot be removed". Anyone found a solution? TIA, Bill

  Posted to State Management (Forum) by Bill_H on 11/12/2009

• Re: Validation of viewstate MAC failed

  As I said in the intial post, we already use URLrewriting, applicaltion wide, which has nothing whatsoever to do with this issue. But I hope this is a nice plug for your book....

  Posted to State Management (Forum) by Bill_H on 11/12/2009

• Re: Validation of viewstate MAC failed

  KDevendra: That link is from 2005, long before Net 3.5 SP1 and the changeds that SP caused, and basically implicates the machine key point, of which I stated twice, a machine key is in place. Best, Bill

  Posted to State Management (Forum) by Bill_H on 10/29/2009

• Re: Validation of viewstate MAC failed

  Owaisyahya: Please read the starting post. Bluntly put, neither of your suggestions are relevant. I stated TWICE that a machine key is already in place, and enableeventvalidation is not relelvant to the issue and has been in place since Net 2.0 release. Bill

  Posted to State Management (Forum) by Bill_H on 10/29/2009

• Re: Validation of viewstate MAC failed

  Vijay; FWIW, removing the action attribute from the page directive entirely has no effect at all. Rather shoots that first aspnet team link in the ole url. Cheers, Bill

  Posted to State Management (Forum) by Bill_H on 10/28/2009

• Re: Validation of viewstate MAC failed

  Vijay: There are a lot of related "issues" that will appear on the top end, such as webresource.axd issues, ajax failed to load, invalid viewstate, viewstatemac failure when the underlying problems are more systemically complex. The usual bandaids are machine key, turning off viewstatemac (instead of getting to the cause) there are even some recommendations from MS to remove http-equiv="Content-Type"content="text/html; charset=UTF-8 from the page head as that seems to be

  Posted to State Management (Forum) by Bill_H on 10/28/2009

• Validation of viewstate MAC failed

  Hi: We are seeing this error recently on a page containing both listview and a datalist control since upgrading to Net3.5 SP1. The machine key is correctly set in the webconfig and all other pages are working correctly. The webserver is not on a web farm, nor in a web garden. And I will repeat, a machine key is set correctly in the web.config. Enable or disable viewstate at the page level did not help. Disable viewstatemac at the page level did not help. We do not want to disableviewstatemac in web

  Posted to State Management (Forum) by Bill_H on 10/27/2009
  Filed under: viewstatemac

• Re: Validation of viewstate MAC failed

  Vijay: I am familiar with that link, unfortunately it does not apply. The form action attribute is the same as the page url that is being posted back to, because of the form.browser rewritting the action attribute. Cheers, Bill

  Posted to State Management (Forum) by Bill_H on 10/27/2009