Microsoft KB Archive/314715

= XADM: Fixing an &quot;InetOrgPerson&quot; Collision with Mangled Attributes =

PSS ID Number: 314715

Article Last Modified on 6/17/2003

-

The information in this article applies to:


 * Microsoft Exchange 2000 Server

-



This article was previously published under Q314715





SYMPTOMS
When you install or upgrade an Exchange 2000 Server computer in a domain that contains multiple domain controllers, you may receive the following error message during the setup /forestprep process:

Setup failed while installing sub-component Microsoft Windows Active Directory schema update with error code 0xC1037AE6 (please consult the installation logs for a detailed description). You may cancel the installation or try the failed step again.

The Setup log may contain the following error message:

[14:07:16] ScRunLDIFScript (k:\admin\src\libs\exsetup\exmisc.cxx:1333)

Error code 0XC1037AE6 (31462): Extending the schema in the Active Directory failed. Please consult the error log LDIF.ERR in your TEMP directory.



CAUSE
This issue occurs because of an InetOrgPerson collision. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

314649 Windows Server 2003 ADPREP Command Causes Mangled Attributes in Windows 2000 Forests That Contain Exchange 2000 Servers



RESOLUTION
To resolve this issue:  Identify mangled names. Use Ldp.exe to locate attributes that are affected by object mangling:  Install Ldp.exe from the Support\Tools folder of the Microsoft Windows 2000 or Microsoft Windows Server 2003 media. Start Ldp.exe from a domain controller or member computer in the forest. On the Connection menu, click Connect. Leave the Server box blank, set port to 389, and then click OK. On the Connection menu, click Bind. Leave all of the boxes blank, and then click OK. Record the distinguished name path for the SchemaNamingContext attribute. For example, for a domain controller in the CORP.COMPANY.COM forest, the distinguished name path might be:

CN=Schema,CN=Configuration,DC=corp,DC=company,DC=com

</li> On the Browse menu, click Search.</li> Configure the Search dialog box as follows: <ul> Base DN: The distinguished name path for the schema naming context that is identified in step d</li> Filter: (ldapdisplayname=dup*)</li> Scope: Subtree</li></ul> </li> Mangled Secretary and LabeledURI attributes have LDAPDisplayName attributes that are similar to the following format:

lDAPDisplayName: DUP-labeledURI-9591bbd3-d2a6-4669-afda-48af7c35507d;

lDAPDisplayName: DUP-secretary-c5a1240d-70c0-455c-9906-a4070602f85f

If you discover mangled names, repair them.</li></ol> </li> Repair the mangled names. To repair the mangled names for Secretary and LabeledURI schema attributes: <ol style="list-style-type: lower-alpha;"> Download the Windows 2000 InetOrgPerson Kit. The following file is available for download from the Microsoft Download Center:

Download W2K_IOP_kit.exe now

For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:

119591 How to Obtain Microsoft Support Files from Online Services

Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help to prevent any unauthorized changes to the file.</li> Extract the self-extracting InetOrgPerson Kit, W2K_IOP_kit.exe, to a new folder.</li> Enable changes to the schema. To do so, follow the steps in the following article in the Microsoft Knowledge Base:

261231 XADM: Unable to Update the Schema on the Schema Owner

</li> Run the InetOrgPerson-Fix.ldf file. From the console of the schema operations master roles (also known as flexible single master operations or FSMO), use the LDIFDE command to remove the duplicated LdapDisplayName attribute

LDIFDE -i -f inetOrgPerson-Fix.ldf -c DC=X

NOTE: that following the -c parameter there are two values: &quot;DC=X&quot; and &quot; &quot;, where this second value is the dn path for the root domain in the forest. This defines a &quot;find and replace&quot; operation on the contents of the LDF file -- replacing DC=X.

TIP: Use steps 1c and 1d in step 1 (which identifies mangled names) to obtain the value for the forest root domain by reading the value for the rootDomainNamingContext attribute.</li> Disable changes to the schema, again according to the Q-Article Q261231 in step c.</li></ol> </li></ol>

<div class="moreinformation_section">

MORE INFORMATION
You can copy the following text &quot;as is&quot; into an .ldf file, XSchemaFix.ldf, and then substitute that XSchemaFix.ldf file for the .ldf file in the InetOrgPerson Kit that is described in the &quot;Resolution&quot; section of this article. The content is the same:

<pre class="fixed_text"># Update the LDN of InetOrgPerson schema objects to RFC compliance.

dn: CN=secretary,CN=Schema,CN=Configuration,DC=X changetype: Modify replace: lDAPDisplayName LDAPDisplayName: secretary -

dn: CN=labeledURI,CN=Schema,CN=Configuration,DC=X changetype: Modify replace: lDAPDisplayName lDAPDisplayName: labeledURI -

dn: CN=ms-Exch-Assistant-Name,CN=Schema,CN=Configuration,DC=X changetype: Modify replace: lDAPDisplayName lDAPDisplayName: msExchAssistantName -

dn: CN=ms-Exch-LabeledURI,CN=Schema,CN=Configuration,DC=X changetype: Modify replace: lDAPDisplayName lDAPDisplayName: msExchLabeledURI -

dn: changetype: Modify add: schemaUpdateNow schemaUpdateNow: 1 -

Additional query words: DC exch2kp2w DN

Keywords: kberrmsg kbprb KB314715

Technology: kbExchange2000Search kbExchange2000Serv kbExchange2000ServSearch kbExchangeSearch

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© 2004 Microsoft Corporation. All rights reserved.