salman_sulaiman_2008
asked on
I get this error: Validation of viewstate MAC failed. when Editing my GridView control
Greetings everyone!
suddenly this error started appearing when I am running my web application, I have a GridView control, with editing enabled, once i click on the "edit" button on the gridview I get this error message:
"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. "
I hope someone could help.
thanks in advance.
~salman~
suddenly this error started appearing when I am running my web application, I have a GridView control, with editing enabled, once i click on the "edit" button on the gridview I get this error message:
"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. "
I hope someone could help.
thanks in advance.
~salman~
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Greetings QPR!
thanks for the reply mate!
I found one suggested solution but without much explaination on how to implement it, here what the one of the guys posted:
--------------------
Thanks for reply;
The Machine Key in Webconfig has solved the proble. The session issues we related to limitation on CPU usage on server that server admin has solved by removing the limitation.
I highly recommend anyone has this proble to try put the MachineKey on Web.config
Cheers
Moez
------------------------
so, I am wondernig now, how can I place the machine key inside the web.config to solve my problem?
~salman~
thanks for the reply mate!
I found one suggested solution but without much explaination on how to implement it, here what the one of the guys posted:
--------------------
Thanks for reply;
The Machine Key in Webconfig has solved the proble. The session issues we related to limitation on CPU usage on server that server admin has solved by removing the limitation.
I highly recommend anyone has this proble to try put the MachineKey on Web.config
Cheers
Moez
------------------------
so, I am wondernig now, how can I place the machine key inside the web.config to solve my problem?
~salman~
ASKER
Greetings QPR!
thanks for the reply mate!
I found one suggested solution but without much explaination on how to implement it, here what the one of the guys posted:
--------------------
Thanks for reply;
The Machine Key in Webconfig has solved the proble. The session issues we related to limitation on CPU usage on server that server admin has solved by removing the limitation.
I highly recommend anyone has this proble to try put the MachineKey on Web.config
Cheers
Moez
------------------------
so, I am wondernig now, how can I place the machine key inside the web.config to solve my problem?
~salman~
thanks for the reply mate!
I found one suggested solution but without much explaination on how to implement it, here what the one of the guys posted:
--------------------
Thanks for reply;
The Machine Key in Webconfig has solved the proble. The session issues we related to limitation on CPU usage on server that server admin has solved by removing the limitation.
I highly recommend anyone has this proble to try put the MachineKey on Web.config
Cheers
Moez
------------------------
so, I am wondernig now, how can I place the machine key inside the web.config to solve my problem?
~salman~
ASKER
Greetings Rejojohny!
thanks mate! I just read your commet too, and it fixed the problem. But, if this way would raise up some security issues then can't we do it some other way, i read on the forum one guy suggesting to place the MachineKey inside the web.config, and another guy suggesting to Uninstall Framework and reinstall it again, but for now, placing that statement inside the web.config actually fixed the problem.
the thing is, I am developing this web application under Windows Vista, and I am wondering if upgrading to .NetFramework 3.0 and Vistual Studio 2008, would be a good idea to come over such debugging problems..? what do you think?
Best Wishes,
~salman~
thanks mate! I just read your commet too, and it fixed the problem. But, if this way would raise up some security issues then can't we do it some other way, i read on the forum one guy suggesting to place the MachineKey inside the web.config, and another guy suggesting to Uninstall Framework and reinstall it again, but for now, placing that statement inside the web.config actually fixed the problem.
the thing is, I am developing this web application under Windows Vista, and I am wondering if upgrading to .NetFramework 3.0 and Vistual Studio 2008, would be a good idea to come over such debugging problems..? what do you think?
Best Wishes,
~salman~
ASKER
Greetings Rejojohny!
thanks mate! I just read your commet too, and it fixed the problem. But, if this way would raise up some security issues then can't we do it some other way, i read on the forum one guy suggesting to place the MachineKey inside the web.config, and another guy suggesting to Uninstall Framework and reinstall it again, but for now, placing that statement inside the web.config actually fixed the problem.
the thing is, I am developing this web application under Windows Vista, and I am wondering if upgrading to .NetFramework 3.0 and Vistual Studio 2008, would be a good idea to come over such debugging problems..? what do you think?
Best Wishes,
~salman~
thanks mate! I just read your commet too, and it fixed the problem. But, if this way would raise up some security issues then can't we do it some other way, i read on the forum one guy suggesting to place the MachineKey inside the web.config, and another guy suggesting to Uninstall Framework and reinstall it again, but for now, placing that statement inside the web.config actually fixed the problem.
the thing is, I am developing this web application under Windows Vista, and I am wondering if upgrading to .NetFramework 3.0 and Vistual Studio 2008, would be a good idea to come over such debugging problems..? what do you think?
Best Wishes,
~salman~
discussed here with potential fix