By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,874 Members | 1,028 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,874 IT Pros & Developers. It's quick & easy.

unable to validate data

P: n/a
running IIS on a single server, hosting pages on an intranet basis,
one single user out of 50 is having an unable to validate data issue
how do i fix this (the microsoft KB is a little inconclusive) ?

cheers

mark

this is the error message

Unable to validate data.
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information
about the error and where it originated in the code.

Exception Details: System.Web.HttpException: Unable to validate data.

Source Error:

An unhandled exception was generated during the execution of the current web
request. Information regarding the origin and location of the exception can
be identified using the exception stack trace below.

Stack Trace:

[HttpException (0x80004005): Unable to validate data.]

System.Web.Configuration.MachineKey.GetDecodedData (Byte[] buf, Byte[]
modifier, Int32 start, Int32 length, Int32& dataLength) +196

System.Web.UI.LosFormatter.Deserialize(String input) +60

[HttpException (0x80004005): Authentication of viewstate failed. 1) If this
is a cluster, edit <machineKey> configuration so all servers use the same
validationKey and validation algorithm. AutoGenerate cannot be used in a
cluster. 2) Viewstate can only be posted back to the same page. 3) The
viewstate for this page might be corrupted.]

System.Web.UI.LosFormatter.Deserialize(String input) +118

System.Web.UI.Page.LoadPageStateFromPersistenceMed ium() +102

[HttpException (0x80004005): Invalid_Viewstate

Client IP: 192.168.0.21

Port: 1109

User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1;
..NET CLR 1.1.4322; .NET CLR 2.0.50727)

ViewState:
dDwtMTM3MjY4MTQzNTt0PDtsPGk8MT47PjtsPHQ8O2w8aTw1Pj tpPDEwPjtpPDExPjs+O2w8dDxAMDxwPHA8bDxQYWdlQ291bnQ7 XyFJdGVtQ291bnQ7XyFEYXRhU291cmNlSXRlbUNvdW50O0RhdG FLZXlzOz47bDxpPDE+O2k8MD47aTwwPjtsPD47Pj47Pjs7Ozs7 Ozs7Ozs+Ozs+O3Q8cDxwPGw8VGV4dDs+O2w8NS8yNi8yMDA1LS 0tLS0tLS0tNi8yLzIwMDU7Pj47Pjs7Pjt0PHA8cDxsPFRleHQ7 PjtsPEplbm5hIEtlbm5lZHk7Pj47Pjs7Pjs+Pjs+Pjs+Y5qdRv 2F2k73KF7fQjKP5EMZbcw=

Http-Referer: http://**********/

Path: /**************.]

System.Web.UI.Page.LoadPageStateFromPersistenceMed ium() +448

System.Web.UI.Page.LoadPageViewState() +18

System.Web.UI.Page.ProcessRequestMain() +447

Jan 5 '06 #1
Share this Question
Share on Google+
4 Replies


P: n/a
I have also run into similar issue on our app. most of the time the culprit
is presence of a proxy server or a cache server intercepting the
request/response and chopping off the view state if its too big. Check if
these users have components like WebTv or Google accelrator.

"Mike Fellows" wrote:
running IIS on a single server, hosting pages on an intranet basis,
one single user out of 50 is having an unable to validate data issue
how do i fix this (the microsoft KB is a little inconclusive) ?

cheers

mark

this is the error message

Unable to validate data.
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information
about the error and where it originated in the code.

Exception Details: System.Web.HttpException: Unable to validate data.

Source Error:

An unhandled exception was generated during the execution of the current web
request. Information regarding the origin and location of the exception can
be identified using the exception stack trace below.

Stack Trace:

[HttpException (0x80004005): Unable to validate data.]

System.Web.Configuration.MachineKey.GetDecodedData (Byte[] buf, Byte[]
modifier, Int32 start, Int32 length, Int32& dataLength) +196

System.Web.UI.LosFormatter.Deserialize(String input) +60

[HttpException (0x80004005): Authentication of viewstate failed. 1) If this
is a cluster, edit <machineKey> configuration so all servers use the same
validationKey and validation algorithm. AutoGenerate cannot be used in a
cluster. 2) Viewstate can only be posted back to the same page. 3) The
viewstate for this page might be corrupted.]

System.Web.UI.LosFormatter.Deserialize(String input) +118

System.Web.UI.Page.LoadPageStateFromPersistenceMed ium() +102

[HttpException (0x80004005): Invalid_Viewstate

Client IP: 192.168.0.21

Port: 1109

User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1;
..NET CLR 1.1.4322; .NET CLR 2.0.50727)

ViewState:
dDwtMTM3MjY4MTQzNTt0PDtsPGk8MT47PjtsPHQ8O2w8aTw1Pj tpPDEwPjtpPDExPjs+O2w8dDxAMDxwPHA8bDxQYWdlQ291bnQ7 XyFJdGVtQ291bnQ7XyFEYXRhU291cmNlSXRlbUNvdW50O0RhdG FLZXlzOz47bDxpPDE+O2k8MD47aTwwPjtsPD47Pj47Pjs7Ozs7 Ozs7Ozs+Ozs+O3Q8cDxwPGw8VGV4dDs+O2w8NS8yNi8yMDA1LS 0tLS0tLS0tNi8yLzIwMDU7Pj47Pjs7Pjt0PHA8cDxsPFRleHQ7 PjtsPEplbm5hIEtlbm5lZHk7Pj47Pjs7Pjs+Pjs+Pjs+Y5qdRv 2F2k73KF7fQjKP5EMZbcw=

Http-Referer: http://**********/

