"Authentication Failed or Access denied" message is shown, when trying to add the Server Monitor through WMI mode.

"Authentication Failed or Access denied" message is shown, when trying to add the Server Monitor through WMI mode.

Overview

This article provides troubleshooting steps for Authentication Failed, Access Denied, and related WMI authentication errors encountered while adding a Windows Server Monitor or during data collection through WMI mode in Applications Manager.
These errors are commonly caused by:
  • Incorrect credentials
  • Improper username format
  • Insufficient user privileges
  • DCOM or WMI permission issues
  • Firewall restrictions
  • WMI connectivity failures

Applicable WMI Error Codes

  • 0x80070005 — Access is denied (Access denied by DCOM security)
  • 0x80041003 — Access denied (Access denied by a provider)

Where to Perform These Steps

⚠️ CRITICAL: Each troubleshooting step must be performed on the correct server as indicated:
    • Applications Manager Server: Steps performed while configuring monitors or testing connectivity
    • Remote Windows Server: Steps performed on the server being monitored or to be monitored to verify configurations
      Each step below clearly indicates where it should be performed. Pay close attention to these indicators to avoid configuration errors.

Troubleshooting Steps

Step 1: Verify the Username Format

📍 Perform on: Applications Manager Server (while configuring or editing the Windows monitor credentials)

      Ensure that the monitoring credentials are specified in the correct format.

      Domain Environment

            If the target server is joined to a domain, specify the username in the following format:

      DOMAIN\Username

            Example:

      CORP\Administrator

            Where:

      • CORP is the domain name
      • Administrator is the username

      Workgroup Environment

          If the target server is part of a workgroup, specify the username in the following format:

      MachineName\Username

          Example:

      WIN-SERVER-01\Administrator
NotesNote: MachineName refers to the computer name of the target Windows server.

To identify the domain or computer name: Navigate to: Control Panel → User Accounts → User Accounts

Step 2: Verify Required Windows Services

📍 Perform on: Remote Windows Server (the server being monitored or to be monitored)

      Ensure that the following services are running on the target server.      

InfoRecommendation: Configure their Startup Type as Automatic.

    • Remote Procedure Call (RPC)
    • Remote Procedure Call (RPC) Locator
    • Windows Management Instrumentation (WMI)
    • COM+ Event System
    • Remote Access Auto Connection Manager
    • Remote Access Connection Manager
    • Remote Registry
    • Server
    • Windows Management Instrumentation Driver Extensions
    • WMI Performance Adapter
    • Workstation

Step 3: Verify Firewall Configuration

📍 Perform on: Remote Windows Server

      Open an elevated Command Prompt on the target server and execute the following commands:

netsh advfirewall firewall set rule group="Windows Remote Management" new enable=yes

netsh advfirewall firewall set rule group="Windows Management Instrumentation (WMI)" new enable=yes

netsh advfirewall firewall set rule group="Remote Administration" new enable=yes
      If the following message is displayed:
No rules match the specified criteria
      Execute:
netsh firewall set service remoteadmin enable
      After executing the above command, re-execute the Remote Administration command and try the WMI connectivity test.

Step 4: Verify WMI Connectivity Using WBEMTEST

📍 Perform on: Applications Manager Server

This verifies that the Applications Manager server can establish a remote WMI connection to the target server.

    1. Open WBEMTEST
    2. Click Connect
    3. Enter the namespace:
      \\hostname\root\cimv2
    4. Enter the monitoring credentials
    5. Click Connect
      If the connection fails using the hostname:
    • Retry using: \\ipaddress\root\cimv2
      If the connection succeeds only with the IP address:
    • Verify DNS resolution
    • Remove incorrect entries from: C:\Windows\System32\drivers\etc\hosts
    • Retry using the hostname

Error-Specific Guidance

      Error Code: 0x80070005 (Access denied by DCOM security)

      Error Code: 0x80041003 (Access denied by a provider)

Step 5: Verify DCOM Configuration

    1. Open: dcomcnfg
    2. Navigate to: Component Services → Computers
    3. Right-click My Computer and select Properties

      Default Properties

            Verify that:
      • ✓ Enable Distributed COM on this computer is enabled
      • ✓ Default Authentication Level is set to Connect
      • ✓ Default Impersonation Level is set to Impersonate or Identify

      COM Security

      Under Access Permissions → Edit Limits:
            Verify that the monitoring user (or its group) has:
      • ✓ Local Access
      • ✓ Remote Access
      Under Launch and Activation Permissions → Edit Limits:
            Verify that the monitoring user (or its group) has:
      • ✓ Local Launch
      • ✓ Remote Launch
      • ✓ Local Activation
      • ✓ Remote Activation

Step 6: Verify WMI Permissions

    1. Open: wmimgmt.msc
    2. Navigate to: WMI Control → Properties → Security
    3. Click Security
    4. Click Advanced
    5. Select the monitoring user (or its group). Add it if it does not exist.
    6. Click Edit
            Configure:
      • Type: Allow
      • Applies to: This namespace and subnamespaces
            Verify that the following permissions are enabled:
      • ✓ Execute Methods
      • ✓ Enable Account
      • ✓ Remote Enable
      • ✓ Read Security

Step 7: Verify User Rights Assignment

    1. Open: gpedit.msc
    2. Navigate to:
      Computer Configuration → Windows Settings → Security Settings → Local Policies → User Rights Assignment
    3. Open: Impersonate a client after authentication
    4. Add the monitoring user if it is not already listed
    5. Apply the changes and retry monitoring

Important Note

Recommendation: For Windows monitoring through WMI mode, it is recommended to use an account with local Administrator privileges.

Non-Administrator Accounts: If using a non-administrator account, ensure that all the required DCOM permissions, WMI namespace permissions, and User Rights Assignment settings are configured correctly. Refer to the following KB articles for detailed configuration steps: