Report Services Cluster

Once upon a time in V9i R1 and before, one could configure a report service cluster to get load balancing and performance improvements; this has been deprecated on iAS10gR2.
What is the equivalent configuration in this new version? Is there any documentation? How do we setup multiple report services addressed by one URL that can share the same cache and same source (deploy reports once).
Thanks for any help

panos,
i am not quite clear what your question is. what kind of information are you looking for ? what is the exact problem in your environemnt ? also please specify exact platform and version of reports you are using.
thanks,
ph.

Similar Messages

Reporting Services as a generic service in a failover cluster group?

There is some confusion on whether or not Microsoft will support a Reporting Services deployment on a failover cluster using scale-out, and adding the Reporting Services service as a generic service in a cluster group to achieve active-passive high
availability.
A deployment like this is described by Lukasz Pawlowski (Program Manager on the Reporting Services team) in this blog article
http://blogs.msdn.com/b/lukaszp/archive/2009/10/28/high-availability-frequently-asked-questions-about-failover-clustering-and-reporting-services.aspx. There it is stated that it can be done, and what needs to be considered when doing such a deployment.
This article (http://technet.microsoft.com/en-us/library/bb630402.aspx) on the other hand states: "Failover clustering is supported only for the report server database; you
cannot run the Report Server service as part of a failover cluster."
This is somewhat confusing to me. Can I expect to receive support from Microsoft for a setup like this?
Best Regards,
Peter Wretmo

Hi Peter,
Thanks for your posting.
As Lukasz said in the
blog, failover clustering with SSRS is possible. However, during the failover there is some time during which users will receive errors when accessing SSRS since the network names will resolve to a computer where the SSRS service is in the process of starting.
Besides, there are several considerations and manual steps involved on your part before configuring the failover clustering with SSRS service:
Impact on other applications that share the SQL Server. One common idea is to put SSRS in the same cluster group as SQL Server. If SQL Server is hosting multiple application databases, other than just the SSRS databases, a failure in SSRS may cause
a significant failover impact to the entire environment.
SSRS fails over independently of SQL Server.
If SSRS is running, it is going to do work on behalf of the overall deployment so it will be Active. To make SSRS Passive is to stop the SSRS service on all passive cluster nodes.
So, SSRS is designed to achieve High Availability through the Scale-Out deployment. Though a failover clustered SSRS deployment is achievable, it is not the best option for achieving High Availability with Reporting Services.
Regards,
Mike Yin
If you have any feedback on our support, please click
here
Mike Yin
TechNet Community Support

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.

SSL Cert for 2008 R2 Reporting Services that is installed on a Failover Cluster - server address mismatch?

I utilized the idea from
http://www.mssqltips.com/sqlservertip/2778/how-to-add-reporting-services-to-an-existing-sql-server-clustered-instance/ to install 2008 R2 Reporting Services on a new Clustered SQL instance. In short, create the new Clustered SQL instance on Node1,
installing Reporting Services with it. Then on Node2, Add a Failover Cluster Node (without choosing Reporting Services); following that up with starting the SQL setup.exe with a cmd to bypass a check so that I can then install the Reporting Services
feature on Node2. It points out using the SQL Cluster Network name for connecting to Reporting Services.
I verified upon failover that I could still access the Reports and ReportServer URLs. However, when wanting to add an SSL certificate to the RS configuration, I run into the warning of "mismatched address - the security certificate presented by
this website was issued for a different website's address", where I can continue and get to the Reports or ReportManager URLs.
I played with different certs (internal CA created) and SANs and other things, but I still get this error with the cert. The Reports URL, for example, is <a href="https:///Reports">https://<SQLClusterNetworkName>/Reports, and the
cert has a CN and Friendly Name of SQLClusterNetworkName (with SAN of DNS: SQLClusterNetworkName.<domain>), but the error still happens.
What am I missing to eliminate the mismatched address warning when using the SQLClusterNetworkName as the base of the URLs?

I got it working by using the FQDN as the common name on the SSL cert, with FQDN in RS URLs.

Service Accounts for Reporting Service in SQL Server Failover Cluster setup

I am setting up 2 Report Services (SSRS) in SQL Failover Clustering (Version: 2012SP1) on Windows 2012, as part of scale out architecture.
There are 2 options to configure the service account for SSRS:
Option 1) Using domain accounts, as what I have done for DB Engine and SQL Agent.
Option 2) accept the default, which is virtual account for SSRS. Per documentation URL:
http://msdn.microsoft.com/en-us/library/ms143504.aspx
which is the recommended one? is it option 2?
There is security note on above URL as well, but does not clearly mention that option 1 is not recommended.
Security Note: Always run SQL Server services by using the lowest possible user rights. Use a MSA or virtual account when possible. When MSA and virtual accounts are not possible, use a specific low-privilege user account or domain account instead
of a shared account for SQL Server services. Use separate accounts for different SQL Server services. Do not grant additional permissions to the SQL Server service account or the service groups. Permissions will be granted through group membership or granted
directly to a service SID, where a service SID is supported.
Thanks very much for your help!

