SCCMentor – Paul Winstanley

Endpoint Management Tips, Fixes and Guides

Reporting Services Point – Server Instance Blank

I’ve helped with this issue a couple of times now so thought it would be ideal to blog.

Basically when running a remote SQL instance, and adding in the Reporting Services Point, the Reporting Services server instance is empty.

ReportingBlank

To resolve the problem ensure that the Reporting Services site role is installed on the SQL server and not the SCCM server.

In Administration workspace choose Site Configuration>Servers and Site System Roles. Right click the SQL server and choose Add Site System Roles. Continue the wizard and add the Reporting Services Point.

So long as the SQL services reporting is installed and configured on the SQL box you should be good to go

Share this:

17 comments.

What if your SCCM server is on one box, SQL is on another and SSRS is on a 3rd?

Install the role on the server hosting the SSRS

In siteserver (SCCM) Under sql server 2012 -> configuration tools Open sqk server configuration manager-> Sql server services -> Run all services an make it automatuc run

Do this with sql server with same above step

I was solve many times with many projects Good luck

I can not see the inventory to sql

Sorry can you clarify what you mean here?

I am looking for a sql servers report on my network but already I can not see

Hi Paul, I have followed your advice and installed the reporting services on to the SQL box, but when I open the Reports folder in the console, it is empty, when I try the URL in Reporting services configurations manager, it too is empty. (Both are empty)

Is this a restart issue or a population issue?

I am well and truly stuck, any advise at this point would be massively appreciated.

Have you configured SSRS at all? Check Configuring Reporting Services on this link https://www.systemcenterdudes.com/install-sccm-2012-reporting-services-point/

Paul, Thanks for getting back to me. Yes I had already configured Reporting services, this is why I reached out. After reading someone elses comment that MS hadn’t seen this issue before, I decided to rebuild back to Server 2008 to see if that fixes the issue, if it does, I will work from there to resolve. If I get a fix for this issue, I’ll post here to help everyone out.

Thanks again

Cheers for that info Paul

My SQL server and reporting services are running on different windows server. I am not able to find the reporting services server instance while adding reporting role on sccm. Please help.

have you installed the reporting services role on the server hosting SSRS?

Sam problem facing plz help me i have installed sccm server and sql server on same server.

Hi, I am having same issue, not able to find SSRS. My SCCM app and SQL Server are on different servers. Trying to add the role on my SQLServer from SCCM console but the SSRS field is empty and the error is same as in snapshot

Does the sccm server have admin rights on the remote SSRS server?

Yes, SCCM computer object is added in Administrators group on SSRS server, and the account using is already member of local administrators group

Hi, I am having same issue as above snapshot. My SCCM is 2203 and SQL Server 2019 & SSRS2019. SCCM and SQL server are on separate server. Trying to install role on SQL Server from SCCM console but SSRS field is empty.

Leave a Reply Cancel reply

' src=

  • Already have a WordPress.com account? Log in now.
  • Follow Following
  • Copy shortlink
  • Report this content
  • View post in Reader
  • Manage subscriptions
  • Collapse this bar

SCCM | Configuration Manager | Intune | Windows Forums

Follow along with the video below to see how to install our site as a web app on your home screen.

Note: This feature currently requires accessing the site using the built-in Safari browser.

PENDING   SCCM Reporting 'empty' blank

  • Thread starter Damon
  • Start date Aug 12, 2020
  • Endpoint Manager
  • Configuration Manager
  • Aug 12, 2020
SMS_EXECUTIVE started SMS_SRS_REPORTING_POINT as thread ID 19852 (0x4D8C). SMS_SRS_REPORTING_POINT 11/08/2020 9:30:49 PM 5352 (0x14E8) Initializing, verbose logging is enabled. SMS_SRS_REPORTING_POINT 11/08/2020 9:31:05 PM 19852 (0x4D8C) This is a SRS Reporting Point Role as SRSRP registry key exists. SMS_SRS_REPORTING_POINT 11/08/2020 9:31:05 PM 19852 (0x4D8C) [DataSource]: Unable to read one of the keys associated with the Reporting Role. Please verify the reporting role is configured correctly SMS_SRS_REPORTING_POINT 11/08/2020 9:31:05 PM 19852 (0x4D8C) [DataSource]: Unable to read one of the keys associated with the Reporting Role. Please verify the reporting role is configured correctly SMS_SRS_REPORTING_POINT 11/08/2020 9:31:05 PM 19852 (0x4D8C) Waiting for change or shutdown for 0 minutes SMS_SRS_REPORTING_POINT 11/08/2020 9:31:05 PM 19852 (0x4D8C) Wait timed out. SMS_SRS_REPORTING_POINT 11/08/2020 9:31:05 PM 19852 (0x4D8C) Click to expand...
<08/11/20 21:30:17> ======== Installing Pre Reqs for Role SMSSRSRP ======== <08/11/20 21:30:17> Found 1 Pre Reqs for Role SMSSRSRP <08/11/20 21:30:17> Pre Req SqlNativeClient found. <08/11/20 21:30:17> SqlNativeClient is already installed (Product Code: {9D93D367-A2CC-4378-BD63-79EF3FE76C78}). But to support TLS1.2, a new version with Product Code: {B9274744-8BAE-4874-8E59-2610919CD419} needs to be manually installed <08/11/20 21:30:17> Pre Req SqlNativeClient is already installed. Skipping it. <08/11/20 21:30:18> ======== Completed Installation of Pre Reqs for Role SMSSRSRP ======== <08/11/20 21:30:18> Installing the SMSSRSRP <08/11/20 21:30:18> Passed OS version check. <08/11/20 21:30:18> .NET Framework 4.0 Full profile is installed. <08/11/20 21:30:18> Clean up old files <08/11/20 21:30:18> No versions of SMSSRSRP are installed. Installing new SMSSRSRP. <08/11/20 21:30:18> Enabling MSI logging. srsrp.msi will log to C:\Program Files\Microsoft Configuration Manager\logs\srsrpMSI.log <08/11/20 21:30:18> Installing C:\Program Files\Microsoft Configuration Manager\bin\x64\srsrp.msi SRSRPINSTALLDIR="C:\Program Files\SMS_SRSRP" SRSRPLANGPACKFLAGS=0 <08/11/20 21:30:28> srsrp.msi exited with return code: 0 <08/11/20 21:30:28> Installation was successful. <08/11/20 21:30:28> CTool::RegisterManagedBinary: run command line: "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\RegAsm.exe" "C:\Program Files\SMS_SRSRP\srsserver.dll" /unregister <08/11/20 21:30:28> CTool::RegisterManagedBinary: Registered C:\Program Files\SMS_SRSRP\srsserver.dll successfully <08/11/20 21:30:28> Unregistered DLL C:\Program Files\SMS_SRSRP\srsserver.dll <08/11/20 21:30:28> CTool::RegisterManagedBinary: run command line: "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\RegAsm.exe" "C:\Program Files\SMS_SRSRP\srsserver.dll" /codebase <08/11/20 21:30:28> CTool::RegisterManagedBinary: Registered C:\Program Files\SMS_SRSRP\srsserver.dll successfully <08/11/20 21:30:28> Registered DLL C:\Program Files\SMS_SRSRP\srsserver.dll <08/11/20 21:30:28> No versions of SMSSRSRP are installed. Installing new SMSSRSRP. <08/11/20 21:30:28> Enabling MSI logging. srsrp.msi will log to C:\Program Files\Microsoft Configuration Manager\logs\srsrpMSI.log <08/11/20 21:30:28> Installing C:\Program Files\Microsoft Configuration Manager\bin\x64\srsrp.msi SRSRPINSTALLDIR="C:\Program Files\SMS_SRSRP" SRSRPLANGPACKFLAGS=0 <08/11/20 21:30:47> srsrp.msi exited with return code: 0 <08/11/20 21:30:47> Installation was successful. <08/11/20 21:30:47> Installation was successful. <08/11/20 21:30:47> ~RoleSetup(). Click to expand...

Garth

Well-Known Member

Unless you save the certificates, your restoring the database is useless. Remove SSRS and start fresh with a new SSRS database.  

  • Aug 13, 2020
  • Thread Starter

Hi Garth, When I installed it, I had to create a new database under the SCCM SQL instance, rather than selecting an existing one. happy to remove it all and start again, but is there anything I should be manually removing as well?  

