Resolutions for the following issues are provided:


SQL clusters are not discovered

Issue symptoms

SQL clusters are not discovered.


Check the following if the KM is unable to discover your SQL cluster:

  1. The host is unreachable from the server running PATROL Agent (ping command)
  2. User credentials might be wrong -  use SQLCollector diagnostic tool  
  3. Make sure use are able to connect to the SQL cluster using MS SQL Management Studio

WMI errors

Issue symptoms

WMI errors are displayed.

Issue scope

Connection to remote computer fails


DCOM permission

Follow the given steps to verify the DCOM permission:

  1. Click Start > Run > enter Dcomcnfg
  2. In the Component Services window, in the left navigation tree, expand Component Services > Computers > My Computer
  3. Right click My Computer and select Properties
  4. Select the COM Security Tab
  5. In the Access Permissions dialog box, click Edit Limits, ensure that the Everyone user group has Local Access and Remote Access permission. Click Ok after verifying the permissions.
  6. In the Launch and Activation Permissions dialog box, click Edit Limits, ensure that the Everyone user group has Local Activation and Local Launch permission. Click Ok after verifying the permissions.

Permission for the user to the WMI namespace

  1. Click Start > Run > enter WMImgmt.msc
  2. In the WMImgmt window, in the left navigation tree, right-click WMI Control (Local) and select Properties
  3. In the WMI Control (Local) Properties dialog box, select the Security tab.
  4. Select Root and click Security button.
  5. Ensure that authenticated users have Execute MethodsProvider Right, and Enable Account rights.
  6. Ensure that the Administrators have all the permissions.

Verify WMI Impersonation Rights

  1. Click Start > Run > enter gpedit.msc, click OK.
  2. In the Local Group Policy Editor window, in the left navigation tree, under Local Computer Policy, expand Computer Configuration and then expand Windows Settings.
  3. Expand Security Settings, expand Local Policies, click User Rights Assignment.
  4. Verify that the SERVICE account is specifically granted Impersonate a client after authentication rights. 

error: Login failed

Issue symptom

The login is from an untrusted domain and cannot be used with Windows authentication.

Issue scope

This is an environmental issue.


It can be resolved at domain/Network/Active Directory level. Use the following workarounds to resolve it:

  • Specify Hostname field as or localhost instead of regular IP address.
  • Disable Loop Back Check feature in the registry:
    • Edit the registry using regedit. (Start > run > Regedit)
    • Browse: HKLM\System\CurrentControlSet\Control\LSA and add a DWORD value called DisableLoopbackCheck to it.
    • Set the value to 1
    • Restart the PATROL Agent

   By performing these registry changes, you can set Hostname field with regular IP address. 

Was this page helpful? Yes No Submitting... Thank you