viewstate is invalid

[Bala]

Hi,

My asp.net page working fine for local and web. But the web server giving
this problem. i dont know where the problem is. can anyone give me idea why
this happen?

Thanks
Bala

The error description is as follows : System.Web.HttpUnhandledException:
Exception of type System.Web.HttpUnhandledException was thrown. --->
System.Web.HttpException: The viewstate is invalid for this page and might be
corrupted.
at System.Web.UI.Page.LoadPageStateFromPersistenceMed ium()
at System.Web.UI.Page.LoadPageViewState()
at System.Web.UI.Page.ProcessRequestMain()
--- End of inner exception stack trace ---
at System.Web.UI.Page.HandleError(Exception e)
at System.Web.UI.Page.ProcessRequestMain()
at System.Web.UI.Page.ProcessRequest()
at System.Web.UI.Page.ProcessRequest(HttpContext context)
at
System.Web.CallHandlerExecutionStep.System.Web.Htt pApplication+IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionS tep step, Boolean&
completedSynchronously)

[Craig Deelsnyder]

On Mon, 07 Mar 2005 13:25:02 -0600, Bala <Ba**@discussions.microsoft.com>
wrote:

Hi,

My asp.net page working fine for local and web. But the web server giving
this problem. i dont know where the problem is. can anyone give me idea
why
this happen?

Thanks
Bala

The error description is as follows : System.Web.HttpUnhandledException:
Exception of type System.Web.HttpUnhandledException was thrown. --->
System.Web.HttpException: The viewstate is invalid for this page and
might be
corrupted.
at System.Web.UI.Page.LoadPageStateFromPersistenceMed ium()
at System.Web.UI.Page.LoadPageViewState()
at System.Web.UI.Page.ProcessRequestMain()
--- End of inner exception stack trace ---
at System.Web.UI.Page.HandleError(Exception e)
at System.Web.UI.Page.ProcessRequestMain()
at System.Web.UI.Page.ProcessRequest()
at System.Web.UI.Page.ProcessRequest(HttpContext context)
at
System.Web.CallHandlerExecutionStep.System.Web.Htt pApplication+IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionS tep step,
Boolean&
completedSynchronously)

Is this sporadically happening? If so, verify that the proper .NET
framework version is being used on each server for your situation. Then I
would also recommend installing the latest service packs for that
version. I believe there was a time when this problem was solved by a
service pack for certain situations.

In one case, I know a large Viewstate variable in the HTML caused this; we
had to chunk the ViewState into multiple variables ourselves.

--
Craig Deelsnyder
Microsoft MVP - ASP/ASP.NET

[Bala]

Thanks craig. i'll check the latest service packs.

bala

"Craig Deelsnyder" wrote:

On Mon, 07 Mar 2005 13:25:02 -0600, Bala <Ba**@discussions.microsoft.com>
wrote:

Hi,

My asp.net page working fine for local and web. But the web server giving
this problem. i dont know where the problem is. can anyone give me idea
why
this happen?

Thanks
Bala

The error description is as follows : System.Web.HttpUnhandledException:
Exception of type System.Web.HttpUnhandledException was thrown. --->
System.Web.HttpException: The viewstate is invalid for this page and
might be
corrupted.
at System.Web.UI.Page.LoadPageStateFromPersistenceMed ium()
at System.Web.UI.Page.LoadPageViewState()
at System.Web.UI.Page.ProcessRequestMain()
--- End of inner exception stack trace ---
at System.Web.UI.Page.HandleError(Exception e)
at System.Web.UI.Page.ProcessRequestMain()
at System.Web.UI.Page.ProcessRequest()
at System.Web.UI.Page.ProcessRequest(HttpContext context)
at
System.Web.CallHandlerExecutionStep.System.Web.Htt pApplication+IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionS tep step,
Boolean&
completedSynchronously)

Is this sporadically happening? If so, verify that the proper .NET
framework version is being used on each server for your situation. Then I
would also recommend installing the latest service packs for that
version. I believe there was a time when this problem was solved by a
service pack for certain situations.

In one case, I know a large Viewstate variable in the HTML caused this; we
had to chunk the ViewState into multiple variables ourselves.

--
Craig Deelsnyder
Microsoft MVP - ASP/ASP.NET