After deploying a new .NET website to a popular Hosting Provider this error started to occur in two instances: First, immediately following a full code/db deployment. Second, anytime a web page was left open for a while and then a link was clicked. There are many possible solutions and it seems these are specific to the website code and/or Hosting Provider environment. The solution that worked great for me was inserting a machinekey in the web config file. Both error instances were immediately solved.
*Use an online MachineKey Generator or Powershell to generate the values.
Image 1:
Solution: <system.web>
<machineKeyvalidationKey= decryptionKey= validation=
|
|
|
|
|