When I do this, I remove the SCCM reporting point. Remove SSRS Delete the database Install SSRS Install the SCCM reporting point. There might be one step less option but I like this and it ensures that everything is clean.  

  • Aug 19, 2020

Thanks for your help, I removed the role, then the reporting services, deleted the databases and then restarted. I still haven't had any luck. I'm still seeing in the log: [DataSource]: Unable to read one of the keys associated with the Reporting Role. Please verify the reporting role is configured correctly  

Did you confirm that SSRS is setup correctly? What permission did you assign the Site server? Is the remote registry service enabled?  

  • Aug 21, 2020

As far as I'm aware SSRS is setup properly, I actually pulled our old server that previously ran these services out of storage and fired it up, I compared all the settings between it and the current server and everything seems to be the same. The remote registry service is running, and the machine is also part of the local administrators group (if thats what you're referring to for the site server permissions?) I hadn't originally thought of the encryption keys from the old server, so I removed reporting services from SCCM, imported the encryption keys from the old server and reinstalled reporting in SCCM, however I still got that same message. I could be missing something really obvious, so I'll take some screenshots of the configuration of both SSRS and SCCM to see if you can see something that I'm missing.  

here is a blog I wrote on how to setup SSRS. If you did all of these steps it should work.  

  • Aug 24, 2020
SMS_EXECUTIVE started SMS_SRS_REPORTING_POINT as thread ID 16092 (0x3EDC). SMS_SRS_REPORTING_POINT 24/08/2020 2:53:44 PM 1152 (0x0480) Initializing, verbose logging is enabled. SMS_SRS_REPORTING_POINT 24/08/2020 2:53:59 PM 16092 (0x3EDC) This is a SRS Reporting Point Role as SRSRP registry key exists. SMS_SRS_REPORTING_POINT 24/08/2020 2:53:59 PM 16092 (0x3EDC) [DataSource]: Unable to read one of the keys associated with the Reporting Role. Please verify the reporting role is configured correctly SMS_SRS_REPORTING_POINT 24/08/2020 2:53:59 PM 16092 (0x3EDC) [DataSource]: Unable to read one of the keys associated with the Reporting Role. Please verify the reporting role is configured correctly SMS_SRS_REPORTING_POINT 24/08/2020 2:53:59 PM 16092 (0x3EDC) Waiting for change or shutdown for 0 minutes SMS_SRS_REPORTING_POINT 24/08/2020 2:53:59 PM 16092 (0x3EDC) Wait timed out. SMS_SRS_REPORTING_POINT 24/08/2020 2:53:59 PM 16092 (0x3EDC) Checking reporting server health. SMS_SRS_REPORTING_POINT 24/08/2020 2:53:59 PM 16092 (0x3EDC) Verifing registry change notification is configured. SMS_SRS_REPORTING_POINT 24/08/2020 2:53:59 PM 16092 (0x3EDC) Waiting for change or shutdown for 1 minutes SMS_SRS_REPORTING_POINT 24/08/2020 2:53:59 PM 16092 (0x3EDC) Wait timed out. SMS_SRS_REPORTING_POINT 24/08/2020 2:54:59 PM 16092 (0x3EDC) Checking reporting server health. SMS_SRS_REPORTING_POINT 24/08/2020 2:54:59 PM 16092 (0x3EDC) Verifing registry change notification is configured. SMS_SRS_REPORTING_POINT 24/08/2020 2:54:59 PM 16092 (0x3EDC) Waiting for change or shutdown for 1 minutes SMS_SRS_REPORTING_POINT 24/08/2020 2:54:59 PM 16092 (0x3EDC) Wait timed out. SMS_SRS_REPORTING_POINT 24/08/2020 2:55:59 PM 16092 (0x3EDC) Click to expand...
<08/24/20 14:53:20> ==================================================================== <08/24/20 14:53:20> SMSSRSRP Setup Started.... <08/24/20 14:53:20> Parameters: C:\Program Files\Microsoft Configuration Manager\bin\x64\rolesetup.exe /install /siteserver ur-server SMSSRSRP 0 <08/24/20 14:53:20> Installing Pre Reqs for SMSSRSRP <08/24/20 14:53:20> ======== Installing Pre Reqs for Role SMSSRSRP ======== <08/24/20 14:53:20> Found 1 Pre Reqs for Role SMSSRSRP <08/24/20 14:53:20> Pre Req SqlNativeClient found. <08/24/20 14:53:20> SqlNativeClient is already installed (Product Code: {9D93D367-A2CC-4378-BD63-79EF3FE76C78}). But to support TLS1.2, a new version with Product Code: {B9274744-8BAE-4874-8E59-2610919CD419} needs to be manually installed <08/24/20 14:53:20> Pre Req SqlNativeClient is already installed. Skipping it. <08/24/20 14:53:20> ======== Completed Installation of Pre Reqs for Role SMSSRSRP ======== <08/24/20 14:53:20> Installing the SMSSRSRP <08/24/20 14:53:20> Passed OS version check. <08/24/20 14:53:20> .NET Framework 4.0 Full profile is installed. <08/24/20 14:53:20> Clean up old files <08/24/20 14:53:21> No versions of SMSSRSRP are installed. Installing new SMSSRSRP. <08/24/20 14:53:21> Enabling MSI logging. srsrp.msi will log to C:\Program Files\Microsoft Configuration Manager\logs\srsrpMSI.log <08/24/20 14:53:21> Installing C:\Program Files\Microsoft Configuration Manager\bin\x64\srsrp.msi SRSRPINSTALLDIR="C:\Program Files\SMS_SRSRP" SRSRPLANGPACKFLAGS=0 <08/24/20 14:53:28> srsrp.msi exited with return code: 0 <08/24/20 14:53:28> Installation was successful. <08/24/20 14:53:28> CTool::RegisterManagedBinary: run command line: "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\RegAsm.exe" "C:\Program Files\SMS_SRSRP\srsserver.dll" /unregister <08/24/20 14:53:28> CTool::RegisterManagedBinary: Registered C:\Program Files\SMS_SRSRP\srsserver.dll successfully <08/24/20 14:53:28> Unregistered DLL C:\Program Files\SMS_SRSRP\srsserver.dll <08/24/20 14:53:28> CTool::RegisterManagedBinary: run command line: "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\RegAsm.exe" "C:\Program Files\SMS_SRSRP\srsserver.dll" /codebase <08/24/20 14:53:29> CTool::RegisterManagedBinary: Registered C:\Program Files\SMS_SRSRP\srsserver.dll successfully <08/24/20 14:53:29> Registered DLL C:\Program Files\SMS_SRSRP\srsserver.dll <08/24/20 14:53:29> No versions of SMSSRSRP are installed. Installing new SMSSRSRP. <08/24/20 14:53:29> Enabling MSI logging. srsrp.msi will log to C:\Program Files\Microsoft Configuration Manager\logs\srsrpMSI.log <08/24/20 14:53:29> Installing C:\Program Files\Microsoft Configuration Manager\bin\x64\srsrp.msi SRSRPINSTALLDIR="C:\Program Files\SMS_SRSRP" SRSRPLANGPACKFLAGS=0 <08/24/20 14:53:41> srsrp.msi exited with return code: 0 <08/24/20 14:53:41> Installation was successful. <08/24/20 14:53:41> Installation was successful. <08/24/20 14:53:41> ~RoleSetup(). Click to expand...

reporting services server instance blank sccm

  • Aug 31, 2020

Alex_251

  • Sep 24, 2020

hello, have you solved your problem then?  

No, it hasn't been resolved yet  

Damon said: No, it hasn't been resolved yet Click to expand...

jschambaugh

  • Apr 16, 2021

I am having the same problem as this after migrating over to a new VM. I was about to post a new thread but found this is exactly the same issue. Was this ever resolved?  

Did you remove and add the reporting point back? did you review the srsp.log on your SSRS server?  