Hi Luo Donghua,
In SQL Server Failover Cluster Instance, personally two options can run well. If you use the virtual account for SQL Server Reporting Service. Virtual accounts in Windows Server 2008 R2 and Windows 7 are managed local accounts that provide the features to
simplify service administration. The virtual account is auto-managed, and the virtual account can access the network in a domain environment.
Of cause, you can also use domain accounts in your clustering.
Just make sure your service account is set up here, or that it is using a proper built-in account.For more information, see:http://ermahblerg.com/2012/11/08/cluster-ssrs-in-2008/
Thanks,
Sofiya Li
Sofiya Li
TechNet Community Support

SCCM 2012 - Migrating SQL components to cluster including Reporting Services

Current SCCM 2012 environment:
- CAS with database on remote SQL (non-cluster) server in a named instance - SQLSRV\CASINST
- SQL Reporting Services in also installed in the SQLSRV\CASINST instance
- The SCCM Reporting Services Point role is installed on the SQLSRV\CASINST instance
- Primary server with database on the same remote SQL (non-cluster) server in a different named instance - SQLSRV\PRIINST
Now I would like to move all of the database stuff to an existing SQL 2008 R2 cluster (SQLCLUSTER) and decommission the SQLSRV server. SQLCLUSTER already exists and the default instance is already in use (for other applications) for both database engine
services and reporting services.
From my understanding:
- SQL 2008 R2 Reporting Services cannot be clustered
- Best practise is to install Reporting Services Point on a remote site server rather than a CAS server
- SSRS can be installed on nodes in SQL cluster as standalone installs - with the caviat that they don't use instance names already in use
So I plan to:
- Move CAS database to new named instance on cluster eg SQLCLUSTER\CASINST
- Move primary database to new named instance on cluster eg SQLCLUSTER\PRIINST
- Install SQL Reporting Services on one of the cluster nodes (unclustered) using a named SSRS instance eg SQLCLUSTERNODE1\SCCMREPORTING
- This article points out some interesting results of not have a default instance - http://magalhaesv.wordpress.com/2012/05/24/system-center-configuration-manager-x-sql-server-reporting-services-x-wmi-english-version/
- Move Reporting Services Point from SQLSRV\CASINST to the cluster node eg SQLCLUSTERNODE1\SCCMREPORTING
I have read on some forums (eg
http://social.msdn.microsoft.com/Forums/en-US/sqlsetupandupgrade/thread/40ad0cb4-a464-4576-b824-957ed6e1b2e2) things like '' If you have an app like SCCM that requires a default instance of SSRS, you are out of luck if your cluster already has a default
instance of the database engine.", but I cannot find this anywhere in Microsoft documentation. From the MS documentation (http://technet.microsoft.com/en-us/library/7fd0d4f5-14e0-4ec7-b2e6-3b67487df555#BKMK_InstallReportingServicesPoint)
I understand that as long the current user has read access to WMI on the remote site server where SQL Reporting Services is installed, you should be able to use a named instance for SQL Reporting Services and successfully install the Reporting Services Point
on it.
So a 2 part question:
- Anybody see any obvious flaws in my high level plan?
- Anybody care to comment on the SCCM requiring a default instance of SSRS?
My Microsoft Core Infrastructure & Systems Management blog -
blog.danovich.com.au

Yes, I know this is an old post, I’m trying to clean them up, Did you figure this out, if so how?
http://www.enhansoft.com/
Hi Garth,
Yes we moved the DBs and RS as outlined above. As expected, we needed to have a default instance of RS because otherwise the SCCM console doesn't see the Reporting Services instance when you try to deploy the Reporting Services site role.
So the above plan worked.
My Microsoft Core Infrastructure & Systems Management blog -
blog.danovich.com.au

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 Service acting strangely

Whenever I start the SQL Reporting Services Service, the service starts successfully, but immediately logs three failed login attempts in the security event log. The audit failure reports this:
An account failed to log on.
Subject:
Security ID: [domain]\[authorized service account]
Account Name: [authorized service account]
Account Domain: [domain]
Logon ID: 0x19a662b7
Logon Type: 2
Account For Which Logon Failed:
Security ID: NULL SID
Account Name: [owner of reporting services database; different from service account above]
Account Domain: [domain]
Failure Information:
Failure Reason: Unknown user name or bad password.
Status: 0xc000006d
Sub Status: 0xc000006a
Process Information:
Caller Process ID: 0x508
Caller Process Name: D:\MSRS10_50.ORCHESTRATE_PROD\Reporting Services\ReportServer\bin\ReportingServicesService.exe
Network Information:
Workstation Name: [SQL Server]
Source Network Address: -
Source Port: -
Detailed Authentication Information:
Logon Process: Advapi
Authentication Package: Negotiate
Transited Services: -
Package Name (NTLM only): -
Key Length: 0
This event is generated when a logon request fails. It is generated on the computer where access was attempted.
The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).
The Process Information fields indicate which account and process on the system requested the logon.
The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
The authentication information fields provide detailed information about this specific logon request.
- Transited services indicate which intermediate services have participated in this logon request.
- Package name indicates which sub-protocol was used among the NTLM protocols.
- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
The SQL Server log reports this:
Date  1/24/2014 10:40:05 AM
Log  SQL Server (Current - 1/24/2014 10:00:00 AM)
Source  Logon
Message
Login failed for user '[domain]\[authorized service account]'. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT: <local machine>]
I don't even know where to start on this. Reporting services and replication were working fine before the vendor started poking around. I don't know what (if anything) they changed. The logs show that the ReportService database and the
ReportServicesTempDB had indices restored just before the error started showing up.
Help?

