in Service Manager

Resolve “SQL Server service not running” when installing Service Manager database on SQL AlwaysOn Availability Group

As you may know, there are some things to remember when installing Service Manager database in a SQL AlwaysOn cluster environment. For example SQL Server AlwaysOn Availability Groups functionality is supported by all versions of Service Manager, but only for the default server instance. Also those of you who tried to install Service Manager in a SQL AlwaysOn environment may have experienced the following error when it comes to configuring the database part in the Service Manager install wizard

A required SQL Server service is not running on <YourSqlServer> MSSQLServer

ServiceNotRunningError

Of course you have SQL server up and running on your SQL cluster nodes and the necessary services are running fine. Also you may notice that if you don’t use your SQL Availability Group listener but the IP address of one of your SQL cluster nodes, the install wizard will let you continue with Service Manager setup.

Some posts out there are suggesting installing Service Manager database to one of the cluster nodes and switching database server name in registry after a successful installation. And although this perfectly works, there exists a more comfortable way to work around this issue.

To be able to continue with Service Manager setup you have to add the following key to the registries of your SQL AlwaysOn cluster nodes. According to a Microsoft article  the NoRemapPipes registry key controls how named pipes are opened on the network that is managed by the Network Name resource. If RemapPipeNames is set to TRUE, named pipes are always opened by using local pipe names.

Key: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesLanmanServerParameters
Name: NoRemapPipes
Type: REG_MULTI_SZ
Data: winreg svcctl eventlog

RegChange

Hope this helps 🙂 Merry Christmas and a happy New Year to all of you!

Write a Comment

Comment

  1. Hello. Good point, it resolves 50% of my problematic. Do you know if i can install Service Manager with Latin_General_CP1_CI_AS Collation (already used by SCOM 🙂 ) ? If i check on Technet prerequisites, it would be ok, but when i try the installation i have an error like this “Bad collation.. blabla..”

    • Hi Jeremy
      I assume you are referring to SQL_Latin1_General_CP1_CI_AS collation right? SCSM installer shows you a warning message when using this collation but you should be able to bypass and continue with installation.
      I never installed SCSM with this collation and I would not recommend using SQL_Latin1_General_CP1_CI_AS since there might be some issues when storing newer Unicode characters. Check out this blog post for clarification on SQL Server collation requirements for System Center 2012.
      Hope this helps!

      • Hi Stefan, thank you. If i refer to this blog, it is say “You can bypass this warning message and continue to install using the SQL_Latin1_General_CP1_CI_AS” but not how we can do this ? I wish to use a common SQL AlwaysON infrastructure for SCOM, SCOR and now SCSM (1 AG per product). But as you know, each AG inherits of the SQL instance collation (in that case General_CP1_CI_AS…). If only i could apply a collation per AG…

Webmentions

  • Installing Service Manager – “A required SQL Server service is not running” – The Automation Guy December 26, 2014

    […] N.B. Credit to Stefan Johner who first blogged about it here! […]

  • MicrosoftTouch December 26, 2014

    […] Plus d'informations: http://scsmlab.com/2014/12/23/resolve-sql-server-service-not-running-when-installing-service-manager&#8230; […]