Article ID: 328661 - View products that this article applies to.
This article was previously published under Q328661
This article has been archived. It is offered "as is" and will no longer be updated.
When you try to install Exchange 2000 Server by using the /forestprep switch, Setup may not work. The Exchange Server Setup Progress.log file may contain the following entry:
The Ldif.err file may contain the following entry:
Error code 0XC1037AE6 (31462): Extending the schema in the Active Directory failed. Please consult the following error log: %s\LDIF.ERR.
Add error on line XXX: Unwilling To Perform The server side error is "Schema update failed: duplicate LDAP display name." An error has occurred in the program.
This issue may be caused if a labeledURI schema object with an lDAPDisplayName of labeledURI already exists in the Active Directory. The labeledURI object may have been created by a third-party program such as the Cisco Systems "Cisco Call Manager" program.
To resolve this issue, use the Microsoft Windows 2000 inetOrgPerson Kit to modify the schema:
Download and Extract the Windows 2000 inetOrgPerson Kit
Determine the rootDomainNamingContext ValueYou can use the Lightweight Directory Protocol (LDP) utility to help determine the rootDomainNamingContext for your domain. The rootDomainNamingContext is required to update the schema. To determine the rootDomainNamingContext:
Modify the Exchange.ldf FileThe Exchange.ldf file is included with the Windows 2000 inetOrgPerson Kit. This file provides a method for modifying the ldapDisplayName value. To modify the Exchange.ldf file:
Copy the Exchange.ldf File to the Schema OwnerAfter you modify the Exchange.ldf file, you must copy it to the domain controller schema owner. To determine which domain controller is the schema owner and copy the file:
Update the Schema By Using LDIFDELDIFDE is a utility in Windows 2000 to support batch-update operations to the Active Directory based on the LDIF file format standard. To use LDIFDE to update the Active Directory:
For additional information about how to modify this registry key, click the following article number to view the article in the Microsoft Knowledge Base:
Schema update is not allowed on this DC. Either the registry key is not set or the DC is not the schema FSMO role owner.
(http://support.microsoft.com/kb/285172/ )Schema update require Write Access to schema in Active Directory
TroubleshootingWhen using LDIFDE, you may receive one of the following error messages:
An attempt was made to add an object to the directory with a name that is already in use.
If this occurs, note the value that produced the error message, and then follow these steps:
The specified value already exists.
To resolve this issue:
Entry DN: CN=Mail-Recipient,CN=Schema,CN=Configuration,DC=cpn,DC=net change: modify
Attribute 0) mayContain:secretary Add error on line 2628: No Such Attribute The server side error is "The parameter is incorrect." An error has occurred in the program
For additional information about related topics, click the following article numbers to view the articles in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/312371/ )HOW TO: Prepare the forest by using ForestPrep in Exchange 2000
312407The third-party products that are discussed in this article are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.
(http://support.microsoft.com/kb/312407/ )Requirements for preparing Windows domains for Exchange Server 2003 or for Exchange 2000 Server
Contact us for more help
Connect with Answer Desk for expert help.