Applicable WMI Error Codes

• 0x80070776 — The object exporter specified was not found.

Overview

This error occurs when AppManager is unable to establish WMI/DCOM communication with the target Windows server during monitor addition or data collection. It is commonly caused by RPC/DCOM communication failures, DNS resolution issues, NAT environments, firewall restrictions, or network connectivity problems.

Common Causes.

• RPC/DCOM communication failure.
  

• DNS resolution issues between the AppManager server and the target server.
  

• WMI communication blocked by NAT or firewall configuration.
  

• Windows Firewall or network firewall blocking WMI/DCOM traffic.

• Required RPC dynamic ports are blocked.

• DCOM service communication failure.

• Windows Management Instrumentation (WMI) service is unresponsive.

• The target hostname cannot be resolved from the AppManager server.

• Antivirus or security software blocking WMI/DCOM communication.

• Network instability between the AppManager server and the target server.
  

Resolution Steps

1. Verify WMI Connectivity

For detailed instructions, Refer to the steps under the section "Verify WMI Connectivity Using WBEMTEST" for instructions on using the WBEMTEST tool.

2. Verify Required Windows Services

Ensure that the following Windows services are running on the target server:

• Remote Procedure Call (RPC)

• RPC Endpoint Mapper

• DCOM Server Process Launcher

• Windows Management Instrumentation (WMI)

Restart any stopped services before proceeding with further troubleshooting.

3. Validate NAT and DNS Configuration

This issue is commonly observed when the target server is located behind a NAT firewall or when DNS resolution is not configured correctly.

Verify that the target server's hostname resolves correctly from the AppManager server.

If necessary, add an entry for the target server in the hosts file on the AppManager server:

C:\Windows\System32\drivers\etc\hosts

After updating the hosts file, retry the WMI connectivity test using the hostname instead of the IP address.

4. Verify DCOM Configuration

Verify the DCOM configuration on the target server by following the steps under "Verify DCOM Configuration" in the Authentication Failed or Access Denied KB article.

5. Verify Firewall Configuration

Ensure that Windows Firewall and any network firewall allow the following:

• TCP Port 135 (RPC Endpoint Mapper)

• WMI service communication

• Dynamic RPC Ports

Refer to: The RPC Server Is Unavailable KB to enable Windows Firewall Rules for RPC.

6. Restart the WMI Service

Restart the Windows Management Instrumentation (WMI) service on the target server by executing the following commands from an elevated Command Prompt:

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.