Deployed with: SQL Server 2012 Enterprise
According to available documentation installing Reporting Services in already clustered SQL Server instance is not possible. If you want the Reporting Services on the other nodes you must install them in separate SQL Server instances. This “feature” was first introduced in SQL Server 2008 and it remains the same in SQL Server 2012. There was a workaround solution I wrote about in my post Installing SQL Server 2008 Reporting Services on Failover Cluster in already clustered instance.
Multiple instances mean a lot of administration because each instance must be handled separately. There are scenarios when you should or want to use multiple instances, but I wanted to use existing Windows/SQL failover cluster instance. Running setup on the second node and selecting the Reporting Services will caus setup to fail with following error:
“Failed – The instance selected for installation is already installed and clustered on computer.To continue, select a different instance to cluster.”
The solution is to run setup with option to skip check if Reporting Services are installed in already clustered instance. Don’t forget first to add SQL Server failover cluster on another node. Run the setup again with the following command at the command prompt to add Reporting Services on other nodes:
Setup.exe SkipRules=StandaloneInstall_HasClusteredOrPreparedInstanceCheck Action=Install
This will run Setup in full interaction GUI mode while skipping cluster instance check. Just follow setup to install Reporting Services in SQL Server clustered instance.
After installing Reporting Services on failover cluster please keep in mind:
- Reporting Services running on an Active-Passive cluster handle requests on each cluster node on which the service is deployed.
- Report server must be configured to use SQL failover cluster virtual name to connect to the report server database. This is because it is hosted on a SQL Server that is part of a failover cluster. If not, the report server will be unable to connect to the report server database if a failover occurs.
This solution provides the highly available Reporting Services with default SQL server instance and uses already deployed hardware. It is not substitute for a true Scale-out deployment of the Reporting Services, but a way of achieving high availability (we just used the existing high availability platform).