This Knowledge Base provides troubleshooting guidance for commonly encountered Windows Management Instrumentation (WMI) errors that may occur while adding a Windows monitor or collecting metrics using WMI mode in Applications Manager.

WMI errors can be caused by one or more of the following:

• RPC communication failures
• DCOM configuration issues
• Firewall or network restrictions
• DNS or hostname resolution failures
• Corrupted WMI repository
• Missing or invalid WMI namespaces
• Missing or unregistered WMI classes/providers
• Invalid WMI (WQL) queries
• Corrupted or disabled Windows performance counters
  
• Authentication issues with local WMI connections

The following sections group the errors based on their common causes and provide the appropriate troubleshooting reference for each category.

WMI/RPC Communication Errors

These errors indicate that Applications Manager was unable to communicate with the target Windows server using WMI. They are typically associated with RPC communication failures, DCOM configuration issues, firewall restrictions, or network connectivity problems.

Applicable Error Codes

• 0x800706BE — The remote procedure call failed

• 0x80010002 — Call was canceled by the message filter

Troubleshooting:

Refer to the WMI/RPC Communication Errors KB for detailed troubleshooting steps.

These errors occur when the required WMI class cannot be accessed, or the WMI query cannot be executed successfully. They are commonly caused by invalid WQL queries, missing or corrupted WMI classes, corrupted performance counters, or missing or improperly registered WMI providers.

Applicable Error Codes

• 0x80041017 — Invalid Query

• 0x80041010 — Invalid Class

Troubleshooting

Refer to the WMI Query and Class Validation Errors KB for detailed troubleshooting steps.

WMI Namespace and Provider Errors

There is a slight technical/grammatical mismatch because a namespace can be unavailable, while "not properly registered" is more directly applicable to providers.

Applicable Error Codes

• 0x8004100E — Invalid Namespace

Troubleshooting:

Refer to the WMI Namespace and Provider Errors KB for detailed troubleshooting steps.

WMI/DCOM Communication and Network Resolution Errors

These errors are generally related to DCOM communication failures, hostname resolution issues, DNS configuration problems, NAT configurations, or firewall restrictions that prevent successful WMI communication.

Applicable Error Codes

• 0x80070776 — The object exporter specified was not found

Troubleshooting:

Refer to the WMI/DCOM Communication and Network Resolution Errors KB for detailed troubleshooting steps.

Local Connection Authentication Errors

These errors occur when the configured hostname or IP address resolves to the Applications Manager server (localhost) instead of the intended remote Windows server. Since the connection is treated as a local WMI connection, the configured remote credentials cannot be used in the expected manner, which can cause the connection to fail.

Applicable Error Codes

• 0x80041064 — User credentials cannot be used for local connections.
  

Troubleshooting:

Refer to the Local Connection Authentication Errors KB for detailed troubleshooting steps.

---

Error Code not listed?

If the reported WMI error code is not covered in this article, collect the following information before contacting Applications Manager Support:

• Complete error message or screenshot
• Screenshot of the WBEMTEST connection result
• WQL query executed 
• Target server hostname and IP address
• Any firewall, DNS, or network-related observations

Providing these details will help the support team identify the cause of the issue more efficiently.

Microsoft References

The following Microsoft resources provide additional information about troubleshooting WMI-related issues:

• WMI mode isn't working 

• WMI Troubleshooting Guide

• WMI missing or failing Providers / Invalid WMI Class