cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Symptoms:

In FNMS you will see duplicate records for the device. Where the duplicate device have missing Hardware information, this is due to an issue with the WMI classes in the device. The agent couldn't run its query to get the WMI classes.

Diagnosis:

  • Check if the duplicate device has hardware information
  • Open the NDI file using any text-editor and look for Win32_classes if they exist.
  • Next step is to enable tracing for ndtrack
    a) On the server, browse to C:\Program Files (x86)\ManageSoft
    b) Make backup of etcp.trace file
    c) Move/Copy the etcp.trace file provided in the attachments. (I pre-enabled tracing)
    d) Manually run ndtrack, on a cmd prompt as admin -
    "C:\Program Files (x86)\ManageSoft\Tracker\ndtrack.exe -t Machine"
    e) After the inventory gathering, this should generate a trace file on the default file path: C:\
    d) Disable tracing by overwriting the provided etcp.trace file with your own.
  • Observe in the ManageSoft.log (Trace file) the following errors:

    2020-12-29 04:07:08.190Z, pid 3524, thread 3964 (Inventory/Tracker/Hardware): WMI config file: C:\Program Files (x86)\ManageSoft\Tracker\wmitrack.ini
    2020-12-29 04:07:08.190Z, pid 3524, thread 3964 (Inventory/Hardware/WMI/Query): Begin WMI class enumeration for 'Win32_ComputerSystem'
    2020-12-29 04:07:08.190Z, pid 3524, thread 3964 (Error/Catalog/Fetch): Message s4m4112 from process catalog: Invalid class
    2020-12-29 04:07:08.190Z, pid 3524, thread 3964 (Inventory/Hardware/WMI/Query): Failed to begin enumeration of the WMI class 'Win32_ComputerSystem': Invalid class (0x80041010)
    2020-12-29 04:07:08.205Z, pid 3524, thread 3964 (Error/Catalog/Fetch): Message s4m4112 from process catalog: Invalid class
    2020-12-29 04:07:08.205Z, pid 3524, thread 3964 (0,Error/Occurrence/Warning/371/2): Warning Occurrence (s371m2): Failed to enumerate the WMI class 'Win32_ComputerSystem': Invalid class (0x80041010)
    2020-12-29 04:07:08.205Z, pid 3524, thread 3964 (Inventory/Tracker/Hardware/WMI/Class): WMI class tracked: Win32_ComputerSystem

Solution:

This article to help further troubleshoot and fix the WMI class issue.

https://www.virtuallyboring.com/microsoft-wmi-invalid-class-error-0x80041010/

Also, you can also try using the WbemTest tool on the device to verify if they are able to query the WMI classes correctly -

https://docs.microsoft.com/en-us/mem/configmgr/develop/core/understand/introduction-to-wbemtest

Was this article helpful? Yes No
No ratings
Version history
Last update:
‎Jan 11, 2021 07:16 PM
Updated by: