Validation of viewstate MAC failed. If this application is hosted by a Web Farm or cluster, ensure that configuration specifies the same
I want to share this experience that I've encountered just now (but actually not once...even several times) I just opened this topic on my blog...
As I am working on a certain projects.. I encountered this error Validation of viewstate MAC failed. If this application is hosted by a Web Farm or cluster, ensure that configuration specifies the same validationKey and validation algorithm. AutoGenerate cannot be used in a cluster.
Well @ first sight , I don't have any Idea where , when and what went wrong with my work... so I just go on search over the internet ..and I have found out that there is something really wrong with it... and based on some forums that I have read ..it was a some kind of a bug ..too bad they haven't solve this issue yet and still continuing their investigations and looking for some work-around/solutions.
you may refer to this site that has same encountered problem as mine :
http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=101988
I want also to share , that there will be something new with the vs.net which is the "Microsoft Visual Orcas"
this "Orcas" has been introduce by the Microsoft to enable their clients to connect applications on the latest .net frameworks , this might solve .net compatibility... (I think the release of this "Orcas" has relation with the issue I had mentioned earlier)... I hope it will be another work around on some VS.net issues...
You may refer to this site for more Microsoft Visual Studio Orcas details : http://blogs.msdn.com/somasegar/archive/2006/05/18/601354.aspx
As I am working on a certain projects.. I encountered this error Validation of viewstate MAC failed. If this application is hosted by a Web Farm or cluster, ensure that
Well @ first sight , I don't have any Idea where , when and what went wrong with my work... so I just go on search over the internet ..and I have found out that there is something really wrong with it... and based on some forums that I have read ..it was a some kind of a bug ..too bad they haven't solve this issue yet and still continuing their investigations and looking for some work-around/solutions.
you may refer to this site that has same encountered problem as mine :
http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=101988
I want also to share , that there will be something new with the vs.net which is the "Microsoft Visual Orcas"
this "Orcas" has been introduce by the Microsoft to enable their clients to connect applications on the latest .net frameworks , this might solve .net compatibility... (I think the release of this "Orcas" has relation with the issue I had mentioned earlier)... I hope it will be another work around on some VS.net issues...
You may refer to this site for more Microsoft Visual Studio Orcas details : http://blogs.msdn.com/somasegar/archive/2006/05/18/601354.aspx
Comments
Post a Comment