New SQL Management Pack Not Working

Question

My SCOM UR2 2019 is setup fine. I have installed SCOM a few times. But every time I have never about to get the new SQL (the one that is SQL version agnostic) Management Pack to work. It never discover any SQL DB or SQL services at all.

So I just installed the old SQL 2016 MP and the SQL 2016 Reporting Services MP. The old SQL MP works.

I wanted to give the new SQL MP a try. I read I have remove the old SQL MP. But the old SQL MP overrides the Default Management Pack. Meaning I have to delete the Default Management Pack before I can remove all the old SQL MP. I exported my Default Management Pack, thinking I am re-import that. I proceed to delete all old SQL MP. When I tried to import the Default Management Pack, it refuses to allow me to import because of dependency. Anyway I fixed this by finding the Default Management Pack in the SCOM 2019 Installer.

Import the new SQL MP successfully but after half a day, I still cannot discover any SQL servers or services. Why the new SQL MP doesn't work?

Answer 1

Hi anonymous userLim95131,

Did you go through Kevin's blog post about the transition from old SQL management packs to the new version-agnostic SQL management pack?
https://kevinholman.com/2019/06/12/how-to-transition-to-the-sql-version-agnostic-mp/

Also note the following:

The DEFAULT settings for discovery for this MP is to discover ALL SQL versions SQL 2012 and later. If you do not want DULPICATE discovery of ALL your SQL computers, engines, DB’s, etc…. There is a rule in the management pack that attempts to inspect to see of the older 2012-2016 Legacy MP’s exist in the management group, and if they do, it will try to set an override on the primary DB Engine discovery to not discover 2012-2016, so no duplicates would be discovered.

You could also consider clearing the cache of your SCOM management servers:
How and When to Clear the Cache

Also have you checked the Operations Manager event log on the SCOM management servers for any warnings/errors that could be related to the discoveries of the SQL servers?

----------

(If the reply was helpful please don't forget to upvote or accept as answer, thank you)

Best regards,
Leon

Answer 2

Hi Luke,

I will also encourage you to follow exactly the steps in the article of Kevin Holman (Leon provided a link). If the old MP is working, the new one will also work, I am sure of this.
Just check also the profiles if your are using a dedicated AD account for the monitoring.

Regards,
Stoyan

Answer 3

Have you ran Remove-SCOMDisabledClassInstance after old MPs cleanups ? Did you check under anything getting discovered for class Local Discovery Seed ( MSSQL on Windows: Discover Installation Source (seed)) which is targeted at Microsoft.Windows.Server.Computer ; this is the base class for all SQL discoveries in this MP.
If you have removed all older SQL MPs then you can disable MSSQL on Windows: Automatic setup of DB Engine discovery filter rule.

Answer 4

A new update, I rebooted the SQL server and surprisingly the readings started showing up.

Does that mean that all my SQL servers have to be rebooted? For all other Management Pack, I don't really have to reboot the server.

Answer 5

Hi anonymous userLim95131,

let me try to recap the whole thing, as I have the feeling I am missing something. Can you please confirm:

• You have imported the new SQL version agnostic MP in th eversion 7.0.24.0 and you have removed all the old version specific SQL management packs.
• You have run "SCOM-RemoveDisabledClassInstance", which should clean the objects discovered be the old management pack.
• You have cleared the cache on your SCOM management server(s)?
• You have properly configured either Health Service SID or a domain account on the monitored servers and in case of the domain account you have ensured the account is mapped to the related SQL RunAs profiles (important)?
• You have checked for related events (Warnings or Errors) on your management servers, under the Operation Manager event log?
• You have checked for alerts, generated by the SQL MP that related to discovery issues. Normally those have names like "MSSQL on Windows: Discovery failed" or "MSSQL: Discovery failed"?
• You have followed the SQL MP guide for all related and recommended configurations?

Can you please go over the list and see if this is the case.

Thanks and Regards,
Stoyan