1. Support
  2. KBAs
  3. Troubleshooting Access Is Denied

Troubleshooting Access Is Denied

The following article describes how to troubleshoot ‘Access is Denied’ error messages in Goverlan.

Information:

Local administrative privileges are not required on a remote machine in order to query information. However, many features require local administrative privileges for them to be successful. If Goverlan receives an ‘Access Is Denied’ while executing an action, it automatically prompts for alternate credentials. Please note: If you are getting an Access Denied when attempting to perform a Goverlan action against the machine that has the Goverlan console installed, you must right-click the Goverlan icon, then click Run As Administrator.
This article applies to those cases in which Goverlan keeps asking for alternate credentials and regardless of what you specify, you are not authorized to execute the action.

The name ‘MachineA’ will be used to define the remote machine in the following tests.

Check 1 – Administrative Share Access

From Windows on your machine, select Start >> Run and type \\MachineA\C$. Then press enter. If Windows prompts you for credentials, enter an account which has local administrative privileges on the remote machine.

If you can open the C$ share properly, go to Check 2.
If Windows keeps prompting you for credentials and regardless of what you specify they are rejected, verify that the entered credentials do indeed have local administrative privileges on the remote machine. Go to MachineA, open the local Administrators group and validate its content.
If Windows prompts you for credentials but the Username field is grayed out and set to Guest, then MachineA may have improper local security policies for remote administration.
Review the following article to resolve this problem: Required Windows XP Local Policy Settings for Remote Administration

Check 2 – Registry Access

From Windows on your machine, select Start >> Run and type Regedit then press enter.
From the Registry Editor, select File >> Connect Network Registry, and enter MachineA in the Enter the object name to select field.

If the registry database of MachineA doesn’t open, check that you are using an account which has local administrative privileges on MachineA. Also check that the Remote Registry Service is started and set to Automatic on MachineA.
If the registry database of MachineA is opened, check that you can read the following registry location on MachineA: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion
If you do not have access to this key, check that the NTFS permission on the ROOT HKLM key and subkeys are correct.

Check 3 – WMI Access

If you open the Goverlan System Information window of MachineA and you are prompted repeatedly for alternate credentials, it may be due to WMI Security restrictions.
Cancel the credentials prompt and look at the System Information Screen.

If all of the information is populated except for the Computer Identity section, it is a good indication that this is a WMI Security related issue. This is most common on Windows 2003 Servers since the Remote Administration through WMI policy is disabled by default.

To configure WMI Security, refer to the following articles:
Configuring WMI Security
How to troubleshoot WMI-related issues in Windows XP SP2
How to Set WMI Namespace Security in Windows Server 2003
If you need further assistance, please contact our Support Team.

Was this article helpful?

Related Articles