Hello!
I see this is an old post but it seems to be very closely related to an issue I am having. The issue is that reports are not showing up in SCCM, but can be used and accessed from the Reports URL. The ReportsServer URL also works.
In srsrp.log I see these entries repeated every minute.
Updating SRS Configuration. SMS_SRS_REPORTING_POINT 7/14/2023 12:47:17 PM 10264 (0x2818)
Checking reporting server health. SMS_SRS_REPORTING_POINT 7/14/2023 12:47:17 PM 10264 (0x2818)
Successfully created srsserver instance to monitor reporting service. SMS_SRS_REPORTING_POINT 7/14/2023 12:47:17 PM 10264 (0x2818)
Reporting Services URL from Registry [
https://servername/Reports/ReportService2005.asmx] SMS_SRS_REPORTING_POINT 7/14/2023 12:47:17 PM 10264 (0x2818)
The request failed with an empty response. SMS_SRS_REPORTING_POINT 7/14/2023 12:47:17 PM 10264 (0x2818)
(!) SRS not detected as running SMS_SRS_REPORTING_POINT 7/14/2023 12:47:17 PM 10264 (0x2818)
Failures reported during periodic health check by the SRS Server servername. SMS_SRS_REPORTING_POINT 7/14/2023 12:47:17 PM 10264 (0x2818)
Verifing registry change notification is configured. SMS_SRS_REPORTING_POINT 7/14/2023 12:47:17 PM 10264 (0x2818)
Waiting for change or shutdown for 1 minutes SMS_SRS_REPORTING_POINT 7/14/2023 12:47:17 PM 10264 (0x2818)
A little bit of background. The SCCM server was installed and setup prior to me getting hired and both guys who initially set it up are no longer here. When I started I was tasked with taking over SCCM. At the time I was still learning and had not used the reporting feature, but when I tried to use it the first time, the services were unavailable. Upon further investigation I discovered that the Reporting Services Point was stopped and a little later I found that it was a licensing issue. It seems that when the Reporting Services were installed they used the 180 Trial. At the time I did not know that the SCCM license included the use of SQL and SQL Reporting Services. As such I used a different license which allowed activation of the services. This is when I realized that the service was having issues. Fast forward about 6 months and here we are. I have not had the time to really dig into this issue especially since it is not a highly utilized tool, it has been a lower priority.
Since then I have upgraded MECM to 2303 and started digging into this issue again. I just found the tutorial for installation of reporting services,
//www.photo-critics.com/the-report-server-has-encountered-a-configuration-error/. In it you say the license used for reporting services
mustbe the same as that used for SCCM/SQL and it is only displayed when you install SQL for SCCM. If this is the case, is there any way to see the SCCM License and recover that key? Will it work as is without switching that key?
There are not any errors in srsrpSetup.log nor srsrpMSI.log.
更多的信息。SCCM或MECM、SQL和SQLReporting Services are installed on the same server. I am using a domain account that has local admin rights in both SCCM Reporting Service Point Properties and Report Server Configuration Manager. I also tried using my Domain Admin account on both to test and that did not work either. Now I am stuck. What should I try next?
TIA!
