XADM: Error Message: The Active Directory Connector Snap-in Failed to Initialize (286802)
The information in this article applies to:
- Microsoft Exchange 2000 Server
This article was previously published under Q286802 SYMPTOMS
When you log on to an Exchange Server computer using a domain administrator account, and you attempt to start the Active Directory Connector Management tool, you may receive the following error message:
The Active Directory Connector snap-in failed to initialize. The Default Active Directory Connector Policy object could not be located in the Active Directory. Please ensure that the directory object has not been deleted and that sufficient permissions have been granted to your account.
ID no: c103aa81
Microsoft Active Directory Connector Management.
CAUSE
This behavior can occur if you removed the Allow Read permission for the Authenticated Users group from the Configuration container of Active Directory.
RESOLUTIONWARNING: If you use the ADSI Edit snap-in, the LDP utility, or any other LDAP version 3 client, and you incorrectly modify the attributes of Active Directory objects, you can cause serious problems. These problems may require you to reinstall Microsoft Windows 2000 Server, Microsoft Exchange 2000 Server, or both. Microsoft cannot guarantee that problems that occur if you incorrectly modify Active Directory object attributes can be solved. Modify these attributes at your own risk.
To resolve this behavior, start the ADSI Edit utility from the Microsoft Windows 2000 Support Tools installation to grant the Authenticated Users group Read permissions on the Configuration container. You can also install Windows 2000 Support Tools by using the Windows 2000 CD-ROM. To do so, locate the Support/Tools folder on the Windows 2000 CD-ROM.
STATUSThis behavior is by design.MORE INFORMATION
By default, domain administrators in any domain are able to start the Active Directory Connector Management tool. Other permissions modifications to portions of Active Directory also may cause the error listed in the "Symptoms" section. However, the most common cause is the removal of the Read permission on the Configuration container.
| Modification Type: | Minor | Last Reviewed: | 4/25/2005 |
|---|
| Keywords: | kberrmsg kbprb KB286802 |
|---|
|