SSRS second entry never shows up in scale out deployment screen

All we need is an easy explanation of the problem, so here it is.

I am trying to setup two SSRS servers in a scale-out deployment that use a Always-On availability group for the database.

  • The AG is setup and working.
  • I have both SSRS servers using the AG listener on the Database page
    of the Report Server Configuration Manager.
  • All credentials in SSRS configuration manager are using domain
    accounts.

Should work right?

When I go to the Scale-out Deployment page in the SSRS configuration manager I only ever get one entry in the list.
And the entry seems to flip back and forth between the two SSRS server.

i.e. when I look at the list on the Scale-out Deployment page, one minute it will say ServerA the next minute it will say ServerB but it never shows both at the same time so I can add ServerB.

Any Ideas?

How to solve :

I know you bored from this bug, So we are here to help you! Take a deep breath and look at the explanation of your problem. We have many solutions to this problem, But we recommend you to use the first method because it is tested & true method that will 100% work for you.

Method 1

Wound up contacting MS for a solution to this. Turns out when the servers were setup, an image was used (AWS). As a result, the Installation ID for both servers were identical. Here is the solution from MS:

We tried to add Reportserver DB to AG and configure, still we were
facing the issue.

From dbo.keys we can see that installation id is same in config files
of both servers.

I tried to replicate the issue in my Lab by giving the same
installation id and followed below steps to resolve the issue.

Please use below action plan and let us know if it works. Please let
us know if you need help in performing below steps so that I will
schedule a meeting.

  1. Go to SQL server instance and run below query. We will get a sample
    id. SSRS second entry never shows up in scale out deployment screen

  2. Go to config file in the server which is not working now Path :
    C:\Program Files\Microsoft SQL Server Reporting
    Services\SSRS\ReportServer File name : rsreportserver.config Open this
    file and search for And change the installation ID
    to the one which we got from the query in step1 Restart the service.

  3. Check dbo.keys for new installation id as shown below. enter
image description here

  4. If you are still facing issue related to encryption keys. Please
    delete the encryption key and restart the service. 5) Add the server
    in scale out deployment after this step.

Note: Use and implement method 1 because this method fully tested our system.
Thank you 🙂

All methods was sourced from stackoverflow.com or stackexchange.com, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0

Leave a Reply