SQL Reporting Services SRS RP HTTP 500 Error When Browsing Reports Site
Came accross an issue when attempting to set up an SRS RP on SCCM 2007 . When browsing the SQL Reporting Services website (http://localhost/reports) Internet Explorer will throw a http 500 internal server error when we attempt to load the SRS webpage.
Upon investigation within the Reporting Services logs (\MSRS10_50.MSSQLSERVER\Reporting Services\LogFiles\) we see the following error messages:
e ERROR: System.InvalidOperationException: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.
e ERROR: HTTP status code –> 500
e ERROR: System.Web.HttpException: Error executing child request for Error.aspx. —> System.Web.HttpUnhandledException: Exception of type ‘System.Web.HttpUnhandledException’ was thrown. —> System.InvalidOperationException: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.
At the time of writing this, Microsoft state the issue as follows on a published troubleshooting article for SRS:
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.
So you have two options. Modify the security policy locally or using a GPO. Alternatively we can modify one of the configuration files used by SRS, which is explained here:
- Open the following file in notepad on the SRS Instance \MSRS10_50.MSSQLSERVER\Reporting Services\ReportManager\web.config
- Add the following text into the <system.web> section of the config file <machineKey validationKey=”AutoGenerate,IsolateApps” decryptionKey=”AutoGenerate,IsolateApps” validation=”3DES” decryption=”3DES”/>
- Close and save the file, and then restart the SRS Service
- (Please note that if you copy and paste line 2 above into notepad, you will need to replace the quotation special characters within the ‘pasted’ code, as for some reason these are replaced on this blog site with the ‘curly’ quote marks – you’ll see what I mean if you compare a new quotation mark in notepad and the copied and pasted line from above)
Your web.config file should look something like this
Launch the SQL Reporting Services web page once more and all should be well!