Actually, this issue is not caused by IIS, the problem occurs when the following conditions are true:
Reference: Muthukumar (http://nadarmuthukumar.blogspot.in), ref
Hope you liked this and let me know your thoughts on post through your comments :)
- The HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\fipsalgorithmpolicy registry subkey is set to 1.
- ASP.NET 2.0 uses the RijndaelManaged implementation of the AES algorithm when it processes view state data. The ReindaelManaged implementation has not been certified by the National Institute of Standards and Technology (NIST) as compliant with the Federal Information Processing Standard (FIPS). Therefore, the AES algorithm is not part of the Windows Platform FIPS validated cryptographic algorithms.
- In a text editor such as Notepad, open the application-level Web.config file.
- In the Web.config file, locate the <system.web> section.
- Add the following <machineKey> section to in the <system.web> section: <machineKey validationKey="AutoGenerate,IsolateApps" decryptionKey="AutoGenerate,IsolateApps" validation="3DES" decryption="3DES"/>
- Save the Web.config file.
- Restart the Microsoft Internet Information Services (IIS) service. To do this, run the following command at a command prompt: iisreset
Reference: Muthukumar (http://nadarmuthukumar.blogspot.in), ref
Hope you liked this and let me know your thoughts on post through your comments :)