This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Dear Experts,
I've updated our SCCM CB to version 2309 but still failing with the Reporting services point. I've tried to restart SQLServerReportingServices but to no avail. I also noticed that when I tried to open Report Server Configuration Manager it took a long time to connect, it showed Started but when I tried to access http://sqlserver/ReportServer it failed with "HTTP Error 503. The service is unavailable."
It was running fine before I configured PKI for our SCCM and now I'm totally lost. Any advice would be really appreciated.
Hi, @Eaven HUANG
Thank you for posting in Microsoft Q&A forum.
Have we check the Srsrp.log file on the reporting services point for error messages?
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Add comment".
I saw repeating errors below, but the SSRS service is showing running and I've tried to restart the service, even rebooted the SCCM server.
Wait timed out. SMS_SRS_REPORTING_POINT 02/02/2024 11:14:09 992 (0x03E0) Updating SRS Configuration. SMS_SRS_REPORTING_POINT 02/02/2024 11:14:09 992 (0x03E0) Checking reporting server health. SMS_SRS_REPORTING_POINT 02/02/2024 11:14:09 992 (0x03E0) Successfully created srsserver instance to monitor reporting service. SMS_SRS_REPORTING_POINT 02/02/2024 11:14:09 992 (0x03E0) Reporting Services URL from Registry [http://MECMServer/ReportServer/ReportService2005.asmx] SMS_SRS_REPORTING_POINT 02/02/2024 11:14:09 992 (0x03E0) The request failed with HTTP status 503: Service Unavailable. SMS_SRS_REPORTING_POINT 02/02/2024 11:14:09 992 (0x03E0) (!) SRS not detected as running SMS_SRS_REPORTING_POINT 02/02/2024 11:14:09 992 (0x03E0) Failures reported during periodic health check by the SRS Server university.edu.cn. SMS_SRS_REPORTING_POINT 02/02/2024 11:14:09 992 (0x03E0) Verifing registry change notification is configured. SMS_SRS_REPORTING_POINT 02/02/2024 11:14:09 992 (0x03E0) Waiting for change or shutdown for 1 minutes SMS_SRS_REPORTING_POINT 02/02/2024 11:14:09 992 (0x03E0) Wait timed out. SMS_SRS_REPORTING_POINT 02/02/2024 11:15:09 992 (0x03E0) Updating SRS Configuration. SMS_SRS_REPORTING_POINT 02/02/2024 11:15:09 992 (0x03E0) Checking reporting server health. SMS_SRS_REPORTING_POINT 02/02/2024 11:15:09 992 (0x03E0) Successfully created srsserver instance to monitor reporting service. SMS_SRS_REPORTING_POINT 02/02/2024 11:15:09 992 (0x03E0) Reporting Services URL from Registry [http://MECMServer/ReportServer/ReportService2005.asmx] SMS_SRS_REPORTING_POINT 02/02/2024 11:15:09 992 (0x03E0) The request failed with HTTP status 503: Service Unavailable. SMS_SRS_REPORTING_POINT 02/02/2024 11:15:09 992 (0x03E0) (!) SRS not detected as running SMS_SRS_REPORTING_POINT 02/02/2024 11:15:09 992 (0x03E0) Failures reported during periodic health check by the SRS Server university.edu.cn. SMS_SRS_REPORTING_POINT 02/02/2024 11:15:09 992 (0x03E0) Verifing registry change notification is configured. SMS_SRS_REPORTING_POINT 02/02/2024 11:15:09 992 (0x03E0) Waiting for change or shutdown for 1 minutes SMS_SRS_REPORTING_POINT 02/02/2024 11:15:09 992 (0x03E0)
Hi, @Eaven HUANG
When you install the SQL server reporting services, you will be asked for the trail of 180 days or input the license key of the SQL server.
If you choose trail, then after 180 days, you will have the issue: The request failed with HTTP status 503: Service Unavailable.
For more details, refer to this article:
Hi @AllenLiu-MSFT Thanks a lot for pointing this out. I noticed that in Report Server Configuration Manager it does show SQL Server Evaluation, do I need to use the same valid key when I installed the SQL Server or this is separate license being required?
Hi, @Eaven HUANG
Use the same key when you install SQL Server.
Hello @AllenLiu-MSFT After I activated the SSRS, eevrything works fine now! thanks a lot
First off, until you can browse the SSRS website there is not point in trying to troubleshot any reporting point issues. Secondly, Is you SQL license valid? SQL evaluation will expire, has it?