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
Related Articles
Failed to enumerate domains for windows browser device discovery: The list of servers for this workgroup is not currently … 19Number of Views Windows OS coverage and VDA requirements in Microsoft 365 17Number of Views ndtrack.exe process may crash gathering info report for Oracle FMW inventory if an WMI query returns Invalid class (0x8004… 4Number of Views Command 'Config.ps1 "Config\FNMS Windows Authentication Config.xml"' fails after "Executing step Create Reporter registry"… 9Number of Views SVM Windows OS Scanning Benchmarks 6Number of Views
Hi, I am Reva - Ask me anything.
No new updates
Thanks for the feedback!
Your feedback has been saved.Rate this response:
Add Additional feedback ( Optional )
Are you sure you want to cancel
the case creation?
Are you sure you want to cancel the case creation?
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
Case id: 00001065
Activity: Status change: 2 hours ago