Microsoft KB Archive/927056

From BetaArchive Wiki
Knowledge Base

You discover a duplicate "lDAPDisplayName" attribute conflict after you modify the Active Directory schema in Windows 2000 Server

Article ID: 927056

Article Last Modified on 12/1/2006


  • Microsoft Windows 2000 Server


Consider the following scenario. In between two replication cycles, you modify the Active Directory® directory service schema. Then, you discover a duplicate lDAPDisplayName attribute conflict on a replication partner computer that is running Microsoft Windows 2000 Server. In this scenario, an event that resembles the following may be logged in the Directory Services log: Event ID: 1572
Category: Internal Processing
Source: NTDS
General Type: Information
Generated: <date and time>
Written: <date and time>
Machine: <computer name>
Message: Inbound replication has detected a duplicate ldapDisplayName conflict between the objects <CN=ms-Exch-LabeledURI,CN=Schema,CN=Configuration,DC=Organization_Name,DC=com> and <CN=labeledURI,CN=Schema,CN=Configuration,DC=Organization_Name,DC=com>. The conflict has been resolved by changing the ldapDisplayName of <CN=labeledURI,CN=Schema,CN=Configuration,DC=Organization_Name,DC=com> to <DUP-labeledURI-321dadb5-fa5b-42b5-8e8f-7907dbf68e09>.


This problem occurs if the following conditions are true:

  • You modify the schema. These modifications include reusing a specific lDAPDisplayName attribute.
  • The schema modifications occur between replication cycles.

When a partner domain controller receives the schema update that includes the lDAPDisplayName attribute, a specific check is performed to validate that the attribute is unique. This check is based on the recently replicated lDAPDisplayName attribute. This check is also based on the local schema cache content. Because the schema cache on the partner domain controller is updated every 5 minutes, the replicated lDAPDisplayName attribute already exists in the cache. This leads to the conflict that is described in the "Symptoms" section.


In order to resolve this problem, force a replication of the schema naming context from the schema master to all the domain controllers that are in the forest. Make sure that you do this before you reuse a specific lDAPDisplayName attribute.

Keywords: kbschema kbactivedirectoryrepl kbactivedirectory kbexpertiseadvanced kbtshoot kbprb kbldap KB927056