Hi goodros_nemesis,
If you’re getting a login failed for your Windows user which you’re sure you put in the sysadmins role. And based on the error message “Login failed for user '[domain]\[authorized service account]'. Reason: Token-based server access validation failed with
an infrastructure error. Check for previous errors. [CLIENT: <local machine>]”, it’s probably because UAC isn’t passing all your group memberships to SSMS when you run it, and therefore giving you access denied.
To fix this issue, please try right clicking and running as administrator and seeing if it goes away. Of course if we added our user explicitly we’re probably fine, but just to get a cluster up and running. We can add domain admins user to the DB, and of
course that’s a membership that UAC will mask.
If there are any misunderstanding, please elaborate the issue for further investigation.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

FEP 2010 with Reporting Services in Clsster

1) It¡s not supported reporting services clustering (2 nodes), but i can install reporting in both nodes sharing report database. This ReportDatabase is installed in a instance (Instance1) onto the same cluster
2) I've create teow SCCM Reportin services point (SRS1 y SRS2)
3) When I launch FEP installation (basic), i can select
http://SRS1/reportServer or http://SRS2/reportServer.
4) But...is supported input URL manual to http://Instance1/ReportServer
Thanks

This is old post and there have been several changes in FEP, now the successor of FEP is System Center Endpoint Protection (SCEP) and several things been improved. Try reproduce your issue in SCEP and if problem persist, please post it as a new question.

Error in sql 2008 reporting services with sharepoint 2013

i have database sql 2008r2 and sharepoint 2013 enterprise
database is in cluster server and sharepoint have 2 servers one for webfront end and one for services.
im tring to configer ssrs in the web front end server for sharepoint and i install sql 2008 add on for sharepoint 2010 but still have this error
The configuration parameter SharePointIntegrated is set to True but Share
Point Object Model cannot be loaded. The error was:
System.IO.FileNotFoundException: Could not load file or assembly
'Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral,
PublicKeyToken=71e9bce111e9429c' or one of its dependencies. The system cannot
find the file specified. File name: 'Microsoft.SharePoint, Version=14.0.0.0,
Culture=neutral, PublicKeyToken=71e9bce111e9429c' at
Microsoft.ReportingServices.SharePoint.Objects.RSSPImpSecurity.set_StaticCatchAccessDeniedException(Boolean
value) at
Microsoft.ReportingServices.SharePoint.Server.SharePointServiceHelper..ctor() at
Microsoft.ReportingServices.SharePoint.Server.SharePointServiceHelperFactory.get_ServiceHelper()
WRN: Assembly binding logging is turned OFF. To enable assembly bind failure
logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog]
(DWORD) to 1. Note: There is some performance penalty associated with assembly
bind failure logging. To turn this feature off, remove the registry value
[HKLM\Software\Microsoft\Fusion!EnableLog]. .
(rsSharePointObjectModelNotInstalled)
and befour that i was install sql 2012 add on for sharepoint 2013 but was the same error so i did uninstall for it
this error when i try to open reporting services url
Thanks for any help :) my blog is: http://www.waelk.com

