locked
SQL Server support for ServiceBus and Workflow Manager management packs RRS feed

  • Question

  • Hi all.

    We're facing an issue in monitoring ServiceBus and Workflow Manager running on 3 servers of a SharePoint 2013 SP1 farm on SQL Server 2014: all the necessary Management Packs have been correctly installed and all the necessary RunAs accounts have been created and distributed, but the databases used by ServiceBus as well as the ones used by Workflow Manager are always reported in "Critical" state; the error message in the SCOM Health Explorer states "There is no installed System Center Monitoring pack for SQL Server" and the link in the "Knowledge" tab of the Health Explorer point to the download page for the Microsoft System Center Management Pack for SQL Server, which targets SQL Server up to version 2012.
    Is it possible that the ServiceBus and Workflow Manager management packs do not work fine if the databases used by those two components are hosted in a SQL Server version higher than 2012?
    Thank you.

    Bye.


    Luigi Bruno
    MCP, MCTS, MOS, MTA

    Monday, June 4, 2018 2:07 PM

All replies

  • Hi!

    It appears it's not supported, at least according to Microsoft as it is not stated there as you also mentioned.

    You could try the following Management Pack:

    Microsoft System Center Management Pack for SQL Server 2014

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com  LinkedIn:   

    Sunday, June 17, 2018 12:16 AM
  • Could you provide us with screenshots of what you are talking about? State views, health explorer, alerts... whatever could help understand what it is, because I'm unable to find a monitor that fits with that description just using text search.
    Sunday, June 17, 2018 8:42 AM
  • Hi!

    It appears it's not supported, at least according to Microsoft as it is not stated there as you also mentioned.

    You could try the following Management Pack:

    Microsoft System Center Management Pack for SQL Server 2014

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com  LinkedIn:   

    Thanks Leon.
    We've installed several SQL Server Management Packs to be able to discover and monitor different SQL Server versions (including 2014 and higher), but the problem is still there: I presume that the Service Bus and Workflow Manager MPs cannot discover and monitor their respective databases if they're hosted in a SQL Server version higher than 2012.

    Bye.


    Luigi Bruno
    MCP, MCTS, MOS, MTA

    Sunday, June 17, 2018 6:04 PM
  • Could you provide us with screenshots of what you are talking about? State views, health explorer, alerts... whatever could help understand what it is, because I'm unable to find a monitor that fits with that description just using text search.

    We're receiving the same alert for each of the 3 DBs used by the Service Bus and the Workflow manager.
    As an example, here's the detail for the alert related to the management DB used by the Service Bus

    as well as the information reported by the SCOM health Explorer

    Also, here's the detail for the alert related to the management DB used by the Workflow Manager

    as well as the information reported by the SCOM health Explorer

    As you can see, no other information is discovered by SCOM.
    Thank you.

    Bye.


    Luigi Bruno
    MCP, MCTS, MOS, MTA

    Monday, June 18, 2018 9:03 AM
  • OK so the way this monitor works is pretty dumb : it checks if any instance of class Microsoft.SQLServer.DBEngine exists on the server (see here )

    Unfortunately, this class only contains SQL 2008/2008R2/2012 instances; SQL 2014 instances' class is Microsoft.SQLServer.2014.DBEngine which explains why you are getting this alert.

    I see 2 solutions to this issue : simply disable this monitor if you don't believe you need it, or disable it and then create your own that works the same way but takes into account every SQL version by adding multiple "Or" expressions in the ConditionDetection.



    • Edited by CyrAz Monday, June 18, 2018 9:07 PM
    Monday, June 18, 2018 9:06 PM
  • OK so the way this monitor works is pretty dumb : it checks if any instance of class Microsoft.SQLServer.DBEngine exists on the server (see here )

    Unfortunately, this class only contains SQL 2008/2008R2/2012 instances; SQL 2014 instances' class is Microsoft.SQLServer.2014.DBEngine which explains why you are getting this alert.

    I see 2 solutions to this issue : simply disable this monitor if you don't believe you need it, or disable it and then create your own that works the same way but takes into account every SQL version by adding multiple "Or" expressions in the ConditionDetection.



    Thanks CyrAz.

    We'll think about it and decide how to proceed.

    Bye.


    Luigi Bruno
    MCP, MCTS, MOS, MTA

    Saturday, June 30, 2018 5:22 PM