I'm looking for information on what others are experiencing with their
asp.net web sites.

In February, my site had 1,899,680 requests and there were 3,819 errors.
That gives us an error rate of about 0.2%

Most of the errors are:
The state information is invalid for this page and might be corrupted.
Validation of viewstate MAC failed.
Exception of type 'System.Web.HttpUnhandledException' was thrown.
The client disconnected.
Request timed out.

thanks.

From my experience all errors come from "non-defensive" programming.
Most of them generated by bots...
there are a lot of bots that submit forms hoping to send an email on
"contact us" form. Usually those bots change or do not submit viewstate....


George.

"DK" <(E-Mail Removed)> wrote in message
news:87A538A1-931F-479D-A88D-(E-Mail Removed)...
> I'm looking for information on what others are experiencing with their
> asp.net web sites.
>
> In February, my site had 1,899,680 requests and there were 3,819 errors.
> That gives us an error rate of about 0.2%
>
> Most of the errors are:
> The state information is invalid for this page and might be corrupted.
> Validation of viewstate MAC failed.
> Exception of type 'System.Web.HttpUnhandledException' was thrown.
> The client disconnected.
> Request timed out.
>
> thanks.
>

you need to decide what is too high. there are 2 common reasons for your error:

1) asp.net recycled before the postback. every recycle generates a new key
(unless fixed in the web.config), so people that post after a recycle get
this message.

2). your viewstate is too large and proxy servers are truncating it.


-- bruce (sqlwork.com)


"DK" wrote:

> I'm looking for information on what others are experiencing with their
> asp.net web sites.
>
> In February, my site had 1,899,680 requests and there were 3,819 errors.
> That gives us an error rate of about 0.2%
>
> Most of the errors are:
> The state information is invalid for this page and might be corrupted.
> Validation of viewstate MAC failed.
> Exception of type 'System.Web.HttpUnhandledException' was thrown.
> The client disconnected.
> Request timed out.
>
> thanks.
>