Symptoms:
• Reporting Services Point role installs correctly and you are able to access the Web Service URL, but not the Report Manager URL
• When accessing the Report Manager URL, you receive an Internal Server Error (HTTP 500)
• No reports show up in the Configuration Manager Console
• The ssrp.log shows the following every minute after deployment:
Set configuration
Check state
Check server health
Successfully created srsserver
Reporting Services URL from Registry
Reporting Services is running
Retrieved datasource definition from the server
...
[1] [0] SMS_SRS_REPORTING_POINT
Confirmed version [11.0.3128.0] for the Sql Srs Instance
Retrieved datasource definition from the server
Updating data source
(!) SRS root folder was reported missing
Failures reported during periodic health check by the SRS Server
I banged my head on this for a while, but finally resolved it.
Resolution:
Check the ReportServerService logs in your SQL folder (Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\LogFiles). I saw the following: System.InvalidOperationException: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.
We run a secure environment with the following GPO setting enabled:
Policy Setting System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing Enabled
This policy effectively breaks SSRS.
Here is the fix:
• Run notepad with administrative credentials
• Open the Reporting Services Web.config file (Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\ReportManager)
• Scroll through the file to find the <system.web> section
• Add the following line within this section:
<machineKey validationKey="AutoGenerate,IsolateApps" decryptionKey="AutoGenerate,IsolateApps" validation="3DES" decryption="3DES"/>
• Save the Web.config file and close notepad
• Open the Reporting Services Configuration Manager and connect to the Report Server Instance
• Stop and Start the Report Service
Sure enough, no more HTTP 500 error!
Hope this helps anyone else who is having this issue.