Validation of viewstate MAC failed.

Question

1.00/5 (2 votes)

See more:

[ViewStateException: Invalid viewstate. Client IP: 31.204.153.195 Port: 56612 Referer: Path: /Default User-Agent: Opera/9.80 (Windows NT 6.1; Win64; x64) Presto/2.12.388 Version/12.16 ViewState: /wEPDwUKMTUxNDM5ODAxMA9kFgJmDw8WAh4FY291bnRmZBYGZg9kFgoCAg8WAh4HY29udGVudAWKAVBvc3QuQmlkLlNoaXAuIGVuYWJsZXMgdHJhbnNwb3J0YXRpb24gcHJvdmlkZXJzIHRvIGNvbXBldGUgZm9yIGJ1c2luZXNzIGJ5IGJpZGRpbmcgdG8gaGF1bCBsb2FkcyBwb3N0ZWQgYnkgc2hpcHBlcnMgb2YgY29tbWVyY2lhbCBmcmVpZ2h0LmQCAw8WAh8BBbIBRnJlaWdodCwgYmlkZGluZywgQmlkIG9uIGZyZWlnaHQsIEZyZWlnaHQgcXVvdGUsIEZyZWlnaHQgcXVvdGVzLCBGcmVpZ2h0IHJhdGVzLCBMb2FkYm9hcmQsIExvYWQgYm9hcmQsIFBvc3QgbG9hZHMsIFN1cHBseSBjaGFpbiwgU3VwcGx5IGNoYWluIG1hbmFnZW1lbnQsIEZyZWlnaHQgYnJva2VyLCBDYXJyaWVyc2QCBA8WAh8BBQxJTkRFWCxGT0xMT1dkAhEPFgIeBFRleHQFxgQ8IS0tIFNUQVJUIEFETUlOIENPREUgQkVGT1JFIC9IRUFEIC0tPg0KDQo8IS0tU3RhcnQgb2YgWm9waW0gTGl2ZSBDaGF0IFNjcmlwdC0tPg0KPHNjcmlwdCB0eXBlPSJ0ZXh0L2phdmFzY3JpcHQiPg0Kd2luZG93LiR6b3BpbXx8KGZ1bmN0aW9uKGQscyl7dmFyIHo9JHpvcGltPWZ1bmN0aW9uKGMpe3ouXy5wdXNoKGMpfSwkPXoucz0NCm...]

[HttpException: Validation of viewstate MAC failed. If this application is hosted by a Web Farm or cluster, ensure that <machinekey> configuration specifies the same validationKey and validation algorithm. AutoGenerate cannot be used in a cluster. http://go.microsoft.com/fwlink/?LinkID=314055]
at System.Web.UI.ViewStateException.ThrowError(Exception inner, String persistedState, String errorPageMessage, Boolean macValidationError)
at System.Web.UI.ObjectStateFormatter.Deserialize(String inputString)
at System.Web.UI.Util.DeserializeWithAssert(IStateFormatter formatter, String serializedState)
at System.Web.UI.HiddenFieldPageStatePersister.Load()
at System.Web.UI.Page.LoadPageStateFromPersistenceMedium()
at System.Web.UI.Page.LoadAllState()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest()
at System.Web.UI.Page.ProcessRequest(HttpContext context)
at ASP.default_aspx.ProcessRequest(HttpContext context) in d:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\root\3653c9f4\8117b1a3\App_Web_br1yhtna.6.cs:line 0
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

I have set up the following in config section:
<pages controlrenderingcompatibilityversion="3.5" enableviewstatemac="true" enableviewstate="true" enableeventvalidation="false" viewstateencryptionmode="Never" clientidmode="Inherit" validaterequest="false" pageparserfiltertype="System.Web.Mvc.ViewTypeParserFilter, System.Web.Mvc, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" pagebasetype="System.Web.Mvc.ViewPage, System.Web.Mvc, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" usercontrolbasetype="System.Web.Mvc.ViewUserControl, System.Web.Mvc, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35">

and

<machinekey validationkey="XXX" decryptionkey="XXX" validation="SHA1" decryption="Auto">

But problem still persists. My website is hosted on windows azure and working on 2 instances.New relic is throwing these errors but I didn't get it any where on website.
Please help me to sort out this issue.

Posted 14-Aug-14 0:42am

amit2620

Updated 14-Aug-14 1:43am

v2

Add a Solution

Comments

Suvabrata Roy 14-Aug-14 8:16am

are you using some machine key ?

Richard Deeming 14-Aug-14 9:01am

You have already posted this question:
http://www.codeproject.com/Questions/807266/Invalid-viewstate-System-Web-UI-ViewStateException[^]

If you want to add more information to the question, use the "Improve question" link. DO NOT repost the question.

Sergey Alexandrovich Kryukov 14-Aug-14 12:48pm

Please, think about it: what's the use of publishing the exception stack trace without showing any code sample which throws this exception?
—SA

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

-Dr_X- · Answer 1 · 2014-08-14T19:00:00

Solution 1

Set the ValidateViewState="false" within the header of the .aspx page.

Posted 14-Aug-14 19:00pm

-Dr_X-