Article ID: 924255 - Last Review: October 25, 2007 - Revision: 1.3 How to troubleshoot access denied in a split permission model or minimum permissions modelSYMPTOMSWhen the administrative snap-in that you are using reports
an "Access denied" error code, customers frequently wonder what attributes they
do not have permission to. This happens most frequently for user accounts that
were delegated and have a limited set of permissions to change an OU or a
domain but the delegated user is not a member of "Account Operators" or "Domain
Admins." The "Access Denied" error code 0x80007005 is actually a win32 interpretation of the LDAP error code. To determine the LDAP error code and the attribute for which you do not have access to, you can follow the steps that are mentioned in the Resolution section. RESOLUTIONTo resolve this issue, enable auditing for Failure on the
object that you are trying to change. Then, you try to make the change to this
object. You can also look for Event 566 about the object in the Security log on
the DC, this should tell you the exact permissions that you are
lacking. After you configure an audit policy setting, you can configure auditing for specific objects, such as users, computers, organizational units, or groups, by specifying both the kinds of access and the users whose access that you want to audit. To configure auditing for specific Active Directory objects:
| Article Translations
|
Back to the top
