Applicable Error Code

1. 0x80041064 – User credentials cannot be used for local connections.
   

Overview

This article provides troubleshooting steps for WMI Error 0x80041064, which may occur when:

• Adding a Windows Monitor
• Collecting data through WMI mode

Root Cause:
Applications Manager collects monitoring credentials for the target Windows server. However, if the configured hostname or IP address resolves to the Applications Manager server itself (localhost), WMI treats the connection as local. Since Windows does not use explicit credentials for local WMI connections, Applications Manager cannot pass the configured username and password, causing the connection to fail with Error 0x80041064.

Possible Causes

This error occurs when the hostname or IP address configured for the Windows monitor unexpectedly resolves to the Applications Manager server (localhost) instead of the intended remote Windows server.

Common reasons include:

• ❌ Incorrect DNS resolution
• ❌ Incorrect entries in the local hosts file
• ❌ The hostname resolves to 127.0.0.1 or the local machine
• ❌ The configured IP address belongs to the Applications Manager server instead of the target server
  

Troubleshooting Steps

Step 1: Verify Hostname Resolution

Perform this step from: Applications Manager Server

Verify that the configured hostname resolves to the correct remote server.

Execute:

ping <hostname>

OR

nslookup <hostname>

✅ Ensure the resolved IP address belongs to the target Windows server and not the Applications Manager server.

Step 2: Verify the Configured IP Address

Perform this step from: Applications Manager Server

If the monitor is configured using an IP address, verify it belongs to the target Windows server.

Ensure the configured IP is NOT:

• 127.0.0.1
• localhost
• The IP address assigned to the Applications Manager server
  

Step 3: Check the Hosts File

Perform this step from: Applications Manager Server

Open the hosts file:

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

Verify there are no incorrect entries mapping the target hostname to:

• localhost
• 127.0.0.1
• The Applications Manager server's IP address

⚠️ Action Required: Remove any incorrect entries and retry the connection.

Step 4: Verify WMI Connectivity

Perform this step from: Applications Manager Server 

Use WBEMTEST to verify that the configured hostname or IP address connects to the intended remote server.

For detailed instructions on using the WBEMTEST tool, refer to the "Verify WMI Connectivity Using WBEMTEST" section in the corresponding knowledge base article.

⚠️ If WBEMTEST connects to the local machine instead of the remote server, verify the hostname resolution before proceeding.

Resolution

1. ✅ Verify that the configured hostname resolves to the intended remote Windows server and not to the Applications Manager server (localhost).
2. ✅ Retry the WMI connectivity test to confirm that the remote connection is established successfully.
3. ✅ If the configured hostname or IP address is incorrect, update it using the Update IP/Hostname option for the Windows monitor in Applications Manager.