T
Trevor Andrew
Hi There,
I have a small ASP.NET application under development. I am using VS.NET 2002
(2003 upgrade is on the way) with .NET Framework 1.1. It is hosted on a web
hosting service in the US. I am experiencing the "Viewstate corrupted" error
message on a particular page, when that page is left for a period of time
and I return to it again, and submit it again. The page in question has a
drop-down list of various RSS news feeds I am interested in, so I'll often
look at a set of news articles, read one and return to my page and choose
another RSS feed.
I have been informed by my web hosting organisation that the problem is
caused by "worker process recycling". That is, to minimise resources after a
period of inactivity, the worker process servicing requests for my domain is
re-used.
Does this sound plausible? Many of the other explanations regarding
synchronised machine keys in machine.config files sound much more likely to
me.
Also, even if this were the case, why would the servicing of a subsequent
request by a different worker process consider the client-side persisted
viewstate to be corrupt? That's the bit I just don't understand.
Any help or suggestions would be greatly appreciated.
Regards,
Trevor Andrew
I have a small ASP.NET application under development. I am using VS.NET 2002
(2003 upgrade is on the way) with .NET Framework 1.1. It is hosted on a web
hosting service in the US. I am experiencing the "Viewstate corrupted" error
message on a particular page, when that page is left for a period of time
and I return to it again, and submit it again. The page in question has a
drop-down list of various RSS news feeds I am interested in, so I'll often
look at a set of news articles, read one and return to my page and choose
another RSS feed.
I have been informed by my web hosting organisation that the problem is
caused by "worker process recycling". That is, to minimise resources after a
period of inactivity, the worker process servicing requests for my domain is
re-used.
Does this sound plausible? Many of the other explanations regarding
synchronised machine keys in machine.config files sound much more likely to
me.
Also, even if this were the case, why would the servicing of a subsequent
request by a different worker process consider the client-side persisted
viewstate to be corrupt? That's the bit I just don't understand.
Any help or suggestions would be greatly appreciated.
Regards,
Trevor Andrew