Run ESXQuery standalone with logging for VMware inventory

Use ESXQuery.exe to run VMware inventory outside of a Beacon and capture detailed logs for troubleshooting. This is helpful when you want to diagnose connectivity, credential, or SDK-related issues without relying on a Beacon.

Instructions

1. Verify prerequisites

Make sure your environment meets the following requirements:

A Windows host with network access to vCenter or ESXi targets over TCP 443.
ESXQuery binaries downloaded from the knowledge base: VMware stand-alone inventory agent esxquery.exe for FlexNet Manager Suite and Flexera One ITAM
Access to the VMware SDK endpoint

To confirm SDK access, open the following URL in a browser:
https://<vcenter>:443/sdk/vimService.wsdl

If the WSDL page or login prompt opens, the SDK is reachable.

2. Create the trace configuration file

Create a file named etdp.trace and place it in the same directory as ESXQuery.exe (or in the working directory).

Example:

# Output trace to C:\ManageSoft.log

filename = C:\ManageSoft.log

# Enable VMware-related trace classes

+GSoap

+GSoap/WinHTTP

+Inventory/VMware

+Inventory/VMware/SDK

+Inventory/VMware/SDK/Detail

+Inventory/VMware/SDK/Logic

+Error

3. Prepare Credentials

Provide ESXQuery with the vCenter details and enter your credentials when prompted:

esxquery.exe -s <server name>

4. Run ESXQuery

Enter ESXQuery.exe -a in the command line.

This command generates:

Inventory files (NDI) for discovered VMware objects
A detailed trace log at:
C:\ManageSoft.log

Log Output

The log file includes:

Connection attempts to vCenter or ESXi SDK endpoints
SOAP request and response details for VMware inventory calls
WinHTTP error codes (for example, 12002 timeout and 12175 TLS issues)
Diagnostic messages for credential or proxy-related issues

Troubleshooting common issues

Decryption errors
These occur when you use encrypted credentials from another host. Re-enter credentials or recreate the configuration file.

Proxy interference
Check netsh winhttp show proxy and disable SSL inspection if needed.

SDK connectivity issues
Recheck the WSDL URL to confirm it’s accessible before running ESXQuery.

Upload inventory results

If you generated NDI files outside a Beacon, you can:

Copy them to a Beacon’s Incoming\Inventories folder for processing
Upload them directly, depending on your environment configuration

Outcome

After completing these steps, ESXQuery runs independently and produces detailed diagnostic logs. You can use these logs to identify and troubleshoot VMware inventory issues without relying on a Beacon.

Was this helpful?

Support Hub

Product

Flexera One

Solution Area

IT Asset Management