WMI/RPC Communication Errors

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 target 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 timeout.

  • 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:

Quote
ping <TargetHost>
nslookup <TargetHost>

Ensure that:

  • The hostname resolves to the correct IP address.

  • The target server is reachable from the Applications Manager server.

  • 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)  firewall rules

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 → Verify DCOM Configuration.

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 to enable Windows Firewall Rules for RPC.

6. Restart the WMI Service

If the previous validations do not identify an issue, restart the WMI service on the target server and retry the operation.

Quote
net stop winmgmt /y
net start winmgmt

After restarting the service, retry adding the monitor or collecting data.

Info
Contact Support

If the issue persists after completing the above troubleshooting steps, collect the following information and contact Applications Manager Support:

  • Screenshots of the relevant troubleshooting steps and their results.

  • Screenshot of the WBEMTEST error message or result.

  • Test the WMI connection using both the target server's hostname and IP address, and note which succeeds.

  • If only one method succeeds, update the monitor using the Update Hostname/IP option and verify whether the issue is resolved.

  • Enable Print all logs by navigating to Settings → Logging. Perform a manual poll for the affected Windows monitor.

  • Generate a Support Information File (SIF) from Applications Manager after reproducing the issue and completing the manual poll.