SSRS scale-out deployment configuration error

By | May 5, 2014


This article describes SSRS scale-out deployment configuration error that can occur during migration of the ReportServer database from SSRS 2008 Enterprise/Developmnet to SSRS 2012 Standard (Native mode). When importing encryption keys from the source server a scale out deployment server is added to the configuration on the new target server that cannot be removed through the user interface. The scale-out deployment configuration is also not supported by the SSRS 2012 Standard edition. I have not verified the reason for this behaviour in detail but the affected system(s) in the article is:
Microsoft SQL Server 2008 SP1 10.0.2841.0 (x64) Developer Edition (source system)
Microsoft SQL Server 2012 SP1 11.0.3401.0 (x64) Standard Edition (target system)
Microsoft Windows Server 2012 R2 Version 6.3 (Build 9600) (target system)


You have your old server  (SQL 2008 SP1) with lot of reports that you would like to migrate to a new server with a newer version of Reporting Services (SQL 2012). To accomplish this you can migrate the ReportServer database from the old server to the new.

Migration steps:

  1. Backup ReportServer database on source machine
  2. Backup encryption keys on the source machine
  3. Restore of ReportServer on the target machine
  4. Change/connect the database to ReportingServices on the target machine using Microsoft Reporting Services Configuration Manager
  5. Restore encryption keys on the target machine

For more detailed explanations please see:
Migrate a Reporting Services Installation (Native Mode)

Moving the Report Server Databases to Another Computer

Scale-out deployment configuration error
However when doing step 5 the old server will be added for scale-out deployment on the target machine. If the source and target machine are using different licenses of Reporting Services you might encounter issues that some features are not supported when migrating to a less featured sql server license.

One such issue can be when you try to browse to the report manager url and get the following error:
ssrs scale out deployment error
The feature: “Scale-out deployment” is not supported in this edition of Reporting Services. (rsOperationNotSupported)

Normally that should not impose a problem since you would be able to remove the old server from scale-out deploment from the list in Microsoft Reporting Services Configuration Manager:
SSRS Delete Scale Out Deployment Server Error

At least one would think so… however as seen in the image above this might not work as expected. If you click the link “Tell me more about the problem and how to resolve it” you will get the following:

Microsoft.ReportingServices.WmiProvider.WMIProviderException: No report servers were found. ---> System.Management.ManagementException: Invalid namespace
 at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
 at System.Management.ManagementScope.InitializeGuts(Object o)
 at System.Management.ManagementScope.Initialize()
 at System.Management.ManagementScope.Connect()
 at ReportServicesConfigUI.WMIProvider.RSInstances.GetInstances(String machineName)
 --- End of inner exception stack trace ---
 at ReportServicesConfigUI.WMIProvider.RSInstances.GetInstances(String machineName)
 at ReportServicesConfigUI.WMIProvider.RSInstances.GetInstance(String machineName, String instanceName)
 at ReportServicesConfigUI.Panels.ClusterManagementPanel.ConfigureWebFarm(Object sender, RSReportServerInfo[] rsInfos)


Fortunately there is an easy solution for this problem. Open up table dbo.Keys in the ReportServer database on the target server and look at its contents:
ReprtServer dbo.keys table

Delete the old server from the list and the scale-out deployment error should be gone when you open up report manager url. (At least if you do not have any additional enterprise/developer features referenced from the reportserver database)

DELETE FROM [ReportServer].[dbo].[Keys]
WHERE MachineName = 'YourSourceServerName'

24 thoughts on “SSRS scale-out deployment configuration error

  1. Eric Ness

    Thanks so much for this post. I thought it would take forever to resolve this problem, but after finding the post I had it resolved in a few minutes.

  2. Puja

    Really appreciate the post! I have similar issue and need your help.

    I want to migrate SSRS 2008 R2 Standard Edition SharePoint Integrated Mode reports to SSRS 2012 SP1 Standard Edition with SharePoint Integrated Mode. Want to test the migration on development before moving with actual production migration.

    I followed these steps:
    1. Backup (source) -copy-restore (destination) of Report Server Catalog and Temp databases along with Content database.
    2. Opened Reporting configuration > Created virtual directory.
    3. For database configuration> selected the restored Report Server Catalog database on destination server and upon clicking next it gives this error message: “The database you have selected is configured for Reporting Services SharePoint mode. Please select a SQL Server database that is configured for Reporting Services native mode.”

    I tried the workaround provided in this post to delete an entry from Keys table. The Keys table had machine name of SharePoint App Server (SharePoint 2010). As a part of the migration, we are also migrating from SharePoint 2010 to SharePoint 2013.

    1. admin Post author

      Hi Puja,

      Have a look here:
      and here:

      I believe you need to install and configure SharePoint and Reporting Services in SharePoint Integrated Mode in the new environment. When this is done migrate the content over by backup/restore or detach/attach database(s) and configuration settings.


      1. Puja

        Hi Jonas,
        Thanks for your response.
        I followed the steps listed in the link, but not working me. I will look for what is wrong, could be the SharePoint integrated mode files are not installed.


  3. Jayanth

    Brilliant…just brilliant…me and teammate had spend almost a week trying to fix this issue and you have just given the most simplest solution. It was like looking for a needle in a haystack…thanks a ton for this blog/post…really saved our production reports….many thanks…

Leave a Reply