SCCM 2012 monitoring - Site Status - Reporting Services Point - Status Critical

Hi all,
I have noticed that the Site Status under Monitoring shows Reporting services point as in Critical state though we do not see anything wrong with SCCM as such (at least we haven't been reported any problems thus far). There is nothing in the event viewer
on SQL Server. Just wanted to know how to resolve this issue. Could you help?
When I try to open status messages for Reporting Services (for any days) it does not return anything as if there are no status messages for this role. Also, could you let me know the log file locations/names for Reporting services point?

Here it is... I have replaced server names with a dummy name.
=================
Reporting Services URL from Registry [http://SCCMSQLSERVER/ReportServer/ReportService2005.asmx]~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:31.588-60><thread=6072 (0x17B8)>
Reporting Services is running  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:31.596-60><thread=6072 (0x17B8)>
Retrieved datasource definition from the server.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:31.616-60><thread=6072 (0x17B8)>
Confirmed version [10.50.4000.0] for the Sql Srs Instance.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:31.641-60><thread=6072 (0x17B8)>
Retrieved datasource definition from the server.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:31.686-60><thread=6072 (0x17B8)>
Updating data source {5C6358F2-4BB6-4a1b-A16E-8D96795D8602} at ConfigMgr_PRI  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:31.686-60><thread=6072 (0x17B8)>
Loading localization resources from directory [F:\SMS_SRSRP\SrsResources.dll]   $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:31.713-60><thread=6072 (0x17B8)>
Looking for 'English (United Kingdom)' resources  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:31.715-60><thread=6072 (0x17B8)>
Looking for 'English' resources  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:31.716-60><thread=6072 (0x17B8)>
Found resources for 'English'  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:31.716-60><thread=6072 (0x17B8)>
Next security configuration at [02/09/2014 13:31:30]  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:32.338-60><thread=6072 (0x17B8)>
Root Folder exists  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:32.338-60><thread=6072 (0x17B8)>
Successfully checked that the SRS web service is healthy on server SCCMSQLSERVER.DOMAIN~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:32.338-60><thread=6072 (0x17B8)>
~Waiting for changes for 1 minutes  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:32.339-60><thread=6072 (0x17B8)>
Timed Out...~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:32.336-60><thread=6072 (0x17B8)>
Reporting Services URL from Registry [http://SCCMSQLSERVER/ReportServer/ReportService2005.asmx]~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:32.347-60><thread=6072 (0x17B8)>
Reporting Services is running  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:32.357-60><thread=6072 (0x17B8)>
Retrieved datasource definition from the server.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:32.377-60><thread=6072 (0x17B8)>
Confirmed version [10.50.4000.0] for the Sql Srs Instance.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:32.404-60><thread=6072 (0x17B8)>
Retrieved datasource definition from the server.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:32.451-60><thread=6072 (0x17B8)>
Updating data source {5C6358F2-4BB6-4a1b-A16E-8D96795D8602} at ConfigMgr_PRI  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:32.451-60><thread=6072 (0x17B8)>
Loading localization resources from directory [F:\SMS_SRSRP\SrsResources.dll]   $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:32.478-60><thread=6072 (0x17B8)>
Looking for 'English (United Kingdom)' resources  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:32.480-60><thread=6072 (0x17B8)>
Looking for 'English' resources  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:32.481-60><thread=6072 (0x17B8)>
Found resources for 'English'  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:32.481-60><thread=6072 (0x17B8)>
Next security configuration at [02/09/2014 13:31:30]  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:33.160-60><thread=6072 (0x17B8)>
Root Folder exists  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:33.161-60><thread=6072 (0x17B8)>
Successfully checked that the SRS web service is healthy on server SCCMSQLSERVER.DOMAIN~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:33.161-60><thread=6072 (0x17B8)>
~Waiting for changes for 1 minutes  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:33.161-60><thread=6072 (0x17B8)>
Timed Out...~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:33.159-60><thread=6072 (0x17B8)>
Reporting Services URL from Registry [http://SCCMSQLSERVER/ReportServer/ReportService2005.asmx]~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:33.168-60><thread=6072 (0x17B8)>
Reporting Services is running  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:33.188-60><thread=6072 (0x17B8)>
Retrieved datasource definition from the server.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:33.237-60><thread=6072 (0x17B8)>
Confirmed version [10.50.4000.0] for the Sql Srs Instance.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:33.264-60><thread=6072 (0x17B8)>
Retrieved datasource definition from the server.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:33.462-60><thread=6072 (0x17B8)>
Updating data source {5C6358F2-4BB6-4a1b-A16E-8D96795D8602} at ConfigMgr_PRI  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:33.462-60><thread=6072 (0x17B8)>
Loading localization resources from directory [F:\SMS_SRSRP\SrsResources.dll]   $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:33.539-60><thread=6072 (0x17B8)>
Looking for 'English (United Kingdom)' resources  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:33.541-60><thread=6072 (0x17B8)>
Looking for 'English' resources  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:33.542-60><thread=6072 (0x17B8)>
Found resources for 'English'  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:33.542-60><thread=6072 (0x17B8)>
Next security configuration at [02/09/2014 13:31:30]  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:34.796-60><thread=6072 (0x17B8)>
Root Folder exists  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:34.797-60><thread=6072 (0x17B8)>
Successfully checked that the SRS web service is healthy on server SCCMSQLSERVER.DOMAIN~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:34.797-60><thread=6072 (0x17B8)>
~Waiting for changes for 1 minutes  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:34.797-60><thread=6072 (0x17B8)>
Timed Out...~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:34.795-60><thread=6072 (0x17B8)>
Reporting Services URL from Registry [http://SCCMSQLSERVER/ReportServer/ReportService2005.asmx]~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:34.804-60><thread=6072 (0x17B8)>
Reporting Services is running  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:34.813-60><thread=6072 (0x17B8)>
Retrieved datasource definition from the server.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:34.834-60><thread=6072 (0x17B8)>
Confirmed version [10.50.4000.0] for the Sql Srs Instance.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:34.859-60><thread=6072 (0x17B8)>
Retrieved datasource definition from the server.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:34.904-60><thread=6072 (0x17B8)>
Updating data source {5C6358F2-4BB6-4a1b-A16E-8D96795D8602} at ConfigMgr_PRI  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:34.905-60><thread=6072 (0x17B8)>
Loading localization resources from directory [F:\SMS_SRSRP\SrsResources.dll]   $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:34.940-60><thread=6072 (0x17B8)>
Looking for 'English (United Kingdom)' resources  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:34.942-60><thread=6072 (0x17B8)>
Looking for 'English' resources  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:34.943-60><thread=6072 (0x17B8)>
Found resources for 'English'  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:34.943-60><thread=6072 (0x17B8)>
Next security configuration at [02/09/2014 13:31:30]  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:35.724-60><thread=6072 (0x17B8)>
Root Folder exists  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:35.725-60><thread=6072 (0x17B8)>
Successfully checked that the SRS web service is healthy on server SCCMSQLSERVER.DOMAIN~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:35.725-60><thread=6072 (0x17B8)>
~Waiting for changes for 1 minutes  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:35.726-60><thread=6072 (0x17B8)>
Timed Out...~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:35.723-60><thread=6072 (0x17B8)>
Reporting Services URL from Registry [http://SCCMSQLSERVER/ReportServer/ReportService2005.asmx]~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:35.731-60><thread=6072 (0x17B8)>
Reporting Services is running  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:35.752-60><thread=6072 (0x17B8)>
Retrieved datasource definition from the server.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:35.776-60><thread=6072 (0x17B8)>
Confirmed version [10.50.4000.0] for the Sql Srs Instance.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:35.813-60><thread=6072 (0x17B8)>
Retrieved datasource definition from the server.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:35.902-60><thread=6072 (0x17B8)>
Updating data source {5C6358F2-4BB6-4a1b-A16E-8D96795D8602} at ConfigMgr_PRI  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:35.902-60><thread=6072 (0x17B8)>
Loading localization resources from directory [F:\SMS_SRSRP\SrsResources.dll]   $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:35.954-60><thread=6072 (0x17B8)>
Looking for 'English (United Kingdom)' resources  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:35.956-60><thread=6072 (0x17B8)>
Looking for 'English' resources  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:35.957-60><thread=6072 (0x17B8)>
Found resources for 'English'  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:35.957-60><thread=6072 (0x17B8)>
Next security configuration at [02/09/2014 13:31:30]  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:36.728-60><thread=6072 (0x17B8)>
Root Folder exists  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:36.729-60><thread=6072 (0x17B8)>
Successfully checked that the SRS web service is healthy on server SCCMSQLSERVER.DOMAIN~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:36.729-60><thread=6072 (0x17B8)>
~Waiting for changes for 1 minutes  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:36.730-60><thread=6072 (0x17B8)>
Timed Out...~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:36.727-60><thread=6072 (0x17B8)>
Reporting Services URL from Registry [http://SCCMSQLSERVER/ReportServer/ReportService2005.asmx]~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:36.738-60><thread=6072 (0x17B8)>
Reporting Services is running  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:36.747-60><thread=6072 (0x17B8)>
Retrieved datasource definition from the server.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:36.769-60><thread=6072 (0x17B8)>
Confirmed version [10.50.4000.0] for the Sql Srs Instance.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:36.799-60><thread=6072 (0x17B8)>
Retrieved datasource definition from the server.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:36.848-60><thread=6072 (0x17B8)>
Updating data source {5C6358F2-4BB6-4a1b-A16E-8D96795D8602} at ConfigMgr_PRI  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:36.848-60><thread=6072 (0x17B8)>
Loading localization resources from directory [F:\SMS_SRSRP\SrsResources.dll]   $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:36.875-60><thread=6072 (0x17B8)>
Looking for 'English (United Kingdom)' resources  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:36.878-60><thread=6072 (0x17B8)>
Looking for 'English' resources  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:36.878-60><thread=6072 (0x17B8)>
Found resources for 'English'  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:36.878-60><thread=6072 (0x17B8)>
Next security configuration at [02/09/2014 13:31:30]  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:37.496-60><thread=6072 (0x17B8)>
Root Folder exists  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:37.497-60><thread=6072 (0x17B8)>
Successfully checked that the SRS web service is healthy on server SCCMSQLSERVER.DOMAIN~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:37.497-60><thread=6072 (0x17B8)>
~Waiting for changes for 1 minutes  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:37.497-60><thread=6072 (0x17B8)>
Timed Out...~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:37.494-60><thread=6072 (0x17B8)>
Reporting Services URL from Registry [http://SCCMSQLSERVER/ReportServer/ReportService2005.asmx]~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:37.503-60><thread=6072 (0x17B8)>
Reporting Services is running  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:37.512-60><thread=6072 (0x17B8)>
Retrieved datasource definition from the server.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:37.534-60><thread=6072 (0x17B8)>
Confirmed version [10.50.4000.0] for the Sql Srs Instance.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:37.563-60><thread=6072 (0x17B8)>
Retrieved datasource definition from the server.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:37.610-60><thread=6072 (0x17B8)>
Updating data source {5C6358F2-4BB6-4a1b-A16E-8D96795D8602} at ConfigMgr_PRI  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:37.610-60><thread=6072 (0x17B8)>
Loading localization resources from directory [F:\SMS_SRSRP\SrsResources.dll]   $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:37.646-60><thread=6072 (0x17B8)>
Looking for 'English (United Kingdom)' resources  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:37.648-60><thread=6072 (0x17B8)>
Looking for 'English' resources  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:37.653-60><thread=6072 (0x17B8)>
Found resources for 'English'  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:37.654-60><thread=6072 (0x17B8)>
Next security configuration at [02/09/2014 13:31:30]  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:38.352-60><thread=6072 (0x17B8)>
Root Folder exists  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:38.353-60><thread=6072 (0x17B8)>
Successfully checked that the SRS web service is healthy on server SCCMSQLSERVER.DOMAIN~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:38.353-60><thread=6072 (0x17B8)>
~Waiting for changes for 1 minutes  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:38.353-60><thread=6072 (0x17B8)>
Timed Out...~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:38.351-60><thread=6072 (0x17B8)>
Reporting Services URL from Registry [http://SCCMSQLSERVER/ReportServer/ReportService2005.asmx]~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:38.361-60><thread=6072 (0x17B8)>
Reporting Services is running  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:38.370-60><thread=6072 (0x17B8)>
Retrieved datasource definition from the server.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:38.393-60><thread=6072 (0x17B8)>
Confirmed version [10.50.4000.0] for the Sql Srs Instance.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:38.432-60><thread=6072 (0x17B8)>
Retrieved datasource definition from the server.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:38.484-60><thread=6072 (0x17B8)>
Updating data source {5C6358F2-4BB6-4a1b-A16E-8D96795D8602} at ConfigMgr_PRI  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:38.485-60><thread=6072 (0x17B8)>
Loading localization resources from directory [F:\SMS_SRSRP\SrsResources.dll]   $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:38.520-60><thread=6072 (0x17B8)>
Looking for 'English (United Kingdom)' resources  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:38.522-60><thread=6072 (0x17B8)>
Looking for 'English' resources  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:38.530-60><thread=6072 (0x17B8)>
Found resources for 'English'  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:38.531-60><thread=6072 (0x17B8)>
Next security configuration at [02/09/2014 13:31:30]  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:39.270-60><thread=6072 (0x17B8)>
Root Folder exists  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:39.270-60><thread=6072 (0x17B8)>
Successfully checked that the SRS web service is healthy on server SCCMSQLSERVER.DOMAIN~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:39.271-60><thread=6072 (0x17B8)>
~Waiting for changes for 1 minutes  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:39.271-60><thread=6072 (0x17B8)>
Timed Out...~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:39.268-60><thread=6072 (0x17B8)>
Reporting Services URL from Registry [http://SCCMSQLSERVER/ReportServer/ReportService2005.asmx]~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:39.277-60><thread=6072 (0x17B8)>
Reporting Services is running  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:39.286-60><thread=6072 (0x17B8)>
Retrieved datasource definition from the server.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:39.308-60><thread=6072 (0x17B8)>
Confirmed version [10.50.4000.0] for the Sql Srs Instance.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:39.334-60><thread=6072 (0x17B8)>
Retrieved datasource definition from the server.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:39.380-60><thread=6072 (0x17B8)>
Updating data source {5C6358F2-4BB6-4a1b-A16E-8D96795D8602} at ConfigMgr_PRI  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:39.381-60><thread=6072 (0x17B8)>
Loading localization resources from directory [F:\SMS_SRSRP\SrsResources.dll]   $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:39.421-60><thread=6072 (0x17B8)>
Looking for 'English (United Kingdom)' resources  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:39.423-60><thread=6072 (0x17B8)>
Looking for 'English' resources  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:39.424-60><thread=6072 (0x17B8)>
Found resources for 'English'  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:39.424-60><thread=6072 (0x17B8)>
Confirmed the configuration of SRS role [ConfigMgr Report Users].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.088-60><thread=6072 (0x17B8)>
Confirmed the configuration of SRS role [ConfigMgr Report Administrators].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.098-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.700-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.736-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Asset Intelligence].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.758-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Compliance and Settings Management].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.791-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Administrative Security].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.815-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Operating System].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.849-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Updates - A Compliance].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.870-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Updates - B Deployment Management].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.906-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Updates - C Deployment States].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.929-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Updates - D Scan].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.961-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Updates - E Troubleshooting].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.998-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Driver Management].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.033-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Task Sequence - Deployment Status].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.067-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Task Sequence - Deployments].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.099-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Task Sequence - Progress].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.127-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Task Sequence - References].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.155-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/State Migration].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.192-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Application Monitoring].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.221-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Virtual Applications].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.265-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Package and Program Deployment Status].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.303-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Package and Program Deployment].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.326-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/User - Device Affinity].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.362-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Metering].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.381-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Status Messages].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.413-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Migration].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.432-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Device Management].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.470-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Status Messages - Audit].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.495-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Alerts].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.529-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Client Status].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.551-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Client Push].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.585-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - CD-ROM].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.609-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Disk].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.642-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - General].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.666-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Memory].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.700-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Modem].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.724-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Network Adapter].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.755-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Processor].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.778-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - SCSI].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.815-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Sound Card].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.835-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Video Card].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.867-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Site - Client Information].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.888-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Site - Discovery and Inventory Information].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.924-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Site - General].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.952-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Site - Server Information].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.985-60><thread=6072 (0x17B8)>
The security policy for folder [/ConfigMgr_PRI/Network Access Protection] is out of sync.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.007-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Network Access Protection].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.042-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Power Management].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.073-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Wake On LAN].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.096-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Network].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.132-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software - Files].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.156-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software - Companies and Products].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.189-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Users].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.209-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Collections].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.243-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Content].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.268-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Out Of Band Management].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.298-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Endpoint Protection].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.320-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Status Messages/Status Messages - Hidden].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.349-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Endpoint Protection/Endpoint Protection - Hidden].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.367-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Application Monitoring/Software Distribution - Application Monitoring - Hidden].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.397-60><thread=6072 (0x17B8)>
The security policy for folder [/ConfigMgr_PRI/Network Access Protection] is out of sync.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.418-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Network Access Protection].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.458-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Replication Traffic].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.492-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Upgrade Assessment].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.511-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/User Data and Profiles Health].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.542-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.571-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.599-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Asset Intelligence].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.632-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Compliance and Settings Management].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.656-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Administrative Security].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.689-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Operating System].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.709-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Updates - A Compliance].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.742-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Updates - B Deployment Management].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.767-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Updates - C Deployment States].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.800-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Updates - D Scan].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.822-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Updates - E Troubleshooting].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.856-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Driver Management].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.880-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Task Sequence - Deployment Status].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.911-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Task Sequence - Deployments].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.932-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Task Sequence - Progress].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.966-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Task Sequence - References].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.988-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/State Migration].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.020-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Application Monitoring].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.045-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Virtual Applications].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.078-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Package and Program Deployment Status].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.113-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Package and Program Deployment].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.137-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/User - Device Affinity].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.170-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Metering].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.193-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Status Messages].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.227-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Migration].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.247-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Device Management].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.280-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Status Messages - Audit].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.306-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Alerts].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.339-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Client Status].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.361-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Client Push].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.395-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - CD-ROM].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.415-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Disk].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.445-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - General].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.467-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Memory].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.497-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Modem].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.518-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Network Adapter].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.550-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Processor].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.570-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - SCSI].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.602-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Sound Card].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.625-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Video Card].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.655-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Site - Client Information].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.676-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Site - Discovery and Inventory Information].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.710-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Site - General].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.731-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Site - Server Information].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.762-60><thread=6072 (0x17B8)>
The security policy for folder [/ConfigMgr_PRI/Network Access Protection] is out of sync.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.785-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Network Access Protection].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.821-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Power Management].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.852-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Wake On LAN].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.878-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Network].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.899-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software - Files].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.933-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software - Companies and Products].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.967-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Users].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.994-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Collections].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.027-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Content].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.052-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Out Of Band Management].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.084-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Endpoint Protection].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.106-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Status Messages/Status Messages - Hidden].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.135-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Endpoint Protection/Endpoint Protection - Hidden].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.153-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Application Monitoring/Software Distribution - Application Monitoring - Hidden].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.186-60><thread=6072 (0x17B8)>
The security policy for folder [/ConfigMgr_PRI/Network Access Protection] is out of sync.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.209-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Network Access Protection].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.250-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Replication Traffic].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.284-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Upgrade Assessment].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.304-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/User Data and Profiles Health].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.338-60><thread=6072 (0x17B8)>
Root Folder exists  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.339-60><thread=6072 (0x17B8)>
Successfully checked that the SRS web service is healthy on server SCCMSQLSERVER.DOMAIN~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.339-60><thread=6072 (0x17B8)>
~Waiting for changes for 1 minutes  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.339-60><thread=6072 (0x17B8)>

Similar Messages

  • Reporting Services Point status message errors.

    My Reporting Services Point seems to work OK -all reports are available and run correctly both through the console and via the website. However, I am seeing the following warning in the SMS_SRS_REPORTING_POINT status messages every hour:
    "The SQL Reporting Services datasource on Reporting point server "Databaseserver.contoso.com" is missing or has been changed outside of Configuration Manager.  It will be rebuilt based on the RSP configuration."
    Here's what I think is causing the issue, but I don't know how to solve it.
    The reports database is on the same remote SQL server as my site database. Because these site systems were installed automatically through the SCCM installation process, they show up in the Servers and Site Systems Role without an intranet FQDN. However,
    when I add the RSP to the database server, it creates a new entry because when manually adding site systems SCCM insists on automatically adding the intranet FQDN. So I now have two separate entries for the same server:
    \\DBServer01 - component server, site database server, site system
    \\DBServer01.contoso.com - component server, reporting services point, site system
    Any thoughts on how to stop these errors?

    Yes, I know this is an old post, but I’m trying to clean them up.
    In the past when I have seen this, they will automatically clean themselves up after a few days. (aka up to a week later). Have it clean itself up yet?
    Garth Jones | My blogs: Enhansoft and
    Old Blog site | Twitter:
    @GarthMJ

  • SCCM 2012 R2 - Reporting Services Point installation - "The Datasource does not exist"

    Hi all,
    Quick bit of background, we have SCCM 2012 R2 installed on a Windows 2012 R2 server. We have the SQL back end off box, configured on a SQL 2012 R2 server running on a Windows Server 2012 R2 cluster. Then there is yet another server which runs the reporting
    services. I've just tried installing the Reporting Services Point on the srs server but it doesn't appear to have worked that well. Here's the info i've got back: 
    A] Site Status > Reporting services point:
    SMS_SITE_SYSTEM_STATUS_SUMMERIZER
    Site System Status Summarizer detected that the availability of the "Reporting services point" role on server "\\NA-SQLR01.in.tna.local" has changed to Failed.
    B] The last message from the SMS_SRS_REPORTING_POINT Component Status is "Site Component Manager successfully installed this component on this site system"
    C] Here's the first chunk of info which appears in the srsrp.log file:
    SMS_EXECUTIVE started SMS_SRS_REPORTING_POINT as thread ID 4204 (0x106C).
    This is a SRS Reporting Point Role as SRSRP registry key exists.
    Waiting for changes for 0 minutes
    Timed Out...
    Set configuration
    Check state
    Check server health.
    Successfully created srsserver SMS_
    Reporting Services URL from Registry [http://sqlreportserver/ReportServer_SQL2012/ReportService2005.asmx]
    Reporting Services is running
    The DataSource does not exist.
    [sqlserver.local\SQL1] [SCCM_XXX] [ConfigMgr_XXX] [sqlreportserver.LOCAL]
    [SQL2012] [1] [] [xxx\SCCM2012Server]
    Confirmed version [11.0.5058.0] for the Sql Srs Instance.
    System.Web.Services.Protocols.SoapException: The item '/ConfigMgr_XXX' cannot be found. ---> Microsoft.ReportingServices.Diagnostics.Utilities.ItemNotFoundException: The item '/ConfigMgr_XXX' cannot be found.~   at Microsoft.ReportingServices.Library.ReportingService2005Impl.GetProperties(String
    Item, Property[] Properties, ItemNamespaceEnum itemNamespace, Property[]& Values)~   at Microsoft.ReportingServices.WebServer.ReportingService2005.GetProperties(String Item, Property[] Properties, Property[]& Values)
    Extract resource language packs if exists
    Loading localization resources from directory [D:\SMS_SRSRP\SrsResources.dll]
    Looking for 'English (United Kingdom)' resources
    Looking for 'English' resources
    Found resources for 'English'
    System.Web.Services.Protocols.SoapException: The item '/ConfigMgr_XXX' cannot be found. ---> Microsoft.ReportingServices.Diagnostics.Utilities.ItemNotFoundException: The item '/ConfigMgr_XXX' cannot be found.~   at Microsoft.ReportingServices.Library.ReportingService2005Impl.SetProperties(String
    Item, Property[] Properties, Guid batchId)~   at Microsoft.ReportingServices.WebServer.ReportingService2005.SetProperties(String Item, Property[] Properties)
    System.Web.Services.Protocols.SoapException: The permissions granted to user 'NT AUTHORITY\SYSTEM' are insufficient for performing this operation. ---> Microsoft.ReportingServices.Diagnostics.Utilities.AccessDeniedException: The permissions granted to user
    'NT AUTHORITY\SYSTEM' are insufficient for performing this operation.~   at Microsoft.ReportingServices.Library.ReportingService2005Impl.CreateFolder(String Folder, String Parent, Property[] Properties, Guid batchId)~   at Microsoft.ReportingServices.WebServer.ReportingService2005.CreateFolder(String
    Folder, String Parent, Property[] Properties)
    (!) SRS root folder was reported missing
    STATMSG: ID=7405 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_SRS_REPORTING_POINT" SYS=sqlreportserver.LOCAL SITE=P01 PID=2120 TID=4204 GMTDATE=Wed Apr 08 08:56:05.349 2015 ISTR0="ConfigMgr_XXX" ISTR1="sqlreportserver.LOCAL"
    ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
        WARNING: Could not read registry key HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\MPFDM\Inboxes\ on the server, The operating system reported error 2: The system cannot find the file specified.
        WARNING: Could not read registry key HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\MPFDM\Inboxes\ on the server, The operating system reported error 2: The system cannot find the file specified.
    Failures reported during periodic health check by the SRS Server sqlreportserver.LOCAL.
    Registry change
    Waiting for changes for 1 minutes
    After this point i simply get the following info messages looping endlessly:
    Set configuration
    Check state
    Check server health.
    Successfully created srsserver
    Reporting Services URL from Registry [http://sqlreportserver/ReportServer_SQL2012/ReportService2005.asmx]
    Reporting Services is running
    The DataSource does not exist.
    [sqlreportserverlocal\SQL1] [SCCM_XXX] [ConfigMgr_P01] [sqlreportserver.LOCAL]
    [SQL2012] [1] [] [XX\SCCM2012Server]
    [1] [0]
    Confirmed version [11.0.5058.0] for the Sql Srs Instance.
    System.Web.Services.Protocols.SoapException: The item '/ConfigMgr_XXX' cannot be found. ---> Microsoft.ReportingServices.Diagnostics.Utilities.ItemNotFoundException: The item '/ConfigMgr_XXX' cannot be found.~   at Microsoft.ReportingServices.Library.ReportingService2005Impl.GetProperties(String
    Item, Property[] Properties, ItemNamespaceEnum itemNamespace, Property[]& Values)~   at Microsoft.ReportingServices.WebServer.ReportingService2005.GetProperties(String Item, Property[] Properties, Property[]& Values)
    Extract resource language packs if exists
    Loading localization resources from directory [D:\SMS_SRSRP\SrsResources.dll]
    Looking for 'English (United Kingdom)' resources
    Looking for 'English' resources
    Found resources for 'English'
    System.Web.Services.Protocols.SoapException: The item '/ConfigMgr_XXX' cannot be found. ---> Microsoft.ReportingServices.Diagnostics.Utilities.ItemNotFoundException: The item '/ConfigMgr_P01' cannot be found.~   at Microsoft.ReportingServices.Library.ReportingService2005Impl.SetProperties(String
    Item, Property[] Properties, Guid batchId)~   at Microsoft.ReportingServices.WebServer.ReportingService2005.SetProperties(String Item, Property[] Properties)
    System.Web.Services.Protocols.SoapException: The permissions granted to user 'NT AUTHORITY\SYSTEM' are insufficient for performing this operation. ---> Microsoft.ReportingServices.Diagnostics.Utilities.AccessDeniedException: The permissions granted to user
    'NT AUTHORITY\SYSTEM' are insufficient for performing this operation.~   at Microsoft.ReportingServices.Library.ReportingService2005Impl.CreateFolder(String Folder, String Parent, Property[] Properties, Guid batchId)~   at Microsoft.ReportingServices.WebServer.ReportingService2005.CreateFolder(String
    Folder, String Parent, Property[] Properties)
    (!) SRS root folder was reported missing
    Failures reported during periodic health check by the SRS Server sqlreportserver.LOCAL.
    Registry change
    Waiting for changes for 1 minutes
    Has anyone come across this issue before? Must admit, I'm not too hot on the sql side of things so any advice or suggestions would be greatly appreciated. Thanks in advance!

    Hi guys, cheers for the swift response.
    Garth, i can access SSRS in IE from the SCCM box and it looks a-ok.
    Paul, nope can't say I've done any configuration of reporting services - the whole thing has been set up by the database team. Having had a trundle through Reporting Services Configuration Manager, it seems the Database team have set up SSRS in line with
    the walkthrough you posted.
    Since i'm not seeing the ConfigMgr_XXX folder appear in SSRS I'm wondering if there's something preventing SCCM from being able to create it. The message
    "Microsoft.ReportingServices.Diagnostics.Utilities.AccessDeniedException: The permissions
    granted to user 'NT AUTHORITY\SYSTEM' are insufficient for performing this operation" sounds like the account SCCM is leveraging to perform the install might not have the right permissions in SSRS. Do i need to delegate specific rights to the NT
    AUTHORITY\SYSTEM account in SRS perhaps?

  • Critical Errors SCCM 2012 (Distribution Point and Reporting services point)

    Hello,
    We are getting errors under the Site Status for the Distribution Point and Reporting services point. Was running fine and have not really made any changes but all of a sudden we have these critical errors.
    The report server service is not running on Reporting Service Point server "XXXXXXXXXXX"; start the service to enable reporting.
    We have stopped and restarted the SQL 2012 reporting service point with no errors. What else should we look at for this error? And are these related?
    Thanks,
    Bobby

    Hi,
    Have you checked the log file SRSRP.log?
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • SCCM 2012 R2 Install - Reporting Services Point, Remote SRS Server

    Hi all,
    Here's a brief run down of the setup so far. SCCM 2012 R2 installed on Windows 2012 R2 (SCCM01). SQL 2012 back end is off box, on a separate cluster (SQL01C01). Reporting Services for SQL 2012 is due to be installed on a different server (SRS01).
    My question is, when I come to sort out Reporting Services in SCCM, will I simply need to add SRS01 into SCCM as a Site System Server and install the Reporting Services Point onto SRS01?
    I realise I could simply wait for the sql guys to sort the install of SRS and then test it myself but it might be a while before that gets done so I thought I'd ask....Thanks for the help

     will I simply need to add SRS01 into SCCM as a Site System Server and install the Reporting Services Point onto SRS01?
    Correct, although the other way around. Remember you have to make SCCM01$ a local administrator on SRS01.
    Gerry Hampson | Blog:
    www.gerryhampsoncm.blogspot.ie | LinkedIn:
    Gerry Hampson | Twitter:
    @gerryhampson

  • SCCM 2012 R2 Cu1: Can I reinstall the Reporting Services Point role without delete or change the SSRS-DB?

    Hi, I have some issue with the reports,
    Can I reinstall the SCCM Reporting Services Point role without delete or change the SSRS-DB (just reset the SCCM SSRS function)?
    I have saved/backup the custom made reports.
    /SaiTech

    Yes you can remove and reinstall the Role.  I had to do this recently on our SCCM 2012 R2 due to an issue with the reports not loading.   Found out that the problem with reports was from the upgrade to R2 from 2012 SP1 and was able to run
    a command to re-register the reports with WMI.  I actually removed the role, uninstalled reporting services feature from SQL, deleted the report databases, reinstalled the SQL feature, configured the reporting databases again, added the role back, and
    ran the following command.
    mofcomp "C:\Program Files (x86)\Microsoft SQL Server\100\Shared\sqlmgmproviderxpsp2up.mof"
    This allowed all my reports to register as they should have and run without errors.  If you are having similar problems, you may be able to just run that command to get reports running without all the extra work I did.  For us we were getting an
    invalid Class error in the srsrp.log.
    Brian

  • [Forum FAQ] Reporting Service Point cannot be installed on a Site System Server running SQL Server 2012 SP1

    Symptom: When you install Reporting Service Point role on a Site System Server running SQL Server
    2012 SP1, you may encounter an issue that the Reporting Service Point role cannot be installed. The error log “srsrpMSI.log” and “srsrpsetup.log” may throw the error as shown in Figure 1 and Figure 2.
    03:32:03:764]:
    MainEngineThread is returning 1618
    Figure 1: Error -1
    <03/03/14 03:32:03>
    srsrp.msi exited with return code: 1618
    Figure 2: Error -2
    Reason: All the two logs indicate an error return code 1618. From the KB below you may know what
    the return code means.
    ERROR_INSTALL_ALREADY RUNNING 
    1618
    Another installation is already in progress. Complete that installation before proceeding with this install.
    KB link:
    http://support.microsoft.com/kb/290158 “it is related to an Office Suite KB, anyway, the MSI return code is the same meaning”
    You can look into Resource Manager and Event Viewer to find the other currently running MSI installation. You may get a warning in Event Log that means the MSI wants to install a SQL Server
    related Component (Figure 3). The Resource Manager confirms this (Figure 4).
    Event Log:
    Event ID: 1004
    Source: Msinstaller
    Level: Warning
    Detection of product '{A7037EB2-F953-4B12-B843-195F4D988DA1}',
    feature 'SQL_Tools_ANS', component '{0CECE655-2A0F-4593-AF4B-EFC31D622982}' failed.  The resource '' does not exist.
    Figure 3: Event Log
    Figure 4: Resource Manager
    Resolution: the error is exactly what the following KB describes.
    KB Link:
    http://support.microsoft.com/kb/2793634
    After we resolve the SQL Server 2012 issue, the Reporting Service Role is installed successfully.
    Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

    This implies that ODP.NET does NOT need to be installed on a client. However, I cannot find OraOPs9.dll on a machine with Client Release 9.2 installed. Should OraOps?.dll automatically come with a Client installation of 9.2 or higher?
    ODP.NET needs to be installed on the client. OraOps9.dll is part of ODP.NET, not the Oracle Client.
    Also, if an application is built with the 10g ODP.NET, can it be run from a machine with OraOps9.dll?
    If an application is built with 10g ODP.NET, it can be run with 9.2 ODP.NET as long as you do not use any 10g APIs. The new features in 10g ODP.NET are included in the doc and the ODP.NET FAQ for your reference.

  • Data Source security settings are revert back after correct it !! (SCCM Reporting Services Point)

    I have a strange situation here: SCCM 2012 SP1 and all components are OK and running smoothly BUT all reports report the error:
    An error has occurred during report processing. (rsProcessingAborted)
    Cannot impersonate user for data source 'DataSource2'. (rsErrorImpersonatingUser)
    Log on failed. Ensure the user name and password are correct. (rsLogonFailed)
    Object reference not set to an instance of an object.
    I correct the password and click test connection and it is successful ...few seconds the setting revert back and if I change the settings totally it reverts back to as if something prevent it from change !!
    the strange thing that I tried to remove the reporting services point from the site server and the reports worked well and the setting not change
    what make the settings of the data source created by sccm 2012 reporting services point revert back preventing the report from running
    by the way all authentication and permissions are given to the account that running reports and connects to the database
    help me finding solutions and thanks for all great experts here
    Hossam Wael Elmosallamy (IT Support Engineer-ECC Solutions) MCSE - CCNA [email protected] Mobile:(011)-49464671 www.eccsolutions.net "Experience Reliability"

    I am also experiencing this issue.  I have tried modifying the Data Source credentials directly from the data source configuration on our SSRS web site.  I have also tried changing it from the CM12 Console under the Reporting services
    point, specifically the Reporting Services Point Account.  No matter how many times I change it, it will revert back to an account we don't want it conifigured for any longer.
    Mucking around in the registry, I found the following keys that seem to reference the configuration:
    HKLM\Software\Microsoft\SMS\SRSRP
    HKLM\Software\Microsoft\SMS\SRSRP\Datasource
    It appears as though the Datasource key contains the configuration under two String Values:
    Reserved 1 = User name
    Reserved 2 = guessing encrypted hash of password
    Doesn't seem like it is even an option to change the configuration here, but at least this is some more info.
    Any help on this would be great... until then, I will keep digging.

  • Reporting Services Point Role - Not installing

    Hi,
    I installed SCCM 2012 R2 and SQL Server Standard 2012 with Reporting Services. SCCM is running in secure (HTTPS) mode for both MP and DP. I have also configured SQL Reporting Services WEB URL for HTTPS (443)
    Now I'm trying to install the Reporting Service Point Role but it wont install.
    If I check Monitoring --> Reporting --> Reports its blank. Reporting Services on SQL Server is working properly.
    I have the following errors reported
    "Site Component Manager failed to configure site system "
    Site Component Manager failed to configure site system
    \\xxxx.xxx.xx to receive Configuration Manager Server Components.
    Solution: Review the previous status messages to determine the exact reason for the failure. Site Component Manager cannot install any Configuration Manager Server Components on this site system until the site system is configured successfully. Site Component
    Manager will automatically retry this operation in 60 minutes. To force Site Component Manager to immediately retry this operation, stop and restart Site Component Manager using the Configuration Manager Service Manager.
    " to receive Configuration Manager Server Components.
    Solution: Review the previous status messages to determine the exact reason for the failure. Site Component Manager cannot install any Configuration Manager Server Components on this site system until the site system is configured successfully. Site Component
    Manager will automatically retry this operation in 60 minutes. To force Site Component Manager to immediately retry this operation, stop and restart Site Component Manager using the Configuration Manager Service Manager."
    "Site Component Manager could not find an NTFS partition on site system
    \\xxxx.xxx.xx to hold the Configuration Manager Server Components' files.
    Possible cause: The site system does not contain an NTFS partition.
    Solution: Using the Windows Disk Administrator, create an NTFS partition on the site system, or convert an existing FAT partition to NTFS.
    Possible cause: The site system is not exporting the default drive letter shares, such as "\\xxxx.xxx.xx\C$", "\\xxxx.xxx.xx\D$",
    and so on.
    Solution: You might have disabled the default drive letter shares for security purposes. Configuration Manager requires these shares. Please re-enable these shares using the Windows Disk Administrator.
    Possible cause: The site system is turned off, not connected to the network, or not functioning properly.
    Solution: Verify that the site system is turned on, connected to the network, and functioning properly.
    Possible cause: Site Component Manager does not have sufficient access rights to remotely administer the site system.
    Solution: Verify that the accounts are properly configured to allow the site server to remotely administer the site system.
    Possible cause: Network problems are preventing Site Component Manager from properly accessing the site system.
    Solution: Investigate and correct any problems on your network."
    I'm a bit perplexed because the admin shares can be accessed on the servers. Any help will be appreciated.
    Thanks

    I'm also seeing these in SMS_HIERARCHY_MANAGER
    Hierarchy Monitoring detected that the SQL Server xxxx.xxx.xx Service Broker certificate has missed or is expired, and failed to remediate with Error Failed to read SQL SSB certificate..
    Any ideas why this is happening?
    I ran this query and looks like the cert is fine
    "select s.name, c.name, c.start_date, c.expiry_date
     from sys.services s
     join sys.certificates c on s.principal_id = c.principal_id
     where c.pvt_key_encryption_type = 'MK'
      and c.is_active_for_begin_dialog = 1
      and GETUTCDATE() BETWEEN c.start_date AND c.expiry_date
      and s.service_id > 2;"
    http://schemas.microsoft.com/SQL/ServiceBroker/ServiceBroker
    ConfigMgrEndpointCert
    2009-01-01 00:00:00.000
    2029-01-01 00:00:00.000
    Why does it think my cert is near expired?

  • Reporting Services Point - possibly permissions issue

    I'm having a really hard time configuring a working reporting services point in my test SCCM 2012 R2 environment and was hoping someone might be able to help me work out what's gone wrong.
    My servers are WS2008 R2.  SQL Server 2008 R2 is installed on the primary site server and holds the site database.  I installed SSRS onto a separate site server and added it as a reporting services point.  This worked, and I see the list of
    reports in the SCCM admin console.  However, when I try to run a report - either from the console or via web browser - I get this message:
    The default value expression for the report parameter 'usertokensids' contains an error.  There are no logon servers available to service the logon request. (rsRuntimeErrorInExpression)
       at Microsoft.Reporting.WinForms.ServerReportSoapProxy.OnSoapException(SoapException e)
       at Microsoft.Reporting.WinForms.Internal.Soap.ReportingServices2005.Execution.RSExecutionConnection.ProxyMethodInvocation.Execute[TReturn](RSExecutionConnection connection, ProxyMethod`1 initialMethod, ProxyMethod`1 retryMethod)
       at Microsoft.Reporting.WinForms.Internal.Soap.ReportingServices2005.Execution.RSExecutionConnection.LoadReport(String Report, String HistoryID)
       at Microsoft.Reporting.WinForms.ServerReport.EnsureExecutionSession()
       at Microsoft.Reporting.WinForms.ServerReport.SetParameters(IEnumerable`1 parameters)
       at Microsoft.ConfigurationManagement.AdminConsole.SrsReporting.ReportViewerWindowsForms.SetParameterValues_DoWork(Object sender, DoWorkEventArgs e)
    SMSAdminUI.log shows this message:
    [25, PID:3096][06/12/2014 11:24:05] :[fqdnofprimaryserver] : The request failed with HTTP status 503: Server Error.
    Now, the reason I think this is a permissions issue is because srsrp.log on the Reporting Point server shows this:
    (!) Error retrieving folders - [Login failed for user 'domain\reportingservercomputername$'.].
    (I've removed the actual name here, obviously.)
    I'm really puzzled about what's going on here, what is trying to authenticate with the SSRS server's machine credentials, and what for.  Looking in SQL Server Management Studio on the primary site server which hosts the SQL database, I can see that
    the account has a login listed and it has its default schema listed as DBO.  On the SSRS server, in Reporting Services Configuration Manager, the Report Server Service Account is set to a dedicated domain user account.  The Current Report Server
    Database Credential is set to my own Windows login using Current User - Integrated Security - I can't seem to get it to accept the dedicated user account.
    Can anyone help me figure out what's gone wrong and how I fix it, please?  I'm by no means a SQL person, and I'm at my wit's end with this!
    Thanks,
    M

    The plot thickens.
    The SSRS server has these:
    "The report server has detected a possible denial of service attack. The report server is dropping requests for service from the IP address 192.168.113.163" (this is the IP address of the primary site system, which hosts the SQL database)
    and then
    "Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database"
    The primary site system, meanwhile, has got thousands of these:
    "Login failed for user 'DOMAIN\SSRSSERVERNAME$'. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT: 192.168.113.164]" (that's the IP of the SSRS server)
    The Windows firewall is off for both systems.  They're on an isolated test network.  I still don't understand where the setting is that tells it to make SQL queries using the SSRS server's machine account, rather than the dedicated service account
    I created.
    Any more ideas?  Thanks for your help so far - I really appreciate it!

  • Trying to install Reporting Services Point on MSQL01.

    Primary Site Server : SCCM01 (SCCM2012 R2)
    Remote SQL Server: MSQL01    (SQL 2012 SP1 CU7)
    SCCM Instance: SCCM01
    Static Port:1441
    Product Version: 11.0.3393.0
    Trying to install Reporting Services Point on MSQL01.
    On MSQL01 C:\SMS\Logs\SRSRP.Log
    Successfully created srsserver
    Reporting Services URL from Registry [https://msql01.thg.local/ReportServer_SCCM/ReportService2005.asmx]
    The request failed with HTTP status 404: Not Found.
    (!) SRS not detected as running
    Failures reported during periodic health check by the SRS Server MSQL01.THG.LOCAL.

    Did you install SRS as part of the SQL install?
    If so then follow the tutorial here
    http://prajwaldesai.com/deploying-sccm-2012-part-12-installing-and-configuring-reporting-services-point/
    Also some further details from Torsten 
    http://social.technet.microsoft.com/Forums/en-US/7af9721c-ec04-42bc-bf3f-c36696d12606/reporting-error
    Cheers
    Paul | sccmentor.wordpress.com

  • Reporting Services Point SSL after Role installed

    Scenario,
    Reporting Services (SQL 2012) installed on a remote server and not configured with SSL.  Reporting Services Point installed and functioning correctly.
    We now have enabled SSL in RS Configuration using a cname for the certificate (sccmreports.domain.com) and it is working via web browser, however when I attempt to remove the port 80 binding it breaks SCCM's ability to connect to the reporting point via
    the admin console.   Presumably, if SSL is not enabled prior to installing the RSP that SCCM only knows to connect via HTTP?
    If this is the case, outside of uninstalling and re-installing the RSP now is there a way to "tell" SCCM to use HTTPS to connect?  Maybe its a different issue altogether?
    Thanks!

    The SSRS connection info is stored in Site control file, which is in the view vSMS_SC_SiteControlXML. If you change the SSRS address manually, the info cannot be updated automatically so that you must reinstall SSRS.
    Juke Chou
    TechNet Community Support

  • Reporting Services point

    I'm trying to install the reporting services role and have hit a road block. We have one primary site and the site database is in a cluster with 3 nodes. The SQL Reporting Services is not installed on the cluster nodes but is installed on its own database
    server. Does anyone know if this configuration can be used? If so any help would be appreciated.
    I think I should be able to add a new Site System Role for the server hosting the SQL Reporting Services in Administration and install the reporting services point on that site system.  
    Thank you

    Hi,
    Please refer to the links below:
    Deploying SCCM 2012 Part 12 – Installing and Configuring Reporting Services Point
    http://prajwaldesai.com/deploying-sccm-2012-part-12-installing-and-configuring-reporting-services-point/
    Configuring Reporting in Configuration Manager
    http://technet.microsoft.com/en-us/library/gg712698.aspx#BKMK_InstallReportingServicesPoint
    Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • FQDN or NetBIOS for SQL Reporting Services Point installation in a cluster

    Hi Folks
    We have a SQL cluster for config mgr database & SQL reporting services installed on nodes because it is not cluster aware. During SCCM 2012 installation, we mentioned the details of SQL cluster only & it got installed successfully. When we checked
    in console, it is showing 3 site servers  related to SQL. SQL cluster is having site system role only & site database role moved under 2 nodes. Only NetBIOS names of the SQL nodes are being displayed in console.
    Now when I installed reporting service point role by selecting one of the node, wizard picks the FQDN of this node automatically & role installed successfully.
    Now in the console, I have another site server listed publishing the FQDN of the same node which I selected during installation which means one SQL node (site database role present at this) is displaying with NetBIOS name & the same SQL node
    (reporting services point role at this) is displaying with FQDN.
    My concerns is that - 
    Is there any issue if same SQL node displaying 2 times in SCCM console i.e. with NetBIOS name & with FQDN name?
    Why reporting services point role not placed under the node which is already there with NetBIOS name?
    I hope I explained my issue properly however If you guys need any more information regarding this, then let me know. 
    Cheers | Navdeep Sidhu

    This is the default behavior when installing site DB on cluster - all nodes will be visible as NetBIOS.
    I face a problem in two separate environments with SQL cluster when configuring Auto client push for servers, you will get the following error message in CCM.log in site server:
    SQL Server Native Client 11.0][SQL Server]Invalid length parameter passed to the LEFT or SUBSTRING function. : sp_CP_CheckNewAssignedMachine
    AND
    Failed to execute SQL cmd exec [sp_CP_CheckNewAssignedMachine]
    I believe this is a bug in the product.
    There is a workaround FIX editing the SP in SQL DB but it is UNSUPPORTED.
     

  • Reporting services point - Critical error

    guys,
    This has been working and has suddenly stopped.  My SQL environment has not changed from  being a  Remote SQL instance
    running SQL 2008 SP3 CU9.
    My problem is that the "Reporting service point" component has a critical state.  The error says 7403  "The report server service is not running on Reporting Service Point server "***"; start the service to enable reporting.
    I have tried stopping and starting the service but I still receive the error every hour.  Reports from the web URL just sit at a "loading" state and no reports appear in SCCM.  Any thoughts ?

    Hi Joyce, 
    I already posted a part of the log that I believe is part of the error.  I am not sure how to resolve it thought
    Reporting Services URL from Registry [https://sql.***.org/ReportServer/ReportService2005.asmx]SMS_SRS_REPORTING_POINT
    The request failed with http status 404 : not found
    (!) SRS not detected as running
    SMS_SRS_REPORTING_POINT
    8/21/2014 2:54:44 PM
    4012 (0x0FAC)
    Failures reported during periodic health check by the SRS Server SQL.*****.ORG.
    SMS_SRS_REPORTING_POINT
    8/21/2014 2:54:44 PM
    4012 (0x0FAC)

Maybe you are looking for

  • Is it possible to call SAP RFC by using ODI

    Hi guys, I connected to a SAP system by using ODI. I can fetch SAP tables but is there a way to call a RFC by using ODI? Thanks.

  • Linking errors to forum

    The links that are being generated by the forum so that I can view the replys to the messages posted are coming up with an error that states that the page I am requesting cannot be displayed. this hasn't happened in the past, but I thought you might

  • Help with JTextArea

    Hi, I am working on a GUI Application and need some hlep. 1] When I click on Next Item button, it should clear the previously entered values of TextFields. How do I do this? 2] How do I display text in a JTextArea which appears in a Pop-up window? I

  • In support project which type of requests can be send by users.

    Hi All,      Give me some examples of user requests and solutions.      Thank You.

  • How can i read ebooks

    i have just joined the apple world and want to know how to download books or some type of e reader like i books there are a ton of free epub books out there i just dont know the proper way to store open and organize thank you in advance