Fixing SCOM 2019 discovery and unhealthy state errors

• webrunner

  SSC-Dedicated

  Points: 31863

  More actions

  January 31, 2022 at 9:14 pm

  #3979340

  Hello experts,

  We are using SCOM 2019 along with SQL Server management packs. I'm trying to resolve error alerts like these:

  Information : SCOM Alert: : MSSQL on Windows: Discovery error

  Warning : SCOM Alert: : MSSQL on Windows: DB Engine is in unhealthy state

  I know that certain permissions are required in order for SCOM to discover a SQL instance, but I don't know where to look to see which account is trying to do the discovery. Is it the account listed in the "Last modified by:" part of the alert email?

  And in terms of the "DB Engine is in unhealthy state" where are the criteria for that alert? In other words, how can I find out what SCOM is seeing as unhealthy with the DB Engine?

  Thanks for any help.

  -- webrunner

   

  -------------------
  A SQL query walks into a bar and sees two tables. He walks up to them and asks, "Can I join you?"
  Ref.: http://tkyte.blogspot.com/2009/02/sql-joke.html

• Jo Pattyn

  SSC-Dedicated

  Points: 32347

  More actions

  February 1, 2022 at 9:48 am

  #3979488

  I'm also using SCOM 2019 and run into discovery problems. Usually when the DB is disabled.

  Haven't the time for a full discussion but this may be a start.

  https://docs.microsoft.com/en-us/troubleshoot/system-center/scom/troubleshoot-sql-database-discovery

  The required permissions are also mentioned in the readme of the sql server management pack.

  The "local alert collection rule" is still troublesome

• February 1, 2022 at 12:30 pm

  This was removed by the editor as SPAM