After you upgrade from Microsoft ASP.NET 1.1 to Microsoft ASP.NET 2.0, some ASP.NET-based applications may not function correctly. Additionally, when you access ASP.NET Web pages that have ViewState enabled, you may receive the following error message:
[InvalidOperationException: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.]
This problem occurs when the following conditions are true:
-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.
Resolution:-
http://support.microsoft.com/kb/911722
Note:-Please follow each step carefully within this document and the issue will be definately resolved.
I hope the above document helps you to overcome the above mentioned error message. Thanks!
[InvalidOperationException: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.]
This problem occurs when the following conditions are true:
-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.
Resolution:-
http://support.microsoft.com/kb/911722
Note:-Please follow each step carefully within this document and the issue will be definately resolved.
I hope the above document helps you to overcome the above mentioned error message. Thanks!
Hi Amol,
ReplyDeleteI am trying to install SharePoint 2010 and got a similar error, but in my case the site is still not created, even before it created I get this error.
I am writing a blog post about this problem and have included your this blog posting as a reference link. I hope you don't mind.
Regards,
Mahesh
Hello Mahesh,
ReplyDeleteThank You Very Much for including my blog link as a refferance..Million Thanks once again..
Hi Amol,
ReplyDeleteWe are still getting the same FIPS error when we run the config wizard. THis is a new SharePoint 2010 installation but we keep getting the error!!
FIPS is already disabled, and the setup account has admin privileges.
http://collaborationsharepoint.blogspot.com/2010/09/sharepoint-2010-errorsysteminvalidopera.html
Any idea what could be wrong?
1. Are you trying to install SharePoint on the same server where domain controller is hosted ?
ReplyDelete2. Could you please tell me the failure step of PSCONFIG wizard ?
3. at the same time, any messages from the event viewer ?
Please check and let me know so that i can track some activities,Thanks...
This comment has been removed by the author.
ReplyDeleteHi Amol,
ReplyDeleteI got the issue resolved, there are 3 reg keys associated with the FIPS! I had to manually set their values to 1 and then the PSCONFIG ran successfully.
I have written a small blog about it
http://sp.chartisinsurance.net/sites/isginfra/ie8/default.asp