Applicable WMI Error Codes

• 0x80041017 - Invalid Query
• 0x80041010 - Invalid Class

Overview

This error occurs when the WMI query executed during monitor addition or data collection is invalid, references unavailable WMI classes or performance counters, or when the WMI repository/performance counter data is corrupted.

Common Causes

• Invalid or unsupported WQL query / class.
• Missing or corrupted WMI performance counter classes.
• Corrupted WMI repository.
• Damaged or missing Windows performance counters.
• WMI provider registration issues.
• Corrupted PerfMon counter libraries.
• Invalid property referenced in the WMI query.

Resolution Steps

1. Validate the WMI Query Using WBEMTEST

1. Get the query by referring to the following KB: Namespace & WMI Class

2. Try running the query directly in the wbemtest tool on the Applications Manager server by connecting to the remote server.

3. Refer to the steps under the section "Checking connectivity with WMI Tester" for instructions on using the wbemtest tool.

Note: If the query execution fails, the required WMI class is either unavailable, corrupted, or not properly registered.

2. Rebuild Windows Performance Counters

Corrupted Windows performance counters can commonly trigger this error for PerfMon-related WMI classes.

Run the following command from an elevated command prompt:

lodctr /r

After rebuilding the counters, restart the server.

3. Re-build WMI Repository

Refer to the KB for detailed steps about WMI Reconstruction.

4. Verify Firewall Configuration

Ensure the following are allowed through Windows Firewall and network firewall:

• TCP Port 135 (RPC Endpoint Mapper)
• WMI service communication
• Dynamic RPC Ports

Enable the predefined firewall rules mentioned in the "The RPC server is unavailable" KB.

5. Restart the WMI Service

Run the following commands on the target server:

net stop winmgmt /y

net start winmgmt

Contact Support

When contacting support, provide the following:

• Screenshots of all the troubleshooting steps performed and their results.
• Screenshot of the WBEMTEST error message or result.
• Validate the WMI connection using both the hostname and IP address of the target server, and identify which one succeeds in your environment.
• If only one method succeeds, update the monitor using the Update Hostname/IP option and verify whether the issue is resolved.
• Enable Print all log by navigating to Settings → Logging. Perform a manual poll for the affected Windows monitor.
• Generate a Support Information File from Applications Manager after the manual poll.