SMS_SRS_REPORTING_POINT Error messages

Question

Hi,

Receiving the below message for the "SMS_SRS_REPORTING_POINT" Role.

SQL Reporting Services root folder "ConfigMgr_CAS" is not present or not properly configured on the Reporting point server "adatum.contoso.com".

Reporting Point failed to monitor SQL Reporting Services Server on "adatum.contoso.com".

Component Status Summarizer set the status of component "SMS_SRS_REPORTING_POINT" running on computer "adatum.contoso.com" to Warning.

Possible cause: The component is experiencing a problem.
Solution: Diagnose and fix the problem by:

1. Examine the status messages that the component reports.
2. Correcting the problem.
3. Instructing Component Status Summarizer to reset the counts of Error, Warning, and/or Informational status messages reported by the component. To reset the counts, right-click Reset Counts on the component in the Component Status summary in the Configuration Manager Console. When the counts are reset, Component Status Summarizer will change the status of the component to OK. This might take some time if site "CAS" is a child site.
4. Deleting any unwanted status messages from the site database, if necessary.
5. Monitor the component occasionally to verify the problem does not reoccur.

Possible cause: The component is OK and you were unnecessarily alerted because the Component Status Thresholds are set too low for the component.
Solution: Increase the Component Status Thresholds for the component using the Thresholds tab of the Component Status Summarizer Properties dialog box in the Configuration Manager Console.

Possible cause: The component is "flooding" the status system by rapidly reporting the same message repeatedly.
Solution: Diagnose and control the flood of status messages by:

1. Verifying that the component is actually flooding the status system. View the status messages reported by the component, and verify that the same message is continually reported every several minutes or seconds.
2. Noting the Message ID of the flooded status message.
3. Creating a Status Filter Rule for site "CAS" that instructs Status Manager to discard the flooded status message when component "SMS_SRS_REPORTING_POINT" on computer "adatum.contoso.com" reports it.
4. Verifying that your sites' databases were not filled up by the flooded status message. Delete any duplicate status messages from the site database, if necessary.
5. Refer to the Microsoft Knowledge Base for further troubleshooting information.

Component Status Summarizer detected that component "SMS_SRS_REPORTING_POINT", running on computer "adatum.contoso.com", has reported 1 or more Error status messages during the Component Status Threshold Period.

Possible cause: The count equals or exceeds the Component Status Warning Threshold (1 status messages) for Error status messages for the component.
Solution: If the component's status is not already set to Warning, Component Status Summarizer will set the component's status to Warning in the Component Status summary in the Configuration Manager Console.

The report server service is not running on Reporting Service Point server "adatum.contoso.com"; start the service to enable reporting.

Please help to solve the issue.
No errors found in the Program Files\Microsoft Configuration Manager\Logs\srsrp.log

Answer 1

Did you confirm that SSRS is working? Did you confirm that CM server is SA and Admin on the SSRS server?