Discovery Tool - Invalid Query when scanning for Tomcat instances

[Dan Ebenal]

Using Assets Discovery Tool version 7.0.4.0 on Windows.

I have multiple tomcat instances installed under E:\sw, so I have updated the default Windows_Application_Tomcat.pat pattern to use my root directory instead of the C:\program~1 default

string[] appFolders = { @"E:\sw" };

Setting this allows the tool to locate my tomcat installations:

8/9/2024 1:47:34 PM: [Debug] Adding command dir E:\sw\tomcat*.exe /s/b result to cache was successful 

8/9/2024 1:47:34 PM: [Debug] Command: dir E:\sw\tomcat*.exe /s/b 

8/9/2024 1:47:34 PM: [Debug] Result:

 E:\sw\tomcats\bin\tomcats.exe

 E:\sw\tomcats\bin\tomcats_01w.exe 

 E:\sw\tomcats\bin\tomcats_02w.exe 

The issue is that none of the version checking commands are working

8/9/2024 1:50:50 PM: [Debug] Command: "E:\sw\tomcats\bin\version.bat" | findstr "server number" 

8/9/2024 1:50:50 PM: [Debug] Result: 

8/9/2024 1:50:50 PM: [Debug] Start getting command result from cache 

8/9/2024 1:50:50 PM: [Debug] Getting command result from cache was successful

8/9/2024 1:50:58 PM: [Debug] Command: "type "E:\sw\tomcats\RELEASE-NOTES" | findstr /i /c:"tomcat version"" 

8/9/2024 1:50:58 PM: [Debug] Result: 

8/9/2024 1:50:58 PM: [Debug] Start getting command result from cache 

8/9/2024 1:50:58 PM: [Debug] Getting command result from cache was successful

Running these commands directly on the server return appropriate results.

I am also seeing significant numbers of Management error .... Invalid query in the log

8/9/2024 1:50:58 PM: [Error] Management error: 

8/9/2024 1:50:58 PM: [Normal] Exceptions: 

8/9/2024 1:50:58 PM: [Normal] Invalid query 
   at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode) 
   at System.Management.ManagementObjectCollection.ManagementObjectEnumerator.MoveNext() 
   at ProviderClasses.ScanProviders.WMI.WMIQueryScanProcess.HandleManagementObjectCollection(ManagementObjectCollection managementObjectCollection) 
   at ProviderClasses.ScanProviders.WMI.WMIQueryScanProcess.ExecuteWMIQuery(String command, String wmiNamespace, Boolean useCache)

Are these errors expected or indicative of some WMI issue on the server (or something else)?