Hello Everyone There is a bizform that is sporadically throwing an "Invalid View State" error on submission. Has anyone of you had this issue? I found this stack overflow post and it sounds like an iis / web config issue. thoughts? Thanks Paul

Are you 100% sure it has nothing to do with your machine key? I was having issues with viewstate MAC when I did a new installation on a fresh server. I set the machine key manually in IIS and the problems went away.

We also receive the same error. I chalked it up to a spammer / bot as well, but it would be nice to know.

I have changed the page as per your instructions.. Again same problem is occurring http://takeachallenge.org/CookieConsent.aspx Regards Aashish

I am sure the problem is with Cookie webpart. I tried postbacking the page without cookie webpart and all went correct. Regards Aashish

Thanks. Issue has been resolved. Cookie webpart is not visible in Safari. However, it is working fine with IE, FF and chrome. Please suggest. Regards Aashish

I have a client who has been getting a few different requests that the temporary passwords that are being sent to the users are invalid. The user accounts are being auto-generated when the user checks out as a guest, or if they click the forgot password link. The passwords t...

Hello, Does it happen always or time to time? It could happen if somebody do a postback before the whole viewstate of page is loaded, e.g. if viewstate is too long and/or the connection is slow and user submit some button before the page is completely loaded. Unfortuna...

Can we retrieve if a CancelEvent has been triggered ( on a page with the page wizard control ) in a custom webpart with a macro? I want to make an other web part visible when the page is invalid by using a macro expression. Do I need to write a custom macro for it?

Hello, This issue ordinary happens if somebody do a postback before the whole viewstate of page is loaded, e.g. if viewstate is too long and/or the connection is slow and user submit some button before the page is completely loaded. Unfortunately, this is behavior of .NET...