Garth said: Did you remove and add the reporting point back? did you review the srsp.log on your SSRS server? Click to expand...
Initializing, verbose logging is enabled. SMS_SRS_REPORTING_POINT 4/15/2021 2:12:18 PM 2604 (0x0A2C) This is a SRS Reporting Point Role as SRSRP registry key exists. SMS_SRS_REPORTING_POINT 4/15/2021 2:12:18 PM 2604 (0x0A2C) [DataSource]: Unable to read one of the keys associated with the Reporting Role. Please verify the reporting role is configured correctly SMS_SRS_REPORTING_POINT 4/15/2021 2:12:18 PM 2604 (0x0A2C) [DataSource]: Unable to read one of the keys associated with the Reporting Role. Please verify the reporting role is configured correctly SMS_SRS_REPORTING_POINT 4/15/2021 2:12:18 PM 2604 (0x0A2C) Waiting for change or shutdown for 0 minutes SMS_SRS_REPORTING_POINT 4/15/2021 2:12:18 PM 2604 (0x0A2C) Wait timed out. SMS_SRS_REPORTING_POINT 4/15/2021 2:12:18 PM 2604 (0x0A2C) Checking reporting server health. SMS_SRS_REPORTING_POINT 4/15/2021 2:12:18 PM 2604 (0x0A2C) Verifing registry change notification is configured. SMS_SRS_REPORTING_POINT 4/15/2021 2:12:18 PM 2604 (0x0A2C) Waiting for change or shutdown for 1 minutes SMS_SRS_REPORTING_POINT 4/15/2021 2:12:18 PM 2604 (0x0A2C) Wait timed out. SMS_SRS_REPORTING_POINT 4/15/2021 2:13:18 PM 2604 (0x0A2C) Checking reporting server health. SMS_SRS_REPORTING_POINT 4/15/2021 2:13:18 PM 2604 (0x0A2C) Verifing registry change notification is configured. SMS_SRS_REPORTING_POINT 4/15/2021 2:13:18 PM 2604 (0x0A2C) Waiting for change or shutdown for 1 minutes SMS_SRS_REPORTING_POINT 4/15/2021 2:13:18 PM 2604 (0x0A2C) Wait timed out. SMS_SRS_REPORTING_POINT 4/15/2021 2:14:18 PM 2604 (0x0A2C) Click to expand...

Well looks like I found my issue. It was 100% user error. After migration I failed to re-enter the password in Administration - Security - Accounts within SCCM.  

Latest posts

  • Latest: Ravi Kumar
  • Today at 10:19 PM
  • Latest: gebodido
  • Today at 9:16 PM
  • Latest: sangie15
  • Today at 9:12 PM

Garth

  • Latest: Garth
  • Today at 9:04 PM
  • Latest: brich4750
  • Today at 8:16 PM

Forum statistics

  • This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register. By continuing to use this site, you are consenting to our use of cookies. Accept Learn more…

Nick Moseley's Day-to-Day Technical Journey

Reporting Services Site Role Setup: Instance Blank/Empty

reporting services server instance blank sccm

While it is common “knowledge” that the reporting services database needs to be created first, an oft-overlooked step is to use the Reporting Services Configuration Manager to create the virtual directories for IIS.  And it is these steps which need to be completed to get you on your way.

  • Open Reporting Services Configuration Manager
  • Connect to the server/instance

reporting services server instance blank sccm

  • Click on Report Manager URL – again, make a change to the name and put back to just Reports – and click Apply to generate the new virtual directories.
  • Close configuration manager
  • Return to the CM12 site role setup program, click “Verify” for the database connection, and voila the instance is now populated correctly!

Share this:

4 thoughts on “ reporting services site role setup: instance blank/empty ”.

This worked like a charm for me! I was able to complete the site system roles wizard for reporting. However, when I go into Reporting in SCCM 2012, and click on Reports, my list of reports isn’t popping up. It’s been about 15 minutes and I’m using my test lab. I guess I’ll wait and see. Thanks.

Finally, I got it working!!! Special Thanks to Paul Winstanley (my Linkedin SCCM friend!). Since my SCCM 2012 R2 SQL box is on separate box with my SCCM 2012 R2. I have to do this per Paul. You’re genius! From Paul Winstanley comment: Reza, You should already have the SQL server in your SCCM console as a Site System in Servers and Site System Roles. Right click the SQL server and choose Add Site System Roles. Continue the wizard. So long as the SQL services reporting is installed and configured on the SQL box you should be good to go

I did the same thing as mentioned. But it doesn’t work. I have sccm CB 1702 and remote SQL server. Any suggestions please

Thanks alot, These changes fixed my problem.

Leave a Reply Cancel reply

Create a free website or blog at WordPress.com.

' src=

  • Already have a WordPress.com account? Log in now.
  • Follow Following
  • Copy shortlink
  • Report this content
  • View post in Reader
  • Manage subscriptions
  • Collapse this bar
  • Configuration Manager 2012

www.windows-noob.com

  • Remember me Not recommended on shared computers

Forgot your password?

reporting services server instance blank sccm

SCCM 2012 SP1 Reporting Services Server Instance is Blank

By pnyce24 , April 29, 2013 in Configuration Manager 2012

  • sccm 2012 SP1
  • reporting server
  • reporting instance

reporting services server instance blank sccm

  • Reply to this topic
  • Start new topic

Recommended Posts

  • Report post

I'm tryin to setup the report services point site system role on my SCCM 2012 SP1 primary site. However when I get the configuring the settings the "Reporting Services server instance" is blank, and I'm not able enter anything inside that box. I verified my reporting services configuration manager that report server is setup properly. I see other threads posting similar issues but many of them has to do with SQL 2008.

Current SCCM 2012 SP1 configuration is below....

Primary Site Server: SCCM 2012 SP1

SQL Server(separate remote server) SQL Server 2012 CU2

***SMSAdmin Account has local admin rights on the sql server***

Share this post

Link to post, share on other sites.

Check to see if you have to install any service packs for the SQL instance. I had the same problem and I had to reinstall the SQL service pack onto the Database Instance. This is a protection feature of Microsoft even if you upgrade the whole server you will need to re-install the service pack on the actual database instance for Reporting Services possibly.

Did you install a cumulative update or upgrade to SP1? I'm currently using SQL Server 2012 CU2.

svg

This is due to the fact that reporting services has not been properly configured. The answer to this solution is actually very simple. I have encountered the same issue and could solve it following this procedure http://myitforum.com/myitforumwp/2012/10/10/reporting-services-site-role-setup-instance-blankempty/

:)

Running into a similar problem when trying to add a Reporting services point. SCCM 2012 SP1, SQL 2012 CU7 (have also tried CU2-CU6). One physical server used as a stand-alone Primary site. Report instance is blank - here is what I've tried.

SRS info - running as local system

IP address - All assigned

database running with domain admin creds

* Uninstalling and re installing SRS 2012

* Installing as a separate instance

* Uninstalling and re installing SQL 2012

* HKLM>software>microsoft>microsoft sql server>instance names>rs>shows current reportingservices instance

* Tried renaming SRS virtual directory and renaming them back

GarthMJ

Make sure that you re-install CU6 or better, after you install SSRS.

Thanks for the reply GarthMJ. When I run the CU7 install SQLServer2012-KB282347-x64 the install options are grayed out. The other CU7 installs ran fine, DACFramework.msi and SapBl.msi.

If it is greyed out it mean that it doesn't apply to the server. What does CU7 log say as to why it didn't apply?

UPDATE: A Microsoft case was opened for this issue after trying many different avenues found online (see last post on this thread). After having Microsoft SCCM and SQL teams review settings, configs and installations, current environment and system logs. They were unable to resolve my issue, they say they've never experienced this issue before (I'm skeptical). Because this was for PROD time was critical so it was faster for me to re-format everything and rebuild. Instead of using the 2012 OS and SQL, I took a step back and used 2008 R2 SP1 OS and 2008 R2 SP2 CU6 - working like a charm now.

This is due to the fact that reporting services has not been properly configured. The answer to this solution is actually very simple. I have encountered the same issue and could solve it following this procedure http://myitforum.com/myitforumwp/2012/10/10/reporting-services-site-role-setup-instance-blankempty/   Have fun !

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest

×   Pasted as rich text.    Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.    Display as a link instead

×   Your previous content has been restored.    Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Submit Reply
  • Existing user? Sign In
  • Online Users
  • Leaderboard
  • All Activity
  • Create New...
  • Privacy Policy

{Quick Fix} SSRS instance showing blank while installing reporting extensions for V9.0 on-premise

  • by Debajit Dutta (Former 6x Business Solutions MVP, MCT)
  • August 14, 2019 July 6, 2021

It’s been couple of months since I have written a blog. One of those years where health has gone south for me and I am gradually limping in back into my stride.

Ironically, as I am making my way back, I started with Dynamics V9.0 on-premise project for one customer as well and it’s been more than couple of years since I worked on an on-premise project. And it’s been a quite a learning so far. My next few blogs would be on my experiences with setting up Dynamics on-premise latest version starting with the easiest one.

So coming to the topic here. You may be thinking – why this post? To be honest, there a quite a few blogs which discuss on this. However each represents a specific solution. However this problem can arise for various reasons and fix suggested by one may not work for another. In this post I collate all the possible causes and their remediation. Feel free to write to me in case I miss something. I would love extra knowledge and add them to my post here.

Server : Windows Server 2016 datacenter

SQL server: SQL Server 2017

This issue is not specific to V9.0 and users have faced this with earlier versions of CRM on-premise installations.

Check 1: Run reporting extensions set-up (SetupSrsDataConnector.exe) from box where reporting services is installed.

This is the easiest fix. Make sure you are running the set-up from the machines where reporting services is installed.

If you are running from reporting services box only but still the issue persist, lets go for Check 2.

Check 2: Service account in Report Server configuration manager must be part of PrivReportingGroup

To verify this, open Report Server configuration manager.

image

Navigate to “Service Account” on left navigation pane and verify your account. Here I am using a service account “xrmforyouadmin”. We need to verify if “xrmforyouadmin” belongs to PrivReportingGroup in Active Directory.

image

This step might require your domain admins help. Active directory is not something you will have access to as CRM consultant. However I am providing screenshots below to help you understand better so that you can guide your active directory admin in the right direction.

Open “Active directory users and computers” and then click on Domain controllers. You may find multiple PrivReportingGroups in there. To find the right one for your CRM Organization, you can follow the below link.

Get PrivUserGroup specific to your CRM Organization in Microsoft Dynamics CRM

image

Open the “PrivReportingGroup” specific to your CRM organization and add the service account to the group.

image

Now go back and run SetupSrsDataConnector.exe. Check to see if the issue is fixed. Not fixed? Lets go for the next checklist.

Check 3: Make registry entries in SQL Server box.

The first thing to note here is all the below changes should be made in SQL server box. You would need administrative permissions on the machine to perform these operations. Please follow the below steps:

  • Open Registry Editor (regedit.exe)
  • Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\RS
  • Check for the Key MSSQLSERVER. If absent, create a new key as shown in the below screenshot. Key Name – MSSQLSERVER, Key value – SSRS
  • We  are done with this entry. We need to create one more entry. But for that we would need the SQL server version number installed. But how do I get it? Well, there are many ways. I am showing one of them. Open SQL server management studio and connect to database instance. Then type the below query.

image

As you can see from above screenshot, there is a version number in the result. Copy the same. In my case it is  – 14.0.2027.2

Now navigate to – “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\SSRS\Setup”

image

Look for the entry with the name – “Version”. If not found create a new string value with name – “Version” and value as version of SQL server obtained from earlier step.

All set and done. Now restart SQL server and reporting services and try to install reporting extensions. The installation should successfully complete now

In case the issue is not fixed, the last option is to try install reporting extensions via configuraiton file by adding the instance name into the configuraiton.xml as detailed in below Microsoft Documentation link.

http://technet.microsoft.com/en-us/library/dd979397.aspx

Hope this helped!

Debajit Dutta Business Solutions MVP

1 thought on “{Quick Fix} SSRS instance showing blank while installing reporting extensions for V9.0 on-premise”

' src=

Nice Blog Debajit, Thanks for putting this all together. Wish you a good health and quick recovery.

Comments are closed.

Prajwal Desai

How to Install SCCM Reporting Services Point | ConfigMgr SSRS

This article is a step-by-step guide to install SCCM reporting services point role. I will show you how to install and configure the ConfigMgr SSRS reporting services point and enable reports.

To access reports in Configuration Manager, you need a reporting services point. When you run the reports in ConfigMgr, the Reporting Services connects to the Configuration Manager site database to retrieve data that is returned when you run reports.

If you are thinking of how do I enable reporting in SCCM, it involves a series of steps before you can use the reports in Configuration Manager. This guide shows every step that you require to install and configure reports in SCCM.

Like  SCCM log files , there are many reports that come preinstalled with ConfigMgr. Configuration Manager supplies 470+ built-in reports, covering many of the reporting tasks that you might want to do. You can also use the SQL statements in these reports to help you write your own reports.

If you are looking to repair SSRS or reinstall the reporting services point, refer to the following guide on SCCM reinstall reporting services point .

What is Reporting in SCCM?

Reporting in Microsoft Endpoint Configuration Manager provides a set of tools and resources that help you use the advanced reporting capabilities of SQL Server Reporting Services. SCCM Reporting helps you gather, organize, and present information about users, hardware and software inventory, software updates, applications, site status, and other Configuration Manager operations in your organization.

Reporting provides you with a number of predefined reports that you can use as is or modify to meet your needs, as well as the ability to create custom reports. Configuration Manager includes over 450 report definitions in over 50 report folders, which are copied to the root report folder in SQL Server Reporting Services during the reporting services point installation process.

The reports are organized in subfolders based on the report category and displayed in the Configuration Manager console. Reports are not propagated up or down the Configuration Manager hierarchy; they run only against the database of the site in which they are created.

You can run the reports in Configuration Manager console by using Report Viewer , or you can run reports from a browser by using Report Manager. To run reports in the Configuration Manager console, you must have the Read right for the Site permission and the permissions configured for specific objects. The user account will need Modify right for the Site permission to modify the reports.

What is Reporting Services Point in SCCM?

SCCM’s reporting services point connects with SSRS in order to copy SCCM reports to a defined report folder. SCCM will establish the general and security settings for the reporting service. When you run reports, Reporting Services connects to the SCCM site DB to retrieve the returned data.

A Reporting Services Point role can be installed on a central administration site, primary sites, and on multiple site systems at a site and at other sites in the hierarchy. The reporting services point is not supported on Configuration Manager secondary sites .

By definition, the reporting services point is a site system role that is installed on a server that is running Microsoft SQL Server Reporting Services. The reporting services point performs the following tasks:

  • Reporting Services receives a copy of the Configuration Manager report definitions.
  • Report folders are created depending on report categories.
  • Configures the security policy for report folders and reports. These policies are based on Configuration Manager administrative users’ role-based rights. If you alter the security policy, the reporting services point connects to Reporting Services every 10 minutes to reapply it.

Prerequisites for Reporting Services Point

When you plan to install the reporting services point role in SCCM, the following prerequisites are required.

  • .NET Framework for the Reporting Services Point. Use .NET Framework 4.8 and above.
  • SQL Server Reporting Services for RSP
  • SQL Server Native Client for the Reporting Services Point
  • SQL Server 2017, SQL Server 2022 or later.

SQL Server Installation for Configuration Manager

One of the prerequisites for installing the Configuration Manager is SQL Server. The Configuration Manager stores its entire data in a dedicated database on SQL server. Each Microsoft Endpoint Configuration Manager site requires a  supported SQL Server version  and configuration to host the site database. Hence, you must install the supported SQL Server version for Configuration Manager .

The latest versions of Configuration Manager current branch support SQL Server 2017, SQL Server 2019 and later. You can install any of these versions of SQL Server for Configuration Manager. This guide assumes that you have already installed SQL Server for ConfigMgr. If you are planning to install the SQL Server for SCCM, refer to the following guides:

  • Install SQL Server 2017 for Configuration Manager
  • Install SQL Server 2019 for SCCM | ConfigMgr
  • Upgrade SQL Server 2014 to SQL Server 2017

Create SSRS Connection Account

When you install SCCM reporting services point, you use a dedicated account which is nothing but the SSRS connection account. When you create this account in AD, provide it NO further domain access. Please do not make it a domain administrator. All it requires are regular, low rights. Make it a local administrator on SQL Server or the SSRS server at all costs. SCCM handles granting the rights required by SQL Server and SSRS.

Download SQL Server Reporting Services for SCCM

You can download the latest version of SQL Server Reporting Services from the Microsoft Download center . Older versions of SQL Server would install the SQL server and the reporting services. However, with SQL Server version 2017 and later, you must download the SSRS installer separately and install it.

Download SQL Server Reporting Services for SCCM

Install SQL Server Reporting Services (SSRS)

SQL Server Reporting Services is a server-based reporting platform that provides comprehensive reporting functionality. Reporting Services offers the following features:

  • Paginated reports optimized for document generation and printing.
  • Mobile reports optimized for mobile devices, with responsive layout that adapts to different devices and the different ways you hold them.
  • A modern web portal you can view in any modern web browser.

