Microsoft KB Archive/245658

= The Replication Management Agent Genlog File Logs an "Error 14105" Message =

Article ID: 245658

Article Last Modified on 10/30/2006

-

APPLIES TO


 * Microsoft Metadirectory Services 2.1
 * Microsoft Metadirectory Services 2.2 Service Pack 1
 * Microsoft Metadirectory Services 2.2 Service Pack 1

-



This article was previously published under Q245658



SYMPTOMS
When you run the replication management agent, the following error messages may be logged in the replica server's Genlog files:

ERR_00 0a10 02/01/22 09:35:28.324 (DB5_writeRecord) Failed to write index record, error:14105 DN:[cn=Jeff Smith,ou=PSS,dc=Microsoft,dc=com]

-and-

ERR_00 0a10 02/01/22 09:35:28.324 (SYN_syncOneRecord) [28257]-Error 14105 updating [cn=Jeff Smith,ou=PSS,dc=Microsoft,dc=com]



CAUSE
This behavior may occur if a duplicate Simple Mail Transfer Protocol (SMTP) address is present. In Microsoft Metadirectory Services (MMS), the value of the SMTP mail address of each record must be unique throughout the metaverse. The replication logs report the error messages that are described in the preceding section if the replication management agent is attempting to add records that contain a mail attribute value that is already present in the metaverse. This behavior may occur in the following scenario:
 * 1) An existing metaverse record contains a valid SMTP mail address attribute value, for example, cn=Jeff Smith.
 * 2) The source metaverse has been previously synchronized with the replica metaverse with respect to the metaverse object cn=Jeff Smith.
 * 3) In the source metaverse, cn=Jeff Smith is moved up the tree so that the location of the new cn=Jeff Smith object is processed before the location of the old cn=Jeff Smith object when the replication management agent runs.

After the replication management agent scans the source metaverse, it processes each object in sequence. The management agent moves from the root of the replica subtree to each leaf. The replica server sees an add request for the new cn=Jeff Smith object before the required delete request for the old cn=Jeff Smith object. Because the SMTP mail address is the same for both records, the replication management agent cannot add the second instance of the cn=Jeff Smith object until the SMTP mail value in the original cn=Jeff Smith object is removed.



WORKAROUND
To work around this behavior, run the replication management agent a second time. The first time that the replication management agent runs, the original cn=Jeff Smith object is removed. The second time that the replication management agent runs, the new object is inserted in the correct location. Run the replication management agent twice in quick succession. If there is a delay, the object may be relocated a second time in the source metaverse.



STATUS
This behavior is by design.

Keywords: kberrmsg kbprb KB245658

-

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

© Microsoft Corporation. All rights reserved.