SharePoint 2013 only supports SSRS 2012 SP1 - http://msdn.microsoft.com/en-us/library/gg492257.aspx. You'll need to upgrade your SSRS instance to 2012 SP1.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

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?

SCCM 2012 - Reporting Services - No srsrpsetup.log file

Hi all,
just in the process of moving from SCCM 2007 to 2012 R2. Here's the set up: SCCM installed on Win 2012 R2 box, SQL back end is off box on a Win 2012 R2 cluster, SQL Reporting Services is installed on a dedicated Win 2012 R2 box.
I've installed the Reporting Services Point onto the SRS01 box (which also installed the Site system and Component server roles). The role seems to have instlled ok - it's popped up under the Component Status as Healthy and the State Messages look ok:
I was under the impression that I should then see a new log file (SRSRPSetup.log) appear in the install directory (D:\Program Files\Microsoft Configuration Manager\Logs) but so far nothing's appeared. Since the log files are usually the best to start
troubleshooting I'm a bit stumped as to where to begin troubleshooting this. Does anyone have any suggestions as to why the log file may not have appeared?
Thanks for the help!

Ignore this, just had a poke around on the SRS server and found the log files under D:\SMS\logs. Should have realised sine the role was installed on the SRS01 server, that's naturally where the role installation logs would be located!

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

2 Reporting services point configure

Hi,
In our environment we configured Reporting services point in stand alone primary server and working fine. Also we migrate reports from sccm 2007. Now my question is
Shall I configure one more Reporting services point in helper server. If i configure the second one, How it's work, It's work as high availability(load balance shared one another) or it will work as redundancy. If the second one contain the same reports
for the first one?. Before install the second RP what we consider?
Regards
Gokulnath

If i create second RP how it's workflow?
There is no workflow for this.
There are two completely different RP and if you have any custom reports you will MANUALLY deploy the report to both RP, etc...
Honestly I have never seen the requirement that RP be HA, Even if I did the only solution that I would give is for them to create a cluster Hyper-v server, then create a VM on top of the cluster and Then add SSRS to that VM. The cost for this would
be nuts...
I would push back on this and ask why RP need to be HA? Is CM12 setup as HA? If so how did you set it up?
http://www.enhansoft.com/

Installation Reporting Services Point Role

I have following configuration
SCCM 2012 SP1 (Clean installation) | SQL 2008 SP3 CU4 Named instances | OS: Windows 2008 SP2
SQL Cluster for CAS | Dedicated SQL Server for each primary site (All my roles are separated on dedicated servers)
For SSRS I've been told that this is not cluster aware so I've told my DBA to install the SSRS instance on SQL Server used on my primary site, all of this is located in same data center. I did confirm SSRS is working fine, able to access the URL,
db is created and all security setup correctly.
Trying to install the Reporting Point on my CAS.
When I start the installation wizard from the "Configuration Manager console" and select CAS - Reporting Point, I see that the information about the SQL Cluster is populated however my "Reporting Services Server instance" is blank.
I've searched various forums/blogs and all talk about security settings; version for SSRS etc. I did confirm all this is correct.
I've tried following scenario.
Instead of installing the Reporting Services role on my CAS, I selected the SQL Server that had reporting instance installed, and also has the instance for 1 primary site. Following the same screens I know have my SQL Information populated and also
my "REporting Services Server Instance" is populated !!!!!! the installation know continues fine, and when I go to my REport manager website I can see all reports etc..
But!
Checking the data source, it's now configured for my primary site !!!! so I can only see reports/data from that primary site. If I update the datasource to point to my SQL Cluster, I'm able to run reports but every minute it's reverted back as
part of the check done I can see this in the log file srsrp.log. When I go to my Configuration Manager console, I can only see the reports when I'm connected to my primary site, from the CAS all is blank.
Question I have is following
- can you have SQL Cluster configuration for CAS data and separate SSRS instance on different server? I've got feeling during installation of the reporting point, when it's discovering the SQL Instance for CM, it's looking for some link to determine
the reporting instance, and obviously cannot find this.
- Is there anything on the SQL Cluster that needs to be configured so that it know this is the SSRS instance to be used (only guessing)
- in my setup my DBA installed the SSRS part in already existing SQL Instance (used for my primary site), which would explain above behavior, I will ask him to install SSRS on separate instance, but I then have feeling that this will not work, as the
instance will not be populated when I try to install Reporting point.
Any ideas or suggestion to make this setup work

Since no one has answer this post, I recommend opening a support case with CSS as they can work with you to solve this problem.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

Report Services Cluster

Similar Messages

Maybe you are looking for