To install SSRS for SCCM, you will require the .NET Framework 4.7 or later and SQL Server Database Engine (2012 SP4 or later) , to store the report server database.

In this example, I will be installing SQL Server 2019 Reporting Services for Configuration Manager. Run the SQLServerReportingServices.msi installer to start the installation.

Install SQL Server Reporting Services (SSRS)

On the Choose an edition to install scree, there are two options:

  • Choose a free edition – Evaluation (180 days), Developer, Express.
  • Enter the product key.

Select the second option and enter the product key for SQL Server Reporting Services.

Tip : When you install the SQL server for Configuration Manager, the product key is displayed on one of the initial setup screens. You must use the same key while installing the SSRS.

Click Next .

Enter SSRS Product Key

Click I accept the license terms and then click Next .

Accept License Terms for SSRS

As mentioned earlier, you’ll need an instance of SQL Server Database engine to store the report server database. This option was enabled during the SQL Server installation. Select Install Reporting Services only and click Next .

Install SQL Server Reporting Services

I am going to leave the install location to default, click Install . This begins the installation of Reporting Services. In the next section, we will look at the steps to configure the reporting services.

Install SQL Server Reporting Services

To launch the SQL Server Reporting Services, click Start and type “ Report Server “. From the list of search results, click “ Report Server Configuration Manager.”

Configure Reporting Server Configuration Manager

In this step, we will configure the reporting services for Configuration Manager. In the completion window of SQL Server 2019 Reporting Services, select Configure manually and customize settings and click Configure Report Server .

Configure Reporting Services for SCCM

In the Report Server Configuration Manager window, select the report server instance as SSRS and click Connect .

Configure Report Server Instance

Select the Database tab and here we see the current report server database is empty. This means there is a report server database that has been created before. To create a new report server database for SCCM, select Change Database .

Create Report Server Database

On the Action window, select Create a new report server database . Click Next .

Create Report Server Database for SCCM

Test the credentials that you use to connect to the database server. If you see “ Test connection succeeded “, it means the credentials are valid, and you can proceed.

Create Report Server Database for SCCM

On the Database page of the Report Server Database configuration wizard, choose the Database Name , which is by default set as ReportServer . Select the database language, for example, English (United States) . The report server mode is set to native, which works fine for Configuration Manager. Click Next .

Report Server Database Name

Specify the credentials of an existing account that the report server will use to connect to the report server database. Permission to access the report server database will be automatically granted to the account you specify. Select the Authentication type as Windows Credentials and specify the account name and password. Click Next .

Report Server Database Credentials

This begins the report server database creation now, and on the Progress and Finish page, ensure all the steps show as Success . Click Finish to close the report server database configuration wizard.

Report Server Database Configuration

On the Database tab, we see the tasks have been completed successfully. If you don’t see them, you can click on the “ Apply ” button.

Report Server Database Created

Configure the Web Service URL and Web Portal URL

In this step, we will configure a URL that is used to access the Report Server. You can define multiple URLs for a single report server instance and even specify additional parameters on the URL.

In the Report Server Configuration Manager tool, select the Web Server URL tab, and at the bottom, click the Apply button. This will configure the web service URL for reports.

Configure Web Service URL and Web Portal URL

Similarly, click the Web portal URL and click Apply . This will configure a dedicated URL to access the web portal. Click the Exit button to close the report server configuration manager wizard.

Configure Web Service URL and Web Portal URL

On the  Web Service URL page , click the  URL  in  Report Service Web Service URLs  to test the connection to the report folder. The Windows Security dialog box might open and prompt you for security credentials. By default, your user account is displayed. Enter your password and click OK . Verify that the webpage opens successfully. Close the browser window.

At this point, no Configuration Manager reports are visible because we are yet to install SCCM reporting services point role. Once you install the reporting services point role, the reports will be visible in Configuration Manager console and web URL.

SCCM Reports Web URL

Install SCCM Reporting Services Point Role | ConfigMgr

Follow the below steps to install a new reporting services point role using SCCM console:

  • Launch the SCCM console.
  • Click  Administration  >  Site Configuration . Right click  Servers and Site System Roles .
  • Right-click SQL Server on which you plan to install reporting services point role and select Add Site System Roles .

Install SCCM Reporting Services Point Role | ConfigMgr

On the General window of Add Site System Roles wizard , you have two options for specifying the site system installation account.

  • Use the site servers computer account to install this site system : Select this option to install the site system if both the site server and site system servers are in the same domain. Furthermore, the site server account should be added to the local administrators group on the remote site system server.
  • Use another account for installing this site system : Use this option if the site server and site system servers are in a different domain and there is no two-way trust.

Typically, the first option is preferred in most cases while deploying the reporting services point role in an organization. Verify the Active Directory Forest and Active Directory Domain names and click Next .

Install SCCM Reporting Services Point Role | ConfigMgr

If your organization uses Internet Proxy server, specify it on the Proxy page otherwise click Next .

How To Install SCCM Reporting Services Point Snap21

On the System Role Selection page, from the list of roles, select Reporting Services Point and click Next .

Select Reporting Services Point Role

On the Reporting Services point page, you configure the settings for Reporting Services. This step is critical because the majority of errors such as reporting services server instance blank, is observed here.

If you have installed and configured the reporting services correctly and if the report server database is successfully created, this step should be easy for you. Ideally, the Reporting Services server instance should be automatically populated to SSRS. If the reporting services server instance is blank, you might need to verify the account permissions and perform additional troubleshooting steps .

In the below example, we see the Site Database server name, Database name, Folder Name, and Reporting services server instance are automatically populated.

Specify the credentials that SQL Reporting Services will use when connecting to the Configuration Manager site database and click on Verify . The pop-up window “ Successfully Verified ” confirms the reporting services point account permissions are correct. Click Next .

ConfigMgr SSRS Reporting Services Point Settings

Review the reporting services point role configuration on Summary page and click Next . On the Completion window, click Close . This completes the reporting services point sccm installation steps.

Install ConfigMgr SSRS Reporting Services Point

SCCM Reporting Services Point Log Files

When you install a new reporting services point for SCCM, you can use the following log files to troubleshoot the SSRS installation errors. The log files are located in C:\Program Files\Microsoft Configuration Manager\Logs .

The following table lists the Configuration Manager log files that contain information related to reporting services point in SCCM.

Take a look at the full list of all the important Configuration Manager log files and their locations .

Verify Reporting Services Point Role Installation

To verify that the Reporting Services point role has been installed, launch the SCCM console, click on Monitoring , expand System Sta tus , select Component Status, and look for SMS_SRS_REPORTING_POINT .

From the below screenshot, we see the SMS_SRS_REPORTING_POINT component is online. The green icon indicates the reporting point is healthy and there are no errors.

Verify Reporting Services Point Role Installation

Let’s review the log file named srsrp.log and find out . The log file srsrp.log is located on the site server in the following path: C:\Program Files\Microsoft Configuration Manager\Logs .

The below two lines from the srsrp.log file confirm the successful installation of ConfigMgr SSRS reporting services point.

srsrpMSI.log ConfigMgr Reporting Services Point

In the srsrp.log file, we see the Configuration Manager reports are deployed successfully. Each of these reports are created in a separate folder. Learn how to add SCCM Reports as favorites .

srsrp.log ConfigMgr Reports Deployed Successfully

In the srsrpsetup.log , we see the ConfigMgr SSRS role installation was successful.

srsrpsetup.log Reporting Services Point

Please let us know if you found this article to be useful in the comments section below. Gratitude for reading!

Avatar photo

Prajwal Desai is a Microsoft MVP in Intune and SCCM. He writes articles on SCCM, Intune, Windows 365, Azure, Windows Server, Windows 11, WordPress and other topics, with the goal of providing people with useful information.

Good afternoon, is there a way to reporting services on a separate server to that of the Config Manager DB?

Thanks for the post, a nice walkthrough.

Hi Prajwal,

I installed report services on my sccm server, and it works as usual except that the report account start to register Audit Failure log (4625) ASAP I added the service to SCCM, and every time i open SCCM console. I’m using WS2022, SQL 2019, SSRS 2019. I have few environment which has the same configuration, and there are no problem at all. Do you have any idea?

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Save my name, email, and website in this browser for the next time I comment.