Path: /**************.]

System.Web.UI.Page.LoadPageStateFromPersistenceMed ium() +448

System.Web.UI.Page.LoadPageViewState() +18

System.Web.UI.Page.ProcessRequestMain() +447

Jan 5 '06 #2

P: n/a

"ThirdEye" <Th******@discussions.microsoft.com> wrote in message
news:09**********************************@microsof t.com...
I have also run into similar issue on our app. most of the time the culprit
is presence of a proxy server or a cache server intercepting the
request/response and chopping off the view state if its too big. Check if
these users have components like WebTv or Google accelrator.

"Mike Fellows" wrote:


nothing like that on the users machine, we do have IIS server but its
bypassed for local sites,
just seems weird that its on one machine - it follows the users profile
around as well - so if the user
logs onto another machine - the problem surfaces - might be the cache in the
users profile - will try to clear that
Jan 5 '06 #3

P: n/a
sorry meant ISA server
"Mike Fellows" <mi*************@equityhouse.NOSPAM.co.uk> wrote in message
news:wd********************@giganews.com...

"ThirdEye" <Th******@discussions.microsoft.com> wrote in message
news:09**********************************@microsof t.com...
I have also run into similar issue on our app. most of the time the
culprit
is presence of a proxy server or a cache server intercepting the
request/response and chopping off the view state if its too big. Check if
these users have components like WebTv or Google accelrator.

"Mike Fellows" wrote:


nothing like that on the users machine, we do have IIS server but its
bypassed for local sites,
just seems weird that its on one machine - it follows the users profile
around as well - so if the user
logs onto another machine - the problem surfaces - might be the cache in
the users profile - will try to clear that

Jan 5 '06 #4

P: n/a
Any resolution to this?
--
Brad

"Build a man a fire, you warm him for the night. Set a man on fire, you warm
him for the rest of his life."
"Mike Fellows" wrote:
sorry meant ISA server
"Mike Fellows" <mi*************@equityhouse.NOSPAM.co.uk> wrote in message
news:wd********************@giganews.com...

"ThirdEye" <Th******@discussions.microsoft.com> wrote in message
news:09**********************************@microsof t.com...
I have also run into similar issue on our app. most of the time the
culprit
is presence of a proxy server or a cache server intercepting the
request/response and chopping off the view state if its too big. Check if
these users have components like WebTv or Google accelrator.

"Mike Fellows" wrote:


nothing like that on the users machine, we do have IIS server but its
bypassed for local sites,
just seems weird that its on one machine - it follows the users profile
around as well - so if the user
logs onto another machine - the problem surfaces - might be the cache in
the users profile - will try to clear that


Feb 28 '06 #5

This discussion thread is closed

Replies have been disabled for this discussion.