SQL Server MP 6.7.15: MSSQL Monitoring Failed errors

• Question

• 

  

  0

  Sign in to vote

  We upgraded to 6.7.15 SQL MP, and then a whole bunch of servers started complaining, most with these kind of errors

  Date and Time: 2/14/2017 10:36:03 AM Log Name: Operations Manager Source: Health Service Script Event Number: 4001 Level: 1 Logging Computer: XXXX.corp User: N/A

  Description: Management Group: Hatch. Script: Main Module: CPUUsagePercentDataSource.ps1 Version: 6.7.15.0 : Error occured during CPU Usage for SQL Instances data source executing. Computer:XXX  Reason: Invalid class -------- Invalid class -------- Invalid class

  Event Data:

  < DataItem type =" System.XmlData " time =" 2017-02-15T01:36:03.1028149+10:00 " sourceHealthServiceId =" A6400850-75D1-2E24-8942-9E3B49F6A8B0 " >

  < EventData >

    < Data > Management Group: Hatch. Script: Main Module: CPUUsagePercentDataSource.ps1 Version: 6.7.15.0 </ Data >

    < Data > Error occured during CPU Usage for SQL Instances data source executing. Computer:XXX  Reason: Invalid class -------- Invalid class -------- Invalid class </ Data >

    </ EventData >

   </DataItem>

  OR

  Event Data:

  < DataItem type =" System.XmlData " time =" 2017-02-14T10:41:01.3496372-05:00 " sourceHealthServiceId =" 56014E42-8129-A032-D6F3-032661EBC3A0 " >

  < EventData >

    < Data > Management Group: Hatch. Script: Main Module: CPUUsagePercentDataSource.ps1 Version: 6.7.15.0 </ Data >

    < Data > Error occured during CPU Usage for SQL Instances data source executing. Computer:YYY  Reason: Unable to get counter "\Process(sqlservr*)\ID Process": The specified object was not found on the computer. output: Unable to get counter "\Process(sqlservr*)\ID Process": The specified object was not found on the computer. -------- The specified object was not found on the computer. </ Data >

    </ EventData >

    </ DataItem >

  The knowledge base indicates most likely a permissions issue to SQL, but the SCOM service account has local admin and sysadmin to SQL..

  I've seen previous post on an older MP (6.4) having this issue, but now we get it with the newest SQL MP

  Please help, thanks in advance

  Tuesday, February 14, 2017 3:43 PM