.net Error

[Osama Bin Gandhi]

Enduku ostundo telidu..cleared Temp asp.net files ...staging server lo

 

Server Error in '/' Application. The state information is invalid for this page and might be corrupted.

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: The state information is invalid for this page and might be corrupted.

Source Error: 
 

[No relevant source lines]

 

[OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.]

System.Convert.FromBase64String(String s) +0
System.Web.UI.ObjectStateFormatter.Deserialize(String inputString) +77
System.Web.UI.ObjectStateFormatter.System.Web.UI.IStateFormatter.Deserialize(String serializedState) +4
System.Web.UI.Util.DeserializeWithAssert(IStateFormatter formatter, String serializedState) +37
System.Web.UI.HiddenFieldPageStatePersister.Load() +147

[ViewStateException: Invalid viewstate. 

 

[BillMarkSteve]

Debug the code and see...if u can...

[BillMarkSteve]

Staging lo naa ?

Development env lo...no error aa ?

[Osama Bin Gandhi]

ledhu No error.

Staging lo naa ?

Development env lo...no error aa ?

 

[Osama Bin Gandhi]

It worked till one point...tarvata sudden ga started getting this error for TextBox TextChanged Event

 

 

[cinema pichodu]

It worked till one point...tarvata sudden ga started getting this error for TextBox TextChanged Event

i think this is not about temp files bhayya.......i am not a .net guy but usually java lo aithe jvm memory issue. load ekkuvatihe ilanti errors vasthai. we have to change the memory settings.  so .net lo kuda configuration lo change cheyali..

 

Most likely your worker process is configured to be 32 bit (x86). In this case you will hit OOM at very least at about 2GB of allocated objects, but most likely much earlier.

If you really need to load more than let's say 1GB of object in memory consider running your code in 64bit process.

Note: above assuming you actually running out of memory, not something like trying to do 2GB+ allocation at once - which will throw OOM by default (the latest .Net allows bigger allocations as far as I remember).

[Katti_Ramdas]

 

Enduku ostundo telidu..cleared Temp asp.net files ...staging server lo

 

Server Error in '/' Application. The state information is invalid for this page and might be corrupted.

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: The state information is invalid for this page and might be corrupted.

Source Error: 
 

[No relevant source lines]

 

[OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.]

System.Convert.FromBase64String(String s) +0
System.Web.UI.ObjectStateFormatter.Deserialize(String inputString) +77
System.Web.UI.ObjectStateFormatter.System.Web.UI.IStateFormatter.Deserialize(String serializedState) +4
System.Web.UI.Util.DeserializeWithAssert(IStateFormatter formatter, String serializedState) +37
System.Web.UI.HiddenFieldPageStatePersister.Load() +147

[ViewStateException: Invalid viewstate. 

 

 

 

Just set the enableEventValidation attribute in the web.config file for the asp.net application to false.

might also need to check http://blog.syedgakbar.com/2007/11/one-possible-reason-for-the-state-information-is-invalid-for-this-page-exception/

And

http://support.microsoft.com/default.aspx?scid=kb;EN-US;829743

IIS compression enabled on IIS6 can also cause this. Verify this is turned off.

[quintin]

In your webconfig file under app settings check the website route compare it with history or set it to "\