Setting up Configuration Manager current branch (1702) lab for testing. While running the Configmgr reports using IE browser ,http://servername/Reports/Pages/Folder.aspx ,it failed with error code HTTP 500 Internal Server Error. SQL server installed locally on Configmgr box .
I have seen this error couple of time but i don't remember what was the solution to get it fix. So ,in this blog post, we will try to troubleshoot the issue by going through the log files and solve it.
Following the error snippet while while browsing Configmgr reports :
When you get this error, the first place to look at is ,reporting point role installation logs which are located in your Configmgr installation logs folder.
srsrpsetup.log Records results of the reporting point installation process
srsrp.log Records information about the activity and status of reporting services point
From srsrpsetp.log ,reporting services role successfully installed . Next log to look at is srsrp.log to check the health
srsrp.log :
System.Web.Services.Protocols.SoapException: The operation you are attempting requires a secure connection (HTTPS). ---> Microsoft.ReportingServices.Diagnostics.Utilities.SecureConnectionRequiredException: The operation you are attempting requires a secure connection (HTTPS).~ at Microsoft.ReportingServices.WebServer.RsSoapExtension.EnsureHttpsLevel(SoapMessage message)~ at Microsoft.ReportingServices.WebServer.RsSoapExtension.ProcessMessage(SoapMessage message)~ at System.Web.Services.Protocols.SoapMessage.RunExtensions(SoapExtension[] extensions, Boolean throwOnException)~ at System.Web.Services.Protocols.SoapServerProtocol.ReadParameters()~ at System.Web.Services.Protocols.WebServiceHandler.CoreProcessRequest()
Failures reported during periodic health check by the SRS Server servername.domainname
SSRS Role was installed successfully but health check did not run successfully.
Next is to check Reporting services Configuration Manager wizard if anything configured faulty or reporting services running correctly or not (this can be check from services.msc)
At this stage ,all checks passed but still issue persists.
Till now ,we have done the troubleshooting in in Configmgr point of view , but from now onwards ,we will go little further to check from SQL point of view.
Next is to look at SQL reporting services log which is located in your SQL installation folder .Since am using SQL server 2014 on my SCCM server (SQL installed locally) ,reporting services logs can be found at
C:\Program Files\Microsoft SQL Server\MSRS12.MSSQLSERVER\Reporting Services\LogFiles
Look at recently modified date (ReportServerService__07_14_2017_00_05_14) ,open the log using cmtrace.exe
System.InvalidOperationException: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.
Did a internet search using ‘This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms’ ,found this https://blogs.msdn.microsoft.com/dataaccesstechnologies/2015/07/16/report-manager-system-invalidoperationexception-this-implementation-is-not-part-of-the-windows-platform-fips-validated-cryptographic-algorithms/
Follow the instructions given in the above link and apply the solution.
For me, after applying the changes said above (i did web.config) ,i got the following error which leads me to change SecureConnectionLevel to 0 in rsreportserver.config file located in C:\Program Files\Microsoft SQL Server\MSRS12.MSSQLSERVER\Reporting Services\ReportServer ,referrence TechNet article here
Error: The underlying connection was closed: An unexpected error occurred on a send
Solution:
Go back to your reports URL (http://servername/Reports/Pages/Folder.aspx) ,run the reports again to see if it works or not ?
Hope it helps!