in Service Manager

Performing fresh installation of Service Manager with SQL Server 2014

Since the release of Service Manager 2012 R2 Update Rollup 6, the use of SQL Server 2014 is officially supported by Microsoft. This probably seems like a pretty good thing because for new installations you probably want to use the newest SQL Server version. And since SQL Server 2014 was released back in April 2015 more and more customers are using latest version for their System Center deployments.

Well, this all sounds pretty good in theory. However if you really want to use SQL Server 2014 together with Service Manager 2012 R2 you may run into some issues. There exists an official blog post describing how to install a secondary management server after an upgrade to SQL 2014. However installation is quite a bit of a pain because the graphical installer does not yet support installation of a management server together with SQL 2014. As soon as you get to select the database server you will be prompted with a message saying that “SQL Server <Servername> is not running SQL Server 2008R2 or SQL Server2012. Please update a newest version and retry”.

SQL Server Version Error

Well in order to get around this problem you have to use the command line to install the secondary management server. This is perfectly fine, but still installation only works if an in-place upgrade of SQL Server 2012 to SQL Server 2014 was done and fails for the fresh installation of SQL Server 2014.
Unfortunately the installer checks for the SQL Server 2012 Namespace in the SQL server machine. If the namespace Root\Microsoft\SqlServer\ComputerManagement11 is not present in SQL server machine then the command line installation fails.

In order to get past the above mentioned issue, you could install a dummy instance of SQL Server 2012 on the SQL server machine. A much simpler solution however would be to create the mentioned namespace by using PowerShell (thanks to Aaron Croasmun for mentioning this in the comment section of the Deploying Secondary Management Server after SQL 2014 upgrade blog post)

Add the namespace to WMI of your SQL server by using the following commands:

With the above commands we can in fact trick the Service Manager installer to think that SQL Server 2012 is present on our database server.

What works for the installation of a secondary management server does also for a fresh installation of Service Manager 2012 R2. We just have to slightly adjust the command to start a fresh Service Manager installation instead of adding a secondary management server:

I have to mention, that this installation procedure may not be completely supported by Microsoft as in fact SQL Server 2014 is only supported with Update Rollup 6 installed. But there is no process to manually slipstream UR6 into existing Service Manager installation media and you would basically be forced to do a fresh installation of Service Manager 2012 R2 with SQL Server 2012 and upgrade SQL Server after applying UR6.

Using the above command line installation completes successfully even without UR6 installed. You can check installation status by looking into the installer log files located in C:\Users\<Username>\AppData\Local\Temp\2.
Of course you will have to install the latest Update Rollup to make sure SQL Server 2014 is properly supported. You can then safely remove the previously created ComputerManagement11 namespace from your SQL server:

Voilà, your Service Manager environment should now be up and running with SQL Server 2014 without the hassle of performing a SQL upgrade. Just remember to use command line again if you want to install additional management servers. An example can be found on the official Service Manager blog.

Write a Comment

Comment

  1. This worked great for our fresh installation of our primary management server. But we are getting another error when it comes to installing the Data warehouse . Is there a different wmiobject that needs to be added?

    01:56:07:Attempting connection to SQL Server 2012 management scope on servername fqdn
    01:56:07:Using SQL Server 2012 management scope on servername fqdn
    01:56:07:Failed while trying to check remote AS: Invalid class – at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
    at System.Management.ManagementObjectCollection.ManagementObjectEnumerator.MoveNext()
    at System.Management.ManagementObjectCollection.get_Count()
    at Microsoft.SystemCenter.Essentials.SetupFramework.HelperClasses.SetupValidationHelpers.PreReqRemoteMachineforAS(String hostName)
    at Microsoft.SystemCenter.Essentials.SetupFramework.HelperClasses.SetupValidationHelpers.ValidateAS(String hostName).
    01:56:07:***ERROR*** : The server is not available.

    • Hi Matt
      Unfortunately I never did a fresh installation of a DWH management server with SQL 2014 so this error is new to me… Error message seems to point to Analysis Services though. It’s actually possible that you’ll have to add another WMI namespace for your SQL Analysis Services installation. There exists a WMI provider for Reporting Services, but I don’t know about Analysis Services unfortunately

    • Hi Matthias
      That’s correct. As already stated in the post, this is probably not supported by Microsoft. But the described workaround does actually work for me. I tested this successfully in my lab environment. What’s the issue in your case?
      Cheers,
      Stefan

Webmentions

  • Running SCSM 2016 TP5 on SQL AlwaysOn Availability Group – “Execution of user code in the .Net Framework is disabled” – Stefan Johner April 2, 2016

    Hi Matthias
    That’s correct. As already stated in the post, this is probably not supported by Microsoft. But the described workaround does actually work for me. I tested this successfully in my lab environment. What’s the issue in your case?
    Cheers,
    Stefan

  • SCSM 2012 R2 Fresh Install & SQL 2014 AlwaysON – winning here! | SCOM, OMS, the Cloud & Everything Else - A field diary April 2, 2016

    Hi Matthias
    That’s correct. As already stated in the post, this is probably not supported by Microsoft. But the described workaround does actually work for me. I tested this successfully in my lab environment. What’s the issue in your case?
    Cheers,
    Stefan