On a previous article I wrote about a “problem” that happens when we try to install the Reporting Point service of System Center Configuration Manager in a server with more than one instance and/or without a default instance of SSRS.
On that article I mentioned that we really need a default instance of SSRS to install Reporting Point and that there would be two situations where this requisite would not be so simple.
One of these situations is when we have a default instance of the database engine in a cluster. On this type of environment, we can NOT add the SSRS service using the “default” method. If we execute SQL Server installer and try to add the SSRS service to an existing instance in a cluster you will problably receive this message during server validations:
Failed – The instance selected for installation is already installed and
clustered on computer <name>. To continue, select a different instance to
So, imagine a situation where you only have a default sql server instance, clustered, available to install Reporting Point, or any other service, but you don’t have the SSRS installed. What can I do, since you can not remove the instance to reinstall it with the SSRS service, since it would mean making the service unavailable.
In this case, we may use an alternative measure. We will have to execute SQL Server installation by command line and use a parameter telling the installation to ignore the validation of an existing instance. The command would be like this:
Setup.exe /SkipRules=StandaloneInstall_HasClusteredOrPreparedInstanceCheck /Action=Install
This way the installation is going to happen the same way as before, with the same screens, but on the screen of the previous image, there would be no error message and you would be able to finish the installation.
I just do not know yet how Microsoft deals with this type of environment, if it makes the product unsupported or/if they have any way to identify this.
Anyway, if you do this procedure, make sure you install SSRS with a SLIPSTREAM installation, which means adding service packs and/or cumulative updates to the installation.
If you do not SLIPSTREAM the installation, later when you try to patch the instance you may get this error message:
since the build is different between the services. In this happens to you the only way to fix it is removing SSRS service from the instance and only then patch the other services.
I tried to find a way to patch only SSRS, but I could not find any.