Twitter Feed
Tweets by SundownSolLtd

Configuring SP2010 SSRS using SQL2012 for a multi-server environment

3rd August


Common errors this post helps rectify:

Error: Report Server WMI Provider error: Invalid namespace
Error: "Installation Error: Could not find SOFTWARE\Microsoft\Microsoft SQL Server\110 registry key"

If you are deploying SSRS using SP2010 and SQL2012 (multi-server environment) it is key to note that the new SP2013 mechanism of configuring SSRS as a service app is applied. Just to call this out in its truest sense, you no longer use SSRS configuration manager or the central admin options for reporting services. Instead you create a Service Application.

So if you are seeing the above error, you are trying to configure SSRS the SP2010 and SQL2008 way – when you need to configure it using the SP2010 and SQL2012 method – make sense?
All the guidance on this subject assumes a single farm and not a multiple farm initial deployment using sql2012 and there is very little out there for a multi farm environment.

When you do a multi-server deployment, the sql box will be installed and configured first, which means the SSRS component hasn't had chance to register with the SharePoint machines. The upshot of this is that the following commands don't work:

Install-SPRSService

Install-SPRSServiceProxy

If you look at the instructions for the Reporting Services add-in it clearly states that the add-in should be ran on a server running a SharePoint product. Although our SQL box is joined to the farm it shouldn't have SharePoint installed on it – which means we have to add BOTH the add-in and the Reporting Services for SharePoint on an application or web front end server. If you just install the add-in on an app or wfe server then when starting the service application you will receive this error:

"Installation Error: Could not find SOFTWARE\Microsoft\Microsoft SQL Server\110 registry key"

So to be clear – the high level steps for setting up SSRS in SP2010 using SQL2012 in a multi-server environment are:
Install SQL as you would normally – without 'Reporting Services – SharePoint' or the add-in
Then Install and configure Your SharePoint farm as normal

Once your SharePoint farm is up and running and you are ready to progress, log on to your application/WFE and use the SQL 2012 installation media to add the 'Reporting Services – SharePoint' and the add-in to the application/WFE servers of your choice.

The SSRS PowerShell commandlets will now be registered. Progress with the SSRS installation guide below from the section "Install and Start the Reporting Services SharePoint Service": Link

Another note of caution here is that for SSRS to work the SharePoint reporting services add in has to be installed on EVERY web front end server.

Useful Resources:

Install Reporting Services - Link

Troubleshoot Reporting Services - Link

Follow Us