Last post Mar 12, 2012 11:58 AM by geezer
Aug 31, 2006 01:55 PM|kuponutcom|LINK
I have read the full 6 pages (90 posts) of the thread
http://forums.asp.net/7/1173230/ShowThread.aspx and tried just about every single suggestion. nothing has fixed this error.
Sorry for duplicate posting this, I posted this question in that forum thread as well but i have since realized that thread has the "answered" icon so i doubt i will get much help from posting in that thread...
My c# asp.net 2.0 website has not been upgraded from a 1.1 or 1.0 project. I built it from scratch, using 2.0 the whole time. (It would seem most people have this error due to an "upgrading from 1.1" issue, which isn't the case for me)
The error I am getting is:
The state information is invalid for this page and might be corrupted.
and my current web.config file looks like this:
The page(s) that produce this error are all on Firefox. I simultaneously run IE on the same pages to test things at the same time and find that IE has no conflicts whatsoever, these errors are occuring in Firefox
I don't know what other information i can give to try and help my situation getting an answer on how to resolve this issue.
Sep 04, 2006 08:23 AM|vcsjones|LINK
Are you using the latest version of FireFox? It sounds like something in FireFox is corrupting the ViewState.
Also, try running it with ALL Add Ons disabled, perhaps an Add On is doing it.
Sep 08, 2008 03:55 AM|Geeshan|LINK
I have this same problem. I use JQuery to open a popup(another aspx page with postbacks) with some information. But after I close the JQM window, parent page is giving this error when I try to do a post back on the parent page. This only happen in IE and
not in firefox. any ideas? Thanks in advance
Sep 25, 2008 11:04 PM|Geeshan|LINK
I just found a work around. I removed runat="server" tag from the popup page. It working now in IE and FF.
Hope this helps someone
Sep 22, 2010 09:59 AM|dan_2009|LINK
I am getting the same error using jquery tabs and clicking on a button on the parent form that does a postback. Any ideas?
Mar 12, 2012 11:58 AM|geezer|LINK
After trying several workarounds, this is the one that has finally worked for me.
I have a main search page and then talk to another .aspx page (via AJAX) to perform the actual searching and return the results within my parent search page. I removed the 'runat=server' code in the search code page and it worked, finally.