Add missing Classes to WMI Namespace

StatelyElf 21 Reputation points
2020-11-27T12:36:42.587+00:00

Hello

I had the following Error in my SCOM Dashboard:

----------
Exception: ----------
Exception Type: System.Exception
Message: Unable to execute query 'SELECT ServiceName, PropertyName, PropertyNumValue, PropertyStrValue FROM SqlServiceAdvancedProperty WHERE (PropertyName = 'ISWOW64' OR PropertyName = 'LANGUAGE' OR PropertyName = 'INSTANCEID' OR PropertyName = 'SPLEVEL' OR PropertyName = 'INSTALLPATH' OR PropertyName = 'ERRORREPORTING') AND SqlServiceType = 1' for the path '\xxx.xxx.xx\root\Microsoft\SqlServer\ComputerManagement13'. 32 bit: False. Error code: -2147217392. Error message: Invalid class

So I checked the WMI on the Server and saw that the class is missing. There are 17 missing classes in the \xxx.xxxx.xxh\root\Microsoft\SqlServer\ComputerManagement13 Namespace:
43079-sc.png
There schould be 85 objects.....
43239-sc2.png

I checked the WMI with the command winmgmt /verifyrepository but i got the result "WMI repository is consistent"

Does anybody know how I can add the missing classes to the WMI Namespace?

Operations Manager
Operations Manager
A family of System Center products that provide infrastructure monitoring, help ensure the predictable performance and availability of vital applications, and offer comprehensive monitoring for datacenters and cloud, both private and public.
1,417 questions
Windows Server Management
Windows Server Management
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Management: The act or process of organizing, handling, directing or controlling something.
421 questions
0 comments No comments
{count} votes

Accepted answer
  1. CyrAz 5,181 Reputation points
    2020-11-27T15:42:50.23+00:00

    WMI can be quite tricky, but in that specific case I believe the best resolution would be to reimport the SQL .mof files :
    mofcomp "%programfiles(x86)%\Microsoft SQL Server\number\Shared\sqlmgmproviderxpsp2up.mof"

    I would also strongly advise you to take a backup or a snapshot if you can, I've already seen WMI manipulations doing more damage than good...

    0 comments No comments

0 additional answers

Sort by: Most helpful