subscribe to newsletter

Get Access to latest articles on configmgr, intune, windows 365, Azure and much more.

Network Steve

Technology Tips and News

I have installed SCCM 2012 With remote SQL database server successfully, at the time of Reporting service point role installation, its verified the SCCm database successfully but SQL server service instance is blank, what would be the reason....

Below my SCCM architecture:

1. Created one Database in Remote server SQL server is in failover cluster active passive mode

2. Configured Reporting services in active mode.

3. at the time of reporting point role installed failover cluster database name given and its successfully verified with SCCM_123 database.

4. on the instance name showing blank.

Please help me if anyone facing this type of problem.

Thanks in advance.

What version of SQL Server Reporting Services?

Note that SSRS is not a cluster aware application so installing it on a cluster node is not a good practice because SSRS cannot failover.

Have you verified that SSRS is accessible by going to http://hostname/reports ?

Final note is that when installing the reporting point, you are not specifying the SQL server instance, you are specifying the SSRS instance -- these are two different things.

Is the site server's computer account a local admin on the system where SSRS is hosted? Remeber that because SSRS is not a cluster aware application, you cannot specify the name of the cluster.

It is not totally intuitive when installing the Reporting Point role with a cluster.  When installing a Failover Cluster, SSRS can only get put on one node or on its own box, as it uses NLB for scale-out not FoC.  SSRS is also not configured by default if you use it with a clustered SQL instance, so you have to open SSRS Configuration Tool and make sure the ReportServerDB is created, and that the URLs can be browsed.  Once that is done, then try adding it in CfgMgr:

In CfgMgr, In the Administration workspace, expand Site Configuration , and then click Servers and Site System Roles .

Select the node that has SSRS installed on it (not the Failover Cluster virtual computer account).  If SSRS is on its own box, first you have to go to New site system and add the SSRS box .

Then, on the Home tab, in the Server group, click Add Site System Role . The Add Site System Roles Wizard opens.  Choose Reporting Point, and after verifying the connection to the CfgMgr DB, the instance name should populate.

http://technet.microsoft.com/en-us/library/gg712698#BKMK_InstallReportingServicesPoint

http://social.technet.microsoft.com/Forums/en-HK/configmanagerdeployment/thread/390a6ea8-8a24-47d0-b6ad-2e1063bbc72d

Hello! Should I install Reporting Services point on site server or Database server?

I was wondering if someone could help me with the same issue. My Reporting Services server instance remains blank when I am trying to install the Rpoerting Services role and I don't know how to over come this.

My situation is:

Remote SQL Server

Reporting services is running in Native Mode

Not sure what I'm missing or how I can troubleshoot?

OK so after reading this I now think the issue may be Firewall. Can anyone confirm that port 135 needs to be open between site server and SQL server when adding the Reporting Services Role?

  • Proposed as answer by huw shields Thursday, September 20, 2012 1:26 PM

I am having the same issue in this config as well.

Here are some notes I made>  SRS is up and configured.  If I process URL HTTP://SRSServer:80/Reports I get to the website, however  if I try to process URL HTTP://SRSServer.mydomain.com:80/Reports  I get prompted for username and password.  If I enter appropriate user credentials, I do get into SRS.

Problem i beleive is that when you configure a new Site system in SCCM 2012, and you enter the server name, it automatically enters it as a FQDN.

I confirmed that I have SPN's defined for the service account that is running MSSQL Service.  Same account is running SRS

Within IE, add your server to the list of Trusted Sites, then you will not get prompted for a password.

I know this is a little old but I had the same issue, this is what I did to fix the issue.

I did what Jason Sandys requested by trying to get to the URL of http://hostname/reports, once I was able to do that I changed the name of the site by going into site settings from the default name to something that matched my site.  Then I started the add role wizard again and on the first page I checked the box next to 'Require the site server to initiate connections to this site system'  Once I did that I was able to choose my reporting service instance.

Hope this helps

http://www.microtom.net/microsoft-system-center/software-distribution/sccm-2012-reporting-services-do-not-install

I faced issue in install of SCCM reporting then i used  mofcomp.exe to register the SQL MOF Files as follows:

Open an elevated command prompt and type

For SQL Server 2008 R2

mofcomp.exe "C:\Program Files (x86)\Microsoft SQL Server\100\Shared\sqlmgmproviderxpsp2up.mof"

wait for 1 hr max... and it fixed

I know this is an OLD post but I just wanted to share my experience on how I was able to resolve this issue in my Test Environment. to help others who may be in the same situation. 

I am a relatively new to SCCM and SQL and Believe I didnt setup " Reporting Services Configuration Manager ".

So, here's how I fixed it.

Start-->Search and launch "Reporting Services Configuration Manager"--> On the left menu click Web Service URL

-->Virtual Directory = ReportServer

--> IP Address = All Assigned

--> TCP Port = 80

--> SSL Certificate = ConfigMgr SQL Server Identification Certificate

--> SSL Port = 443

--> Apply (Wait for a few mins while the URL is reserved)

Then go back into SCCM and add the reporting Role. Hope I was able to help someone with these steps.

PS: I also read somewhere that even if the reporting is already configured, SCCM 2012 doesnt populate the Reporting Services Server Instance. In this case, a few people were able to resolve the issue by making a fake change in Reporting Services Configuration Manager and reapplying the changes.

This topic is archived. No further replies will be accepted.

Chad's Tech

Enterprise Systems Management… ConfigMgr, Intune, PowerShell, and cookies

ConfigMgr Reporting Services Point with complex SQL

In a new ConfigMgr 2012 R2 SP1 environment the Reporting Services point was proving a bit challenging to install.  After setting all of the required permission it was finally happy.

Required Permissions

On the SQL Server Reporting Services server, an account (in this case a domain user “functional” or “service” account) needed the following:

  • Membership in the server’s local Administrators group
  • SSRS Site Settings -> System Administrator, System User
  • SSRS Folder Settings on the root folder -> Browser, Content Manager, My Reports, Publisher, Report Builder

Scenario Details

This ConfigMgr environment has a complex configuration with 3 different SQL servers in play.

  • Server1: ConfigMgr Primary Site server
  • Server2: server running SQL Server Database Engine role and configured as the ConfigMgr Site Database server
  • Server3: server running SQL Server Reporting Services role
  • Server4: server running SQL Server Database Engine role with only the ReportServer database

With Server1 (ConfigMgr) and Server2 (SQL DB) configured and most functionality working (software deployment, software update deployment, OS deployment, inventory, etc.) it was time to install Reporting Services point.  We created a new ConfigMgr Site Server for Server3 using a domain user account.  However, when attempting to install the Reporting Services point the following error was encountered:

image

  • Unable to locate any configured SRS instances on the server.  Verify SRS is installed, accessible, and correctly configured.
  • The “Reporting Services server instance” is blank.

[read-more-redirect urltext=”CatapultSystems.com” url=”https://www.catapultsystems.com/blogs/configmgr-reporting-services-point-with-complex-sql”]

We knew that SSRS was installed, configured, and working as there were two other applications already using the SRS instance in a production capacity.

We verified the domain user account could actually access the SSRS website from Server1 (the ConfigMgr server) and discovered

  • the account was a member of the local Administrators group
  • the account had System Administrator rights to the SSRS Site
  • the account could not see any existing reports or report folders and the following message displayed: “ User ‘<domain>\<userID>’ does not have required permissions.  Verify that sufficient permissions have been granted and Windows User Account Control (UAC) restrictions have been addressed. “

As the screen shot shows, UAC was actually disabled already.

image

Once the domain user account was given rights to the root folder, the Reporting Services point role could see the Reporting Services server instance the the role installed without issue.

image

After the role installed, ConfigMgr reset its own permissions to give the domain user account only “ConfigMgr Report Users, ConfigMgr report Administrators” roles.

image

Also, the logs for the Reporting Services point are on the SSRS server (Server3 in this case), and located at C:\SMS\logs

[/read-more-redirect]

Share this:

  • Click to share on LinkedIn (Opens in new window)
  • Click to share on Twitter (Opens in new window)
  • Click to share on Facebook (Opens in new window)
  • Click to share on Reddit (Opens in new window)
  • Click to print (Opens in new window)

Related Posts

  • ← Error installing Windows ADK
  • ConfigMgr Status Message Viewer MFC120u.dll Missing Error →

You May Also Like

Sccm and branchcache, report all configmgr admin console users, configmgr 2012 and 32-bit application installers.

This browser is no longer supported.

Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.

Configure reporting in Configuration Manager

  • 8 contributors

Applies to: Configuration Manager (current branch)

Before you can create, modify, and run reports in the Configuration Manager console, there are several configuration tasks to complete. Use this article to help you configure reporting in your Configuration Manager hierarchy.

Before you install and configure SQL Server Reporting Services in your hierarchy, review the following Configuration Manager reporting articles:

Introduction to reporting

Plan for reporting

SQL Server Reporting Services

SQL Server Reporting Services is a server-based reporting platform that provides comprehensive reporting functionality for different kinds of data sources. The reporting services point in Configuration Manager communicates with SQL Server Reporting Services to:

  • Copy Configuration Manager reports to a specified report folder
  • Configure Reporting Services settings
  • Configure Reporting Services security settings

When you run a report, the Reporting Services component connects to the Configuration Manager site database to retrieve data.

Before you can install the reporting services point in a Configuration Manager site, install and configure SQL Server Reporting Services on the target site system. For more information, see Install SQL Server Reporting Services .

Verify SQL Server Reporting Services installation

Use the following procedure to verify that SQL Server Reporting Services is installed and running correctly.

Go to the Start menu on the site system, and open Report Server Configuration Manager . You may find it in the Configuration Tools section of the Microsoft SQL Server group.

In the Reporting Services Configuration Connection window, enter the name of the server that hosts SQL Server Reporting Services. Select the instance of SQL Server on which you installed SQL Server Reporting Services. Then select Connect to open Reporting Services Configuration Manager.

On the Report Server Status page, verify that Report Service Status is Started . If it's not in this state, select Start .

On the Web Service URL page, select the URL in Report Service Web Service URLs . This action tests the connection to the report folder. The browser might prompt you for credentials. Verify that the webpage opens successfully.

On the Database page, verify that the Report Server Mode is set to Native .

On the Report Manager URL page, select the URL in Report Manager Site Identification . This action tests the connection to the virtual directory for Report Manager. The browser might prompt you for credentials. Verify that the webpage opens successfully.

Reporting in Configuration Manager doesn't require Reporting Services Report Manager. You only need it if you want to run reports in the browser or manage reports by using Report Manager.

Select Exit to close Reporting Services Configuration Manager.

Configure reporting to use Report Builder 3.0

On the computer running the Configuration Manager console, open the Windows Registry Editor.

Browse to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\ConfigMgr10\AdminUI\Reporting .

Open the ReportBuilderApplicationManifestName key to edit the value data.

Change the value to ReportBuilder_3_0_0_0.application , and then select OK to save.

Close the Windows Registry Editor.

Install a reporting services point

To manage reports at the site, install the reporting services point. The reporting services point:

  • Copies report folders and reports to SQL Server Reporting Services
  • Applies the security policy for the reports and folders
  • Sets configuration settings in Reporting Services

Requirements and limitations

Before you can view or manage reports in the Configuration Manager console, you need a reporting services point. Configure this site system role on a server with Microsoft SQL Server Reporting Services. For more information, see Prerequisites for reporting .

When you select a site to install the reporting services point, users who will access the reports must be in the same security scope as the site where you install the role.

After you install a reporting services point on a site system, don't change the URL for the report server.

For example, you create the reporting services point. You then modify the URL for the report server in Reporting Services Configuration Manager. The Configuration Manager console continues to use the old URL. You can't run, edit, or create reports from the console.

If you need to change the report server URL, first remove the existing reporting services point. Change the URL, and then reinstall the reporting services point.

When you install a reporting services point, specify a Reporting services point account . For users from a different domain to run a report, create a two-way trust between domains. Otherwise the report fails to run.

Install the reporting services point on a site system

For more information about configuring site systems, see Install site system roles .

In the Configuration Manager console, go to the Administration workspace, expand Site Configuration , and then select the Servers and Site System Roles node.

Add the reporting services point to a new or existing site system server:

New site system : On the Home tab of the ribbon, in the Create group, select Create Site System Server . The Create Site System Server Wizard opens.

Existing site system : Select the target server. On the Home tab of the ribbon, in the Server group, select Add Site System Role . The Add Site System Roles Wizard opens.

On the General page, specify the general settings for the site system server. When you add the reporting services point to an existing server, verify the values that you previously configured.

On the System Role Selection page, select Reporting services point in the list of available roles, and then select Next .

On the Reporting services point page, configure the following settings:

Site database server name : Specify the name of the server that hosts the Configuration Manager site database. The wizard typically retrieves the fully qualified domain name (FQDN) for the server. To specify a database instance, use the format < server name >&lt; instance name >. For example, sqlserver\named1 .

Database name : Specify the Configuration Manager site database name. Select Verify to confirm that the wizard has access to the site database.

The user account you use to create the reporting services point must have Read access to the site database. If the connection test fails, a red warning icon appears. Contextual hover text on the icon has the details of the failure. Correct the failure, and then select Test again.

Folder name : Specify the folder name to create and use for Configuration Manager reports in Reporting Services.

Reporting Services server instance : Select the instance of SQL Server for Reporting Services. If this page doesn't list any instances, verify that SQL Server Reporting Services is installed, configured, and started.

Configuration Manager makes a connection in the context of the current user to WMI on the selected site system. It uses this connection to retrieve the instance of SQL Server for Reporting Services. The current user must have Read access to WMI on the site system, or the wizard can't get the Reporting Services instances.

Reporting services point account : Select Set , and then select an account to use. SQL Server Reporting Services on the reporting services point uses this account to connect to the Configuration Manager site database. This connection is to retrieve the data for a report. Select Existing account to specify a Windows user account that you previously configured as a Configuration Manager account. Select New account to specify a Windows user account that's not currently configured for use. Configuration Manager automatically grants the specified user access to the site database.

The account that runs Reporting Services must belong to the domain local security group Windows Authorization Access Group . This grants the account Allow Read permissions on the tokenGroupsGlobalAndUniversal attribute for all user objects within the domain. Users in a different domain than the reporting services point account need a two-way trust between the domains to successfully run reports.

The specified Windows user account and password are encrypted and stored in the Reporting Services database. Reporting Services retrieves the data for reports from the site database by using this account and password.

The account that you specify must have the Log on locally permission on the server that hosts the Reporting Services database.

Complete the wizard.

After the wizard completes, Configuration Manager creates the report folders in Reporting Services. It then copies its reports to the specified report folders.

To list only site systems that host the reporting services point site role, right-click Servers and Site System Roles , and select Reporting services point .

Languages for reports

When Configuration Manager creates report folders and copies reports to the report server, it determines the appropriate language for the objects.

Create report folders, copy reports

Create objects using locale of the site server OS

If the specific language pack isn't available, default to English (ENU)

View reports in a web browser

Folder and report names: the same locale as the site server

Report contents: dynamic based on the browser locale

View reports in the Configuration Manager console

Folder and report names: dynamic based on the locale of the console

Report contents: dynamic based on the locale of the console

When you install a reporting services point on a site without language packs, the reports are installed in English. If you install a language pack after you install the reporting services point, you must uninstall and reinstall the reporting services point for the reports to be available in the appropriate language pack language.

For more information, see Language packs .

File installation and report folder security rights

Configuration Manager does the following actions to install the reporting services point and to configure Reporting Services:

The site does these actions in the context of the account that's configured for the SMS_Executive service. Typically, this account is the site server local System account.

Install the reporting services point site role.

Create the data source in Reporting Services with the stored credentials that you specified in the wizard. This account is the Windows user account and password that Reporting Services uses to connect to the site database when you run reports.

Create the Configuration Manager root folder in Reporting Services.

Add the ConfigMgr Report Users and ConfigMgr Report Administrators security roles in Reporting Services.

Create subfolders, and then deploy Configuration Manager reports from %ProgramFiles%\SMS_SRSRP on the site server to Reporting Services.

Add the ConfigMgr Report Users role in Reporting Services to the root folders for all user accounts in Configuration Manager that have Site Read rights.

Add the ConfigMgr Report Administrators role in Reporting Services to the root folders for all user accounts in Configuration Manager that have Site Modify rights.

Retrieve the mapping between report folders and Configuration Manager secured object types. Configuration Manager maintains this map in the site database.

Configure the following rights for administrative users in Configuration Manager to specific report folders in Reporting Services:

Add users and assign the ConfigMgr Report Users role to the associated report folder for administrative users who have Run Report permissions for the Configuration Manager object.

Add users and assign the ConfigMgr Report Administrators role to the associated report folder for administrative users who have Modify Report permissions for the Configuration Manager object.

Configuration Manager connects to Reporting Services and sets the permissions for users on the Configuration Manager and Reporting Services root folders and specific report folders. After the initial installation of the reporting services point, Configuration Manager connects to Reporting Services every 10 minutes to verify that the user rights configured on the report folders are the associated rights that are set for Configuration Manager users. When users are added or user rights are modified on the report folder by using Reporting Services Report Manager, Configuration Manager overwrites those changes by using the role-based assignments stored in the site database. Configuration Manager also removes users that don't have Reporting rights in Configuration Manager.

Reporting Services security roles

When Configuration Manager installs the reporting services point, it adds the following security roles in Reporting Services:

ConfigMgr Report Users : Users assigned with this security role can only run Configuration Manager reports.

ConfigMgr Report Administrators : Users assigned with this security role can do all tasks related to reporting in Configuration Manager.

Verify installation

Verify the installation of the reporting services point by looking at specific status messages and log file entries. Use the following procedure to verify that the reporting services point installation was successful.

If you see reports in the Reports subfolder of the Reporting node in the Monitoring workspace in the Configuration Manager console, you can skip this procedure.

Verify installation by status message

In the Configuration Manager console, go to the Monitoring workspace, expand System Status , and select the Component Status node.

Select the SMS_SRS_REPORTING_POINT component.

On the Home tab of the ribbon, in the Component group, select Show Messages , and then choose All .

Specify a date and time for a period before you installed the reporting services point, and then select OK .

Verify status message ID 1015 . This status message indicates that the reporting services point was successfully installed.

Verify installation by log file

Open the Srsrp.log file, located in the Logs directory of the Configuration Manager installation path. Look for the string Installation was successful .

Step through this log file starting from the time that the reporting services point was successfully installed. Verify that the report folders were created, the reports were deployed, and the security policy on each folder was confirmed. After the last line of security policy confirmations, look for the string Successfully checked that the SRS web service is healthy on server .

Configure a certificate to author reports

There are many options for you to author reports in SQL Server Reporting Services. When you create or edit reports in the Configuration Manager console, Configuration Manager opens Report Builder to use as the authoring environment. Regardless of how you author your Configuration Manager reports, you need a self-signed certificate for server authentication to the site database server.

For more information about authoring reports with SQL Server Reporting Services, see Report Builder authoring environment .

Configuration Manager automatically installs the certificate on the site server and any SMS Provider roles. You can create or edit reports from the Configuration Manager console when you run it from one of these servers.

When you create or modify reports from a Configuration Manager console on a different computer, export the certificate from the site server. The specific certificate's friendly name is the FQDN of the site server in the Trusted People certificate store for the local computer. Add this certificate to the Trusted People certificate store on the computer that runs the Configuration Manager console.

Modify reporting services point settings

After you install this role, you can modify the site database connection and authentication settings in the reporting services point properties.

To list only site systems that host the reporting services point, right-click the Servers and Site System Roles node, and select Reporting services point .

Select the site system that hosts the reporting services point. Then select the Reporting service point site system roles in the details pane.

On the Site Role tab of the ribbon, in the Properties group, select Properties .

You can modify the following settings in the Reporting Services Point Properties :

Site database server name

Database name

User account

Select OK to save the changes and close the properties.

For more information about these settings, see the descriptions in the section to Install the reporting services point on a site system .

Power BI Report Server

Starting in version 2002, you can integrate reporting with Power BI Report Server. For more information on configuring it, see Integrate with Power BI Report Server .

Upgrade SQL Server

To upgrade SQL Server and SQL Server Reporting Services, first remove the reporting services point from the site. After you upgrade SQL Server, then reinstall the reporting services point in Configuration Manager.

If you don't follow this process, you'll see errors when you run or edit reports from the Configuration Manager console. You can continue to run and edit reports successfully from a web browser.

Configure report options

You can select the default reporting services point that you use to manage reports. The site can have more than one reporting services point, but it only uses the default server to manage reports. Use the following procedure to configure report options for your site.

In the Configuration Manager console, go to the Monitoring workspace, expand Reporting , and then select the Reports node.

On the Home tab of the ribbon, in the Settings group, select Report Options .

Select the default report server in the list, and then select OK .

If it doesn't show any servers, verify that you installed and configured a reporting services point in the site. For more information, see Verify installation .

Make sure your computer runs a version of SQL Server Report Builder that matches the version of SQL Server that you use for your report server. Otherwise you'll see an error, the default report server won't save, and you can't create or edit reports.

Operations and maintenance for reporting

Submit and view feedback for

Additional resources

IMAGES

  1. Install SCCM Reporting Services Point Role

    reporting services server instance blank sccm

  2. SCCM Reporting Services Point

    reporting services server instance blank sccm

  3. Upgrade SSRS SQL Server Reporting Services To 2019 For SCCM Infrastructure HTMD Blog

    reporting services server instance blank sccm

  4. SCCM doesn't see Reporting Services on a remote named sql instance

    reporting services server instance blank sccm

  5. Install ConfigMgr SSRS Reporting Services Point

    reporting services server instance blank sccm

  6. Install SCCM Reporting Services Point Role

    reporting services server instance blank sccm

VIDEO

  1. Reporting Services con ASP.NET

  2. SQLServer Reporting Services Part 2

  3. Developing a Simple SQL Server 2008 Reporting Services Report

  4. 6. StoreFront Server Configurations & Testing the deployment

  5. How to Enable Submit non-encrypted from date in server 2012

  6. Microsoft System Center Configuration Manager 2007 LAB 1 / 13

COMMENTS

  1. The Role of Blank W2 Forms in Employee Tax Reporting

    When it comes to employee tax reporting, one crucial document that plays a significant role is the W2 form. This form provides essential information about an employee’s wages and taxes withheld throughout the year.

  2. The Benefits of Using Blank Forms to Print in Your Office

    In today’s digital age, it’s easy to assume that all paperwork and forms can be completed online. However, there are still many instances where having physical documents is necessary. This is where blank forms to print come in handy.

  3. What Is a 9-Line UXO Report?

    A 9-line UXO report is a document with nine blank fields, or sections, for reporting an unexploded ordnance (UXO). UXO is any form of explosive or ammunition that has failed to detonate as intended. The report is used to show where the UXO ...

  4. MECM Reporting point server instance blank with remote sql server

    When I try to install sql reporting service role it show instance blank. ... sccm-reporting-services-point/. Please sign in to rate this answer. 5

  5. Reporting Services Point

    To resolve the problem ensure that the Reporting Services site role is installed on the SQL server and not the SCCM server. In Administration

  6. PENDING

    Hi, I've been trying to get the reporting service on our SCCM server working without any luck, so hoping someone may know a fix.

  7. Reporting Services Site Role Setup: Instance Blank/Empty

    Open Reporting Services Configuration Manager · Connect to the server/instance · Click on Web Service URL – make a fake change, such as changing

  8. SCCM 2012 SP1 Reporting Services Server Instance is Blank

    I had the same problem and I had to reinstall the SQL service pack onto the Database Instance. This is a protection feature of Microsoft even if

  9. {Quick Fix} SSRS instance showing blank while installing reporting

    Check 1: Run reporting extensions set-up (SetupSrsDataConnector.exe) from box where reporting services is installed. · Check 2: Service account

  10. Install SCCM Reporting Services Point Role

    This step is critical because the majority of errors such as reporting services server instance blank, is observed here. If you have installed

  11. SCCM 2012 Reporting point server instance blank

    I have installed SCCM 2012 With remote SQL database server successfully, at the time of Reporting service point role installation, its verified the SCCm

  12. Setup Configure SCCM Reporting Services Point ...

    Connect to the SQL Report Server Instance. Make sure the report service status is in the started stage. If not prompted, click on START. SQL

  13. ConfigMgr Reporting Services Point with complex SQL

    SCCM 2012 SP1 downloads. Tags. Azure AD BitLocker ConfigMgr DFS-R DirectAccess FRS

  14. Configure reporting

    Select the instance of SQL Server on which you installed SQL Server Reporting Services. Then select Connect to open Reporting Services