ndtrack failed to compress inventory

[anzevuij]

Hi,

We're on the process of upgrading our deployed Inventory Agent from v15 to v21 (2020 R1 to 2023 R2). A first test on one VM isn't successful with a problem related to WMI.  A .ndi file is generated, but the compressed version is not so no inventory is uploaded to the beacon.

Here is the tracker.log (french OS) :

[06.05.2024 09:18:01 (G, 0)] {1312} ************************************************************
[06.05.2024 09:18:01 (G, 0)] {1312} Program arguments are 'C:\Program Files (x86)\ManageSoft\Tracker\ndtrack.exe -o InventoryType=Machine -o UserInteractionLevel=Quiet'
[06.05.2024 09:18:01 (G, 0)] {1312} Preferences loaded
[06.05.2024 09:18:01 (G, 0)] {1312} Inventory Setting file is 'C:\ProgramData\ManageSoft Corp\ManageSoft\Tracker\InventorySettings\InventorySettings.xml'
[06.05.2024 09:18:01 (G, 0)] {1312} Obtaining semaphore lock (to ensure only one instance is running)...
[06.05.2024 09:18:01 (G, 0)] {1312} Obtained semaphore lock.
[06.05.2024 09:18:01 (G, 0)] {1312} Program version is 'FlexNet Manager Platform 21.0'
[06.05.2024 09:18:01 (G, 0)] {1312} Program path is 'C:\Program Files (x86)\ManageSoft\Tracker'
[06.05.2024 09:18:01 (G, 0)] {1312} Program build number is '8.506'
[06.05.2024 09:18:01 (G, 0)] {1312} Program user is 'système'
[06.05.2024 09:18:01 (G, 0)] {1312} Inventory tracking started
[06.05.2024 09:18:01 (U, 0)] {1312} QUERY: Gathering inventory
......
[06.05.2024 09:19:07 (G, 0)] {1312} Generating a full inventory
[06.05.2024 09:19:07 (G, 0)] {1312} Started compressing inventory
[06.05.2024 09:19:07 (U, 0)] {1312} ERROR: Error (s189m262)
[06.05.2024 09:19:07 (U, 0)] {1312} ----------------
[06.05.2024 09:19:07 (U, 0)] {1312} Failed to get WMI property 'Name': Non trouvé (0x80041002)
Failed to get WMI property 'Name': Non trouvé (0x80041002)
Failed to get WMI property 'Name': Non trouvé (0x80041002)
Failed to get WMI property 'Name': Non trouvé (0x80041002)
Failed to get WMI property 'Name': Non trouvé (0x80041002)
Failed to get WMI property 'Name': Non trouvé (0x80041002)
Failed to get WMI property 'Name': Non trouvé (0x80041002)
Failed to get WMI property 'Name': Non trouvé (0x80041002)
Failed to get WMI property 'Name': Non trouvé (0x80041002)
Failed to get WMI property 'Name': Non trouvé (0x80041002)
Failed to get WMI property 'Name': Non trouvé (0x80041002)
Failed to get WMI property 'Name': Non trouvé (0x80041002)
Failed to get WMI property 'Caption': Non trouvé (0x80041002)
Failed to connect to the WMI provider namespace 'root\virtualization\v2' on server 'localhost': Espace de noms non valide (0x8004100e)
Failed to initialize WMI (0x8004100e)
The specified WMI namespace is invalid or does not exist on the host
Failed to connect to the WMI provider namespace 'root\virtualization' on server 'localhost': Espace de noms non valide (0x8004100e)
Failed to initialize WMI (0x8004100e)
The specified WMI namespace is invalid or does not exist on the host
Failed to connect to the WMI provider namespace 'root\MicrosoftSqlServer' on server 'localhost': Espace de noms non valide (0x8004100e)
Failed to initialize WMI (0x8004100e)
The specified WMI namespace is invalid or does not exist on the host
Failed to connect to the WMI provider namespace 'root\Microsoft\SqlServer' on server 'localhost': Espace de noms non valide (0x8004100e)
Failed to initialize WMI (0x8004100e)
The specified WMI namespace is invalid or does not exist on the host
Failed to connect to the WMI provider namespace 'root\Microsoft\SqlServer\ReportServer' on server 'localhost': Espace de noms non valide (0x8004100e)
Failed to initialize WMI (0x8004100e)
The specified WMI namespace is invalid or does not exist on the host
FlexNet Manager Platform could not compress the inventory.

[06.05.2024 09:19:07 (G, 0)] {1312} Program exited with code -524484346
[06.05.2024 09:19:07 (G, 0)] {1312} ************************************************************

I checked the WMI console of the machine and the problem namspaces are indeed missing: where is the agent look to enumerate the available namespaces ?

[ChrisG]

The main error here is this line of logging:

FlexNet Manager Platform could not compress the inventory.

Unfortunately there is no further logging to give insight into what is causing the inventory compression to fail.

Is it possible any disks on the computer are running low on space?

Could you share screenshots showing what agent configuration settings are specified under the following registry keys?

• HKLM\SOFTWARE\WOW6432Node\ManageSoft Corp\ManageSoft\Tracker\CurrentVersion
• HLKM\SOFTWARE\WOW6432Node\ManageSoft Corp\ManageSoft\Common

NB. I expect the WMI errors appearing in the log here are a red herring. They are likely appearing in the log as an indirect consequence of whatever problem is occurring, and don't indicate anything about the cause of the problem itself.

[anzevuij]

Thanks for your answer ChrisG.
Here are the requested screenshots :

Don't hesitate to tell me if you need further information.
There is more than 20 GB of free space on the disks. I tried to uninstall and reinstall the agent (and verified that the registry is cleaned), but that didn't fixed the issue.

Thanks

[anzevuij]

Ok I know how to reproduce the issue.
I installed the 2023 R2 agent on another device (pc). The 1st inventory ran well. Then, I modified the settings to import some path of the registry (as described here). The next inventory failed with the same WMI and compression errors in the logs. Unfortunately, removing this option don't fix the problem. I realize now that I set this setting on the VM I was talking about on the 1st post and since then, the agent won't compress the inventory anymore, event after a clean reinstall..  any thoughts ?

[ChrisG]

That's interesting. I would be surprised if configuring the IncludeRegistryKey agent preference would be related to this, but maybe the issue is intermittent or only visible the 2nd & subsequent times that inventory is gathered.

I wonder whether the OS language may be related... Are both of the computers you have seen this on running a French OS? Have you seen the issue on any computers running an English OS?