*** Report Manager fails after you enable FIPS compliant
algorithms in Local Security Policy
After you enable the Local Security Policy "System
cryptography: Use FIPS compliant algorithms for encryption, hashing, and
signing", you are not able to use Report Manager. When you open Report
Manager, your browser will be empty or show an "HTTP 500 Internal Server
Error". A SQL Server 2008 R2 or later version of the report server will
add an error message similar to the following in the report server service log
file:
ui!ReportManager_0-1!1708!02/27/2010-08:02:03:: e ERROR:
System.InvalidOperationException: This implementation is not part of the
Windows Platform FIPS validated cryptographic algorithms.
To work around this issue: At this time, there is no
known work around. Report Manager does not support the Local Security Policy
"System cryptography: Use FIPS compliant algorithms for encryption,
hashing, and signing". If you want to use Report Manager you need to
disable the setting and restart the report server service.
This issue applies to: SQL Server 2008 Reporting Services
and SQL Server 2008 R2 Reporting Services.
Reference: