locked
ServiceBus and Workflow Manager Management Packs report databases in unhealthy status 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.
    This is the scenario:

    • ServiceBus and Workflow Manager running on two application servers and one web front end server of the SharePoint farm
    • Management Packs installed: Service Bus Management Pack version 1.0.0.26, Workflow Manager Management Pack 1.0.2015.0, SQL Server 2012 Management Packs 7.0.2.0, SQL Server 2014 Management Packs 7.0.2.0
    • Workflow Manager 1.0, Workflow Manager Client 1.0, Workflow Manager CU KB3104066 installed on the three aforementioned servers
    • RunAs accounts created, configured and distributed as per Management Packs guides
    • All the PowerShell cmdlets for ServiceBus and Workflow farm report good status
      Get-WFFarm OK
      Get-WFFarmStatus OK
      Get-SBFarm OK
      Get-SBFarmStatus OK
    • Microsoft Monitoring Agent running under the SYSTEM account on each monitored server.
    • All the hosts for the Service Bus and the Workflow Manager are discovered and listed by the SCOM console, all of them having "Healthy" status


    There are many error records in the "Operations Manager" log of the Windows Event Viewer like the followings

    Management Group: (omissis for privacy). Script: Main : Error occured during Windows Service Bus discovery.
    Computer:(application server or web front end server)
    Reason: The EXECUTE permission was denied on the object 'GetClusters', database 'PRD_SbManagementDB', schema 'Store'.

    Management Group: (omissis for privacy). Script: Main : Error occured during Windows Workflow discovery.
    Computer:(application server or web front end server)
    Reason: The EXECUTE permission was denied on the object 'GetClusters', database 'PRD_WFManagementDB', schema 'Store'.

    Similar errors are recorded into the "Admin" log of both the "Microsoft-ServiceBus" and "Microsoft-Workflow" groups in the Windows Event Viewer of each server which is part of the ServiceBus and Wowkflo Manager farm.
    Which could be the reason for all these errors and for the Service Bus databases and Workflow Manager databases always displayed in critical state, like there is not Monitoring/Management Pack for SQL server installed? What to check?
    Thank you.

    Bye.


    Luigi Bruno
    MCP, MCTS, MOS, MTA

    Tuesday, April 17, 2018 7:58 AM

All replies

  • Hello,

    Since the errors are related to permissions, the obvious question would be "does the RunAs accounts you're using have the sufficient permission on the databases?"

    You can refer this blog if you want to get rid of RunAs accounts for SQL completely:

    SQL MP Run As Accounts – NO LONGER REQUIRED

    Hope this helps

    Cheers


    Sam (Please take a moment to "Vote as Helpful" and/or "Mark as Answer" wherever applicable. Thanks!)

    Tuesday, April 17, 2018 8:36 AM
  • Hello,

    Since the errors are related to permissions, the obvious question would be "does the RunAs accounts you're using have the sufficient permission on the databases?"

    You can refer this blog if you want to get rid of RunAs accounts for SQL completely:

    SQL MP Run As Accounts – NO LONGER REQUIRED

    Hope this helps

    Cheers


    Sam (Please take a moment to "Vote as Helpful" and/or "Mark as Answer" wherever applicable. Thanks!)

    Thanks for replying, Sameer.

    Yes, the RunAs accounts used to discover ServiceBus and Workflow Manager have enough permissions on the ServiceBus and Workflow Manager databases.
    Do you think it could be anything related to the RunAs accounts used by the SQL Server Management Packs?
    Thank you.

    Bye.


    Luigi Bruno
    MCP, MCTS, MOS, MTA

    Tuesday, April 17, 2018 9:19 AM
  • Hi Luigi,

    >>Do you think it could be anything related to the RunAs accounts used by the SQL Server Management Packs?<<

    Yes, this is the RunAs account that I was referring to :) This is different than the account you use to discover the agents. the Local System account that you run the SCOM agent under does not have enough permissions on the database, so you need a RunAs account to perform such workflows. Please refer to this on setting up RunAs accounts for SQL MP:

    SQL Run As Account Configuration for SCOM Made Easy

    Hope this helps
    Cheers


    Sam (Please take a moment to "Vote as Helpful" and/or "Mark as Answer" wherever applicable. Thanks!)

    Tuesday, April 17, 2018 10:52 AM
  • Hi Luigi,

    >>Do you think it could be anything related to the RunAs accounts used by the SQL Server Management Packs?<<

    Yes, this is the RunAs account that I was referring to :) This is different than the account you use to discover the agents. the Local System account that you run the SCOM agent under does not have enough permissions on the database, so you need a RunAs account to perform such workflows. Please refer to this on setting up RunAs accounts for SQL MP:

    SQL Run As Account Configuration for SCOM Made Easy

    Hope this helps
    Cheers


    Sam (Please take a moment to "Vote as Helpful" and/or "Mark as Answer" wherever applicable. Thanks!)

    All the RunAs accounts have the proper permissions.
    I'm not sure, but I suspect that this could be due to the SQL Server version: all the databases used by the ServiceBus and the Workflow Manager are hosted on a SQL Server 2014 machine; this machine is listed in both the "Microsoft -> SQL Server -> SQL Server 2005/2008/2012 -> Database Engines -> Database engines" and "Microsoft -> SQL Server 2014 -> Database Engines -> Database engines" nodes in the Monitoring pane of the System Center Operations Manager console. In the first node, the server is reported as "Not monitored", in the second one it is reported as "Healthy" (but I think it is monitored only from a SQL Server perspective, thus all the databases are healthy).
    Is it possible that the Management Packs for ServiceBus and Workflow Manager cannot discover those databases if they're hosted in SQL Server 2014 rather than in SQL Server 2012?
    Thank you.

    Bye.


    Luigi Bruno
    MCP, MCTS, MOS, MTA

    Monday, June 4, 2018 1:47 PM