viewstate is invalid

G

Guest

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.LoadPageStateFromPersistenceMedium()
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.HttpApplication+IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean&
completedSynchronously)
 
C

Craig Deelsnyder

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.LoadPageStateFromPersistenceMedium()
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.HttpApplication+IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep 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.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top