Reinstall the reporting services point

We are running SCCM 2012 R2 and using SQL 2008 R2. I had to create a new reporting services database and reinstall the reporting services point. After the reinstall I am now finding the below errors in the srsrp.log log.
Timed Out... SMS_SRS_REPORTING_POINT 6/12/2014 10:15:26 AM 7156 (0x1BF4)
Set configuration SMS_SRS_REPORTING_POINT 6/12/2014 10:15:26 AM 7156 (0x1BF4)
Check state SMS_SRS_REPORTING_POINT 6/12/2014 10:15:26 AM 7156 (0x1BF4)
Check server health. SMS_SRS_REPORTING_POINT 6/12/2014 10:15:26 AM 7156 (0x1BF4)
Successfully created srsserver SMS_SRS_REPORTING_POINT 6/12/2014 10:15:26 AM 7156 (0x1BF4)
Reporting Services URL from Registry [https://server/ReportServer/ReportService2005.asmx] SMS_SRS_REPORTING_POINT 6/12/2014 10:15:26 AM 7156 (0x1BF4)
The request failed with HTTP status 401: Unauthorized. SMS_SRS_REPORTING_POINT 6/12/2014 10:15:26 AM 7156 (0x1BF4)
(!) SRS not detected as running SMS_SRS_REPORTING_POINT 6/12/2014 10:15:26 AM 7156 (0x1BF4)
Failures reported during periodic health check by the SRS Server server. SMS_SRS_REPORTING_POINT 6/12/2014 10:15:26 AM 7156 (0x1BF4)
Registry change SMS_SRS_REPORTING_POINT 6/12/2014 10:15:26 AM 7156 (0x1BF4)
Waiting for changes for 1 minutes SMS_SRS_REPORTING_POINT 6/12/2014 10:15:26 AM 7156 (0x1BF4)
Timed Out... SMS_SRS_REPORTING_POINT 6/12/2014 10:16:26 AM 7156 (0x1BF4)
Set configuration SMS_SRS_REPORTING_POINT 6/12/2014 10:16:26 AM 7156 (0x1BF4)
Check state SMS_SRS_REPORTING_POINT 6/12/2014 10:16:26 AM 7156 (0x1BF4)
Check server health. SMS_SRS_REPORTING_POINT 6/12/2014 10:16:26 AM 7156 (0x1BF4)
Successfully created srsserver SMS_SRS_REPORTING_POINT 6/12/2014 10:16:26 AM 7156 (0x1BF4)
Reporting Services URL from Registry [https://server/ReportServer/ReportService2005.asmx] SMS_SRS_REPORTING_POINT 6/12/2014 10:16:26 AM 7156 (0x1BF4)
The request failed with HTTP status 401: Unauthorized. SMS_SRS_REPORTING_POINT 6/12/2014 10:16:26 AM 7156 (0x1BF4)
(!) SRS not detected as running SMS_SRS_REPORTING_POINT 6/12/2014 10:16:26 AM 7156 (0x1BF4)
Failures reported during periodic health check by the SRS Server server. SMS_SRS_REPORTING_POINT 6/12/2014 10:16:26 AM 7156 (0x1BF4)
Registry change SMS_SRS_REPORTING_POINT 6/12/2014 10:16:26 AM 7156 (0x1BF4)
Waiting for changes for 1 minutes SMS_SRS_REPORTING_POINT 6/12/2014 10:16:26 AM 7156 (0x1BF4)

Hi,
Could you open http://SQLServerName/ReportServer and
http://SQLServerName/Reports in IE?
Best Regards,
Joyce
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.

Similar Messages

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

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?

[Forum FAQ] Configuration Manager Console shows nothing if you change SSRS to using SSL after Reporting Service Point is installed

If the SSRS is changed to SSL mode and http binding is removed after Reporting Service Point is installed. The Configuration Manager Console shows nothing in Reporting Pane. After digging into this problem, the cause is that the SSRS information has not
been updated in Configuration Manager Database. The following steps are taken for finding the root cause.
1. After changing to SSL, the Reporting Service Point log shows the error as shown in Figure 1.
The request failed with HTTP status 404: Not Found.
(!) SRS not detected as running
Failures reported during periodic health check by the SRS Server DB2.SCJIZHO.COM.
Figure 1
From the error, seems the cause was the Reporting Service Point detected a wrong port. We digged around in Registry and found the information is a Registry key named ReportServerUri at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\SRSRP. After changing the Report
Server address to https. The error is gone as shown in Figure 2. But the issue remains, the Console still shows nothing. It is not a right direction.
Figure 2
2. Open the Console log file, it also shows some valuable information.
instance of __ExtendedStatus
                Operation = "ExecQuery";
                ParameterInfo = "SELECT * FROM SMS_Site WHERE SiteCode = 'PRI'";
                ProviderName = "WinMgmt";
\r\n
[1, PID:3136][04/24/2014 01:46:00] :Property: 'LastModifiedTime'\r\nSystem.Management.ManagementException\r\nNot found \r\n   at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
   at System.Management.PropertyData.RefreshPropertyInfo()
   at System.Management.PropertyDataCollection.get_Item(String propertyName)
   at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObjectBase.get_Item(String name)\r\nManagementException details:
[52, PID:3136][05/11/2014 20:14:15] :[ReportProxy] - User-specified default Reporting Point [PRI.scjizho.com] could not be found, [DB2.scjizho.com] is now the default Reporting Point (Figure 3).
Figure 3
It seems the Console wants to access the old http site and it fails to get into the site for sure. Actually, the Site Configuration information is come from Site Control File and as we all know that ConfigMgr 2012 doesn’t store the Site Control file in the
file system. However, it’s stored in the SQL database (as XML file). The XML file is stored in a view named vSMS_SC_SiteControlXML. This view is a read-only view. We cannot edit it directly. The related table stored the SSRS information for this view is SC_SysResUse_Property.
Running the following query will list the SSRS address. We can see the address is still the old one. This is why the Console shows nothing.
SELECT
name,
value2
FROM dbo.SC_SysResUse_Property
where name
='ReportServerUri'
or name=
'ReportManagerUri'
Remarks:
This article is just to let you know why the Console cannot show the Reports after changing to SSL mode. We do not intend to make you change the table in Database, if you want to change it, you will be at your own risk. The real solution to this situation
is to reinstall your Reporting Service Point.
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Ok, but how do you solve this problem? Does uninstalling the RP and adding it back solve this problem?
http://www.enhansoft.com/

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.

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 - 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)

Reporting Services Point - installation location help

I have my SCCM 2012 environment role(s) split up. Granted other roles exist in each location but in a nut shell it's like this:
Server1 - SCCM primary site with MP
Server2 - SCCM DP, software update point, etc
Server3 - Pure DB server hosting multiple other systems DB's and the SCCM DB
I do not want to install the "Reporting Services Point" on the DB server, rather have it installed on Server1, aka the primary MP site server.
Do I need to do or have anything special installed on Server1 to use it as the Reporting Services Point? I am having a hard time finding the requirements needed for just the Reporting Services Point role.

try these links
http://technet.microsoft.com/en-ca/library/gg712698.aspx
http://social.technet.microsoft.com/wiki/contents/articles/15475.how-to-successfully-install-reporting-services-point-role-in-sccm-2012-sp1.aspx
I prefer having the SQL server (DB) and SSRS on the primary site server, but that is a matter of preference / simplicity.

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.

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

Reporting Services Point Error

A new Reporting Services Point installation on a remote SSRS server succeeds, but reports are not created. The srsrp.log shows the following:
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.WebServer.ReportingService2005Impl.SetProperties(String Item, Property[] Properties)~ at Microsoft.ReportingServices.WebServer.ReportingService2005.SetProperties(String Item, Property[] Properties)
Why does 'NT AUTHORITY\SYSTEM' need permissions on SSRS? When the Reporting Services Point was installed, I specifed an AD account with local admin rights on the SSRS server for the installation account. That account was also given SSRS System Administrator
permissions in SSRS.
Has anyone encountered this before? Any thoughts?
Thanks,
Jeff

One more item of note. . .SSRS is configured to use Kerberos authentication. i.e.,
<RSWindowsNegotiate />
I am reviewing the following to see if there are any relevant ideas:
https://msdn.microsoft.com/en-us/library/cc281253.aspx
Thanks,
Jeff

[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.

The report server service is not running on Reporting Service Point server

Hi,
I have encountered a problem, my reporting service point has stopped working. (SCCM 2012 R2)
In srsrp.log:
Check state SMS_SRS_REPORTING_POINT
12/15/2014 5:48:54 AM 3152 (0x0C50)
Check server health. SMS_SRS_REPORTING_POINT
12/15/2014 5:48:54 AM 3152 (0x0C50)
Successfully created srsserver SMS_SRS_REPORTING_POINT
12/15/2014 5:48:54 AM 3152 (0x0C50)
Reporting Services URL from Registry [https://s-hub-sql1.domain.local/ReportServer/ReportService2005.asmx]
SMS_SRS_REPORTING_POINT 12/15/2014 5:48:54 AM
3152 (0x0C50)
The request failed with HTTP status 404: Not Found.
SMS_SRS_REPORTING_POINT 12/15/2014 5:48:54 AM
3152 (0x0C50)
(!) SRS not detected as running SMS_SRS_REPORTING_POINT
12/15/2014 5:48:54 AM 3152 (0x0C50)
Failures reported during periodic health check by the SRS Server S-HUB-SQL1.domain.local.
SMS_SRS_REPORTING_POINT 12/15/2014 5:48:54 AM
3152 (0x0C50)
Registry change SMS_SRS_REPORTING_POINT
12/15/2014 5:48:54 AM 3152 (0x0C50)
Waiting for changes for 1 minutes SMS_SRS_REPORTING_POINT
12/15/2014 5:48:54 AM 3152 (0x0C50)
Timed Out... SMS_SRS_REPORTING_POINT
12/15/2014 5:49:54 AM 3152 (0x0C50)
Set configuration SMS_SRS_REPORTING_POINT
12/15/2014 5:49:54 AM 3152 (0x0C50)
In windows event log:
On 12/15/2014 6:39:28 PM, component SMS_SRS_REPORTING_POINT on computer S-HUB-SQL1 reported: The report server service is not running on Reporting Service Point server "S-HUB-SQL1"; start the service to enable reporting.
In configuration manager service manager, the service sms_srs_reporting_point is running.
In Reporting services configuration manager, the service is running.
If I restart the reporting service, it doesn't helps.
What is not properly?

I've already found the reason why all stopped working - someone deleted the report manager URL HTTPS bindings (in Report services configuration manager). Added it back, than reporting started to work. Awww!

The report server service is not running on reporting service point server ID: 7403 SMS_SRS_REPORTING_POINT

Hi,
I'm having a problem when I try to install Report Services point, I can browser my report server from my SCCM site but when I install the Reporting point the reports do not load to report server.
If I check at my reportserver machine all reports are in the disk.
I have one machine with SQL Server 2012 Std SP1 and another computer with SCCM 2012 SP1.
Error at srsrp.log
SMS_EXECUTIVE started SMS_SRS_REPORTING_POINT as thread ID 3308 (0xCEC).   SMS_SRS_REPORTING_POINT   14/01/2013 14:15:40   3356 (0x0D1C)
This is a SRS Reporting Point Role as SRSRP registry key exists.   SMS_SRS_REPORTING_POINT   14/01/2013 14:15:40   3308 (0x0CEC)
Waiting for changes for 0 minutes   SMS_SRS_REPORTING_POINT   14/01/2013 14:15:40   3308 (0x0CEC)
Timed Out...   SMS_SRS_REPORTING_POINT   14/01/2013 14:15:40   3308 (0x0CEC)
Reporting Services URL from Registry [http://srv-bd/ReportServer/ReportService2005.asmx]   SMS_SRS_REPORTING_POINT   14/01/2013 14:15:44   3308 (0x0CEC)
The request failed with an empty response.   SMS_SRS_REPORTING_POINT   14/01/2013 14:15:44   3308 (0x0CEC)
(!) SRS not detected as running   SMS_SRS_REPORTING_POINT   14/01/2013 14:15:44   3308 (0x0CEC)
STATMSG: ID=7403 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_SRS_REPORTING_POINT" SYS=SRV-BD.F1MAIS.LOCAL SITE=F1M PID=2052 TID=3308 GMTDATE=Mon Jan 14 17:15:44.571 2013 ISTR0="SRV-BD.F1MAIS.LOCAL" ISTR1="" ISTR2=""
ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0   SMS_SRS_REPORTING_POINT   14/01/2013 14:15:44   3308 (0x0CEC)
Failures reported during periodic health check by the SRS Server SRV-BD.F1MAIS.LOCAL.   SMS_SRS_REPORTING_POINT   14/01/2013 14:15:44   3308 (0x0CEC)
Waiting for changes for 1 minutes   SMS_SRS_REPORTING_POINT   14/01/2013 14:15:44   3308 (0x0CEC)
Timed Out...   SMS_SRS_REPORTING_POINT   14/01/2013 14:16:44   3308 (0x0CEC)
Reporting Services URL from Registry [http://srv-bd/ReportServer/ReportService2005.asmx]   SMS_SRS_REPORTING_POINT   14/01/2013 14:16:44   3308 (0x0CEC)
The request failed with an empty response.   SMS_SRS_REPORTING_POINT   14/01/2013 14:16:44   3308 (0x0CEC)
(!) SRS not detected as running   SMS_SRS_REPORTING_POINT   14/01/2013 14:16:44   3308 (0x0CEC)
Failures reported during periodic health check by the SRS Server SRV-BD.F1MAIS.LOCAL.   SMS_SRS_REPORTING_POINT   14/01/2013 14:16:44   3308 (0x0CEC)
Waiting for changes for 1 minutes   SMS_SRS_REPORTING_POINT   14/01/2013 14:16:44   3308 (0x0CEC)
Timed Out...   SMS_SRS_REPORTING_POINT   14/01/2013 14:17:44   3308 (0x0CEC)
Thanks!
Rodrigo Daphanis

It looks like the MS support team just published a support tip to this problem -
http://blogs.technet.com/b/configurationmgr/archive/2013/03/06/support-tip-no-reports-show-up-in-the-console-after-installing-a-system-center-2012-configuration-manager-reporting-server.aspx
Nick Moseley | http://t3chn1ck.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

Reinstall the reporting services point

Similar Messages

Maybe you are looking for