Every now and then (once every day or so) we\'re seeing the following types of errors in our logs for an ASP.NET 3.5 application
It's probably not a good idea to ignore this error. In addition to all the above answers you may want to consider looking into how large your viewstate is. A large viewstate can be truncated by a proxy server.
If your view state is large then it might be a good idea to use a ASP.net trace to see what controls are using viewstate, and where you can turn this off.