Share via

Resolving "Access Denied" Errors

  • Article

Published : September 27, 2005

"Access Denied" errors that occur while DPM is performing a task that involves communication with a protected file server often indicate a configuration problem on the file server. If you experience an "Access Denied" error in a task that involves communication with the file servers, do the following:

  • Verify that the system time on the DPM server and the file server is synchronized with the system time on the domain controller.

  • On a file server running Windows Server 2003 SP1, verify that the DPM server is a member of the Distributed COM Users group and that the group has Distributed COM (DCOM) Launch and Access permissions for the file server.

To verify group membership on the file server:

  1. In Computer Management, expand System Tools, expand Local Users and Groups, and then click Groups.

  2. In the Details pane, double-click the Distributed COM Users group.

  3. Verify that the computer account for the DPM server is a member of the group.

To verify DCOM Launch and Access permission on the file server:

  1. In Administrative Tools, open Component Services.

  2. Expand Component Services, expand Computers, right-click My Computer, and then click Properties.

  3. On the COM Security tab, under Access Permissions, click Edit Limits.

  4. Verify that the Distributed COM Users group is allowed both Local Access and Remote Access permissions.

  5. On the COM Security tab, under Launch and Activation Permissions, click Edit Limits.

  6. Verify that the Distributed COM Users groups is allowed the following permissions:

    • Local Launch

    • Remote Launch

    • Local Activation

    • Remote Activation