Apologies for lack of posts but work’s been crazy.
The above is not a new topic, but nevertheless is worthy of a post as I couldn’t find one place where all the information was.
Basic problem – Installing a new SCSM 2012 R2 environment to a brand new shiny SQL 2014 AlwaysOn environment. The problem is two-fold
- The GUI installer for 2012 R2 doesn’t recognise the SQL 2014 platform as supported
- The SQL Listener returns a “***ERROR*** Validate Arguments: A required SQL Server service is not running on <your listener name here>” error
So, in true style, I turn to the wonderful community to find a handful of blogged solutions for each of the problems above and this post then brings the entire solution together.
The excellent TechNet blog detailing creating a 2012 AlwaysOn Availability group can be found here, and uses the same principle/wizard as for 2014. Creating a dummy Database is a really good idea here as it allows the creation of the Availability Group via the Wizard and then all the prereqs and Network settings are done.
Hi Level Solution
- Update the SQL Nodes with the NoNamedPipes workaround to enable the SM Installer to communicate with the AlwaysOnListener
- Update the SQL Nodes with the relevant SQL 2012 WMI NameSpace to satisfy the SM Installer’s pre-requisites
- Run the Installer (for the first and then secondary Management Server[s])
- Run the Installer for the Data Warehouse Management Server
SQL 2012 Namespace Solution
Link from Stephan Johner covering the fresh install to a SQL 2014 platform
And the original TechNet posting covering installing a Secondary Management Server to that of an upgraded-TO 2014 Environment:
This effectively tricks the SM Installer into thinking the 2014 SQL Server is hosting a SQL 2012 Platform by adding the relevant 2012 WMI Namespace, so when queried meets the Installers Pre-requisite checks.
But before we can do that – using a SQL AlwaysOn Listener with the above approach “may” result in the above error: “***ERROR*** Validate Arguments: A required SQL Server service is not running on <your listener name here>”
in the logfile: “SCSMSetupWizardX” (by default located in C:\Users\<userID>\AppData\Local\Temp)
Effectively the Installer is unable to contact the SQL Server and so the following post gave the workaround, as supplied by Microsoft:
Back up the registry on each of your SQL nodes and then create a registry file from the below text merge so you can easily merge the required parameter.
Windows Registry Editor Version 5.00
This effectively inserts a Multi-SZ Registry value into the above hive
Then, run the following on each of the SQL Nodes in an elevated PowerShell session in order to update the WMI Namespace with the 2012 NameSpace:
$nameSpace = [wmiclass]”root\Microsoft\SQLServer:__Namespace”
This can then be tested with the below code:
Get-WmiObject -Namespace “Root\Microsoft\SqlServer\ComputerManagement11” –List
This should return satisfying PowerShell object:
Then you should now be able to run the below code to install a fresh copy of Service Manager 2012, to a 2014 AlwaysON Listener: (replacing my entries where appropriate)
First Server Syntax
.\Setup.exe /Install:Server /AcceptEula /ProductKey:'XXXXX-XXXXX-XXXXX-XXXXX-XXXXX' /CreateNewDatabase /SqlServerInstance:'SCSMListener' /ManagementGroupName:'LAB-SCSM-AO-MG' /AdminRoleGroup:'LAB\gs-SCSM-Administrators' /ServiceRunUnderAccount:'lab\svc-scsm-sdk\password' /WorkflowAccount:'lab\svc-scsm-wrk\password' /CustomerExperienceImprovementProgram:NO /EnableErrorReporting:NO /Silent
N.B. remove the “.\” if running from a standard CMD prompt, but who does that now eh? 🙂
Secondary Management Server:
.\setup /Silent /Install:Server /AcceptEula /UseExistingDatabase:'SCSMListener' /AdminRoleGroup:'LAB\gs-SCSM-Administrators' /ManagementGroupName:'LAB-SCSM-AO-MG' /ServiceRunUnderAccount:'lab\svc-scsm-sdk\password' /WorkflowAccount:'lab\svc-scsm-wrk\password' /EnableErrorReporting:No /CustomerExperienceImprovementProgram:No /ProductKey:'XXXXX-XXXXX-XXXXX-XXXXX-XXXXX'
Data Warehouse Server:
<Coming Soon> - as soon as I've tested the syntax I will update the post :)
Hope that helps as it puts all the resources you might need in one place. Please note these posts are intended for information only and should be tested in a Lab before deploying to enterprise environments.
Until next time,