WMI/RPC Communication Errors
Applicable WMI Error Codes
0x800706BE – The remote procedure call failed
0x80010002 – Call was canceled by the message filter
Overview
These errors occur when Applications Manager is unable to establish or maintain WMI/RPC communication with the target Windows server during monitor addition or data collection.
The issue is typically related to RPC communication, DCOM configuration, firewall restrictions, WMI service availability, or network connectivity between the Applications Manager server and the monitored Windows server.
Possible Causes
One or more of the following conditions may cause these errors:
The Remote Procedure Call (RPC) service is stopped or unresponsive.
The Windows Management Instrumentation (WMI) service is stopped or not functioning correctly.
DCOM is disabled or improperly configured.
Windows Firewall or a network firewall is blocking TCP Port 135 or the required RPC dynamic ports.
DNS or hostname resolution is incorrect.
Network connectivity issues exist between the Applications Manager server and the target server.
High CPU or memory utilization on the target server causes WMI/RPC requests to time out.
The WMI repository or Windows system components are corrupted.
Antivirus or endpoint security software is blocking WMI communication.
Resolution
Perform the following validation steps in the given order.
1. Verify Basic Network Connectivity
From the Applications Manager server, verify that the target Windows server is reachable and that hostname resolution works correctly.
Run the following commands:
ping <TargetHost>
nslookup <TargetHost>
Ensure that:
The target server responds to the ping request.
The hostname resolves to the correct IP address.
There are no DNS or network connectivity issues.
2. Verify WMI Connectivity
This step helps determine whether the issue is related to WMI, RPC, DCOM, firewall configuration, or user permissions.
Refer to: Verify WMI Connectivity KB.
3. Verify Required Windows Services
Ensure the following services are running on the target server:
Remote Procedure Call (RPC)
RPC Endpoint Mapper
Windows Management Instrumentation (WMI)
If any service is stopped, start the service and retry the operation.
4. Verify DCOM Configuration
Verify that DCOM is enabled and correctly configured on the target server.
Refer to: Authentication Failed or Access Denied KB → Checking DCOM and COM Settings on the Remote Server.
5. Verify Firewall Configuration
Ensure that Windows Firewall and any network firewalls allow WMI communication.
Verify that the following are accessible:
TCP Port 135 (RPC Endpoint Mapper)
RPC Dynamic Ports
Windows Management Instrumentation (WMI)
Refer to: The RPC Server Is Unavailable KB for the required firewall configuration.
6. Restart the WMI Service
If all previous validations are successful, restart the WMI service on the target server.
After restarting the service, retry monitor addition or data collection.
Contact Support
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.
New to ADSelfService Plus?
Related Articles
WMI Namespace and Provider Errors
Applicable WMI Error Codes 0x8004100E - Invalid Namespace Overview This error occurs when the specified WMI namespace is unavailable, corrupted, or when the required WMI provider is not properly registered during monitor addition or data collection. ...WMI Error Troubleshooting Guide
Overview 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 through WMI mode in Applications Manager. WMI ...WMI Query and Class Validation Errors
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, ...Unable to Retrieve Data Through WMI Mode
Overview This article provides troubleshooting steps to identify and resolve data collection failures for Windows monitors configured in WMI mode. If one or more metrics are not being collected, the steps in this article will help determine whether ...Configuring non-admin user account for WMI monitoring
By default, Windows allows only members of the Administrators or Domain Admin groups to read WMI class information. However, you can configure a regular user to access WMI information by performing the following steps on the server that needs to be ...