November 7, 2016 at 12:27 pm
Does anyone know if we can still install SSRS on both nodes of an active-passive SQL 2016 Cluster ?
On SQL Server 2012, I could get it to work using the following work-around:
However, I'm getting the below error during the installation on SQL 2016.
Is there a different work-around for 2016? Or is it not possible at all to do this in SQL 2016?
Appreciate any insights.
Thanks!
(01) 2016-10-27 16:39:17 Slp: Exception type:
Microsoft.SqlServer.Configuration.SetupExtension.InstanceNameIsUsedByAnotherInstanceException
(01) 2016-10-27 16:39:17 Slp: Message:
(01) 2016-10-27 16:39:17 Slp: Instance name 'MSSQLSERVER' is
already in use. To continue, specify a unique instance name.
(01) 2016-10-27 16:39:17 Slp: HResult : 0x858c0014
(01) 2016-10-27 16:39:17 Slp: FacilityCode : 1420 (58c)
(01) 2016-10-27 16:39:17 Slp: ErrorCode : 20 (0014)
(01) 2016-10-27 16:39:17 Slp: Data:
(01) 2016-10-27 16:39:17 Slp: SQL.Setup.FailureCategory =
InputSettingValidationFailure
(01) 2016-10-27 16:39:17 Slp: instanceName = MSSQLSERVER
(01) 2016-10-27 16:39:17 Slp: WatsonData =
Microsoft.SqlServer.Configuration.SetupExtension.InstanceNameIsUsedByAnotherInstanceException@20
(01) 2016-10-27 16:39:17 Slp: DisableWatson = true
(01) 2016-10-27 16:39:17 Slp: Stack:
(01) 2016-10-27 16:39:17 Slp: at
Microsoft.SqlServer.Chainer.Infrastructure.InputSettingService.LogAllValidationErrorsAndThrowFirstOne(ValidationState
vs)
(01) 2016-10-27 16:39:17 Slp: at
Microsoft.SqlServer.Configuration.SetupExtension.ValidateFeatureSettingsAction.ExecuteAction(String
actionId)
(01) 2016-10-27 16:39:17 Slp: at
Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String
actionId, TextWriter errorStream)
(01) 2016-10-27 16:39:17 Slp: at
Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
(01) 2016-10-27 16:39:17 Slp: at
Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker
workerDelegate)
(01) 2016-10-27 16:44:58 Slp: SetupTelemetry: Writing Telemetry to Datastore
November 8, 2016 at 4:37 am
the workaround is not supported by MS, standalone features cannot be added to existing clustered features.
This link https://msdn.microsoft.com/en-us/library/bb630402.aspx details the following
MSDN - Host a Report Server Database in a SQL Server Failover Cluster
Although the Report Server service cannot participate in a failover cluster, you can install Reporting Services on a computer that has a SQL Server failover cluster installed. The report server runs independently of the failover cluster.
The SSRS instances should be installed under a new instance ID different to any existing cluster aware features. It makes no difference if the SSRS instances have a different instance ID, especially since you'll likely be load balancing the SSRS instances and the original URLs will be transparent to the end users.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
November 8, 2016 at 9:44 am
Thanks for the reply.
I agree that the workaround isn't supported my MS. Also, the link you posted applies to all versions starting from 2008 R2.
However, I was able to install SSRS on the default instance of both nodes of a SQL Server 2012 cluster - without having to create a new instances. I realize that this isn't encouraged by MS but SSRS always needed some tweaks.
I suspect this workaround isn't possible in SQL Server 2016. Perhaps MS plugged this hole permanently?
What I would like to know is - has anyone successfully installed SSRS on the default instance of a SQL 2016 cluster?
Thanks!
November 13, 2016 at 6:51 am
Hi,
SSRS is not Cluster capable and as far as I know never was.
The only way of installing it on existing Cluster nodes has been explained here:
1. Install SSRS on the first node as a new instance. The databases for the Report Server can be hosted on the Cluster.
2. Install the SSRS on the second node without a database. When the Installation is finished Point the second RS to the databases created in #1.
3. Restore the encryption key from the first Server onto the second.
3. The important Point to note here is to use Domain accounts for the Services otherwise it won't work as expected over the load balancer.
4. Configure the NLB for the two Report Servers.
Roughly put together reply I know but it will work.
regards,
Kev
November 14, 2016 at 6:40 am
What kevaburg says works on all versions of SQL Server above SQL 2005 (it probably works on SQL2005 but I have not tested it there).
You can also use this technique to cluster SSRS Standard Edition.
SQL FineBuild will do all of this work for you automatically if you install a SQL Cluster that includes SSRS.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply