Service Manager 2012 SP1 secondary Management Server–Cannot set availability on a health service that doesn’t exist

Service Manager 2012 SP1 secondary Management Server–Cannot set availability on a health service that doesn’t exist

  • Comments 15
  • Likes

Just a heads up, in Service Manager 2012 SP1, we made certain changes to custom actions in setup which renders fresh installs of the secondary management server incapable of connecting to the Management Group. This issue was first surfaced in a blog post at Please read this blog post for a detailed explanation of the problem.

Once again, this issue ONLY impacts SCSM 2012 SP1 new installs. It does not impact those customers who are either upgrading from Service Manager 2012 RTM, or are installing only the primary management server. The recommended workaround to address this issue yourself is to install System Center Service Manager 2012 RTM and then upgrade to SP1. If for any reason you are unable to do this, please reach out to support so that they can provide assistance.

Update: A hotfix for this issue has been released. If you are blocked by this issue please call support and they should be able to get you unblocked.

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • Is it supported to install SCSM 2012 RTM as secondary server in SCSM 2012 Sp1 management group?

  • @Anton, you can try, but the install will reject the setup routine as it detects the DB is a later version.

    PSS have a fix which we are testing at the moment.

  • @Anton, yes for short term purposes.  We would recommend upgrading all the management servers to SP1 as soon as possible though.

  • If we want a secondary SCSM server on Windows 2012 and SQL 2012 there is no solution right now, since SCSM 2012 RTM can´t be installed on WIN2012/SQL2012?

    (if we don´t want to install it on WIN2008 and SQL 2008 and upgrade to 2012)

    I guess there will be a patch for this very soon?

  • This is catastrophic for those that already have SP1 fully into production and need to add another management server.

    A question I have asked on every post is WHAT IS THE IMPACT OF NOT DOING THIS?  Do the warnings we are getting warrant rebuilding the entire environment?

  • As a Workaround for Windows Server 2012 , I 've installed first the DW server  in Windows server 2012 and SQL 2012 and the Management Servers  RTM and then upgrade in SP1. After that you can register the DW in Management Server without issues!

  • Do you have any update about this? A lot of customers were waiting for a clean SP1 installation! And now we have this issue. Some days ago I cleaned the Operational Database but when I reinstalled the secondary MS the issue appeared again. The steps that I executed were:

    1. Uninstall Secondary Management Server

    2. Clean Object ( secondary Management Server)  from Operational DB  using PowerShell

    3. Executed the SQL  SP´s:




    4. Then I Check BaseManagedEntity to confirm no record about secondary

    5. Reinstalled Secondary but same issue appeared


  • We will provide an update on this probably next week.

  • Great!


  • Anybody with information on what problems you may have with this bug, I do see all the errors in the log, but are able to connect to secundary management servers.

  • There is a hotfix available. Please enter the hotfix name.

  • Any news on this issue, hotfix name/number,download link, we are facing this  problem and it's getting urgent because we are blocked for the moment.



  • Hi,

    regarding another support case we have open our understanding is that UR3 is delayed and all updates will be scheduled to be available with UR4. If you are facing this issue just open a case with Microsoft - they can provide you with the hotfix.


  • @Geert

  • What do I do now? I upgraded to R2 after installing a secondary and not applying the patch. The secondary was promoted just prior to R2 upgrade because the Primary also has the portal on it. My Primary R2 system has the warning throughout the OpsMgr logs.