MORE INFORMATION
The following events may be logged if immediate replication is triggered (for example, by an urgent replication for a user lockout condition) and collides with the local Active Directory update:
Event Type: Warning
Event Source: NTDS Replication
Event Category: Replication
Event ID: 1083
Description:
Replication warning: The directory is busy. It couldn't update object CN=... with changes made by directory GUID._msdcs.domain. Will try again later.
This indicates that the unsuccessful attempt of the remotely triggered update that will be retried later:
Event Type: Warning
Event Source: NTDS Replication
Event Category: Replication
Event ID: 1061
Description:
Internal error: The directory replication agent (DRA) call returned error 8438.
(decimal 8438 / hex 0x20f6 : ERROR_DS_DRA_BUSY, winerror.h)
If advanced NTDS logging is enabled, the following error ID may also be logged:
Event Type: Warning
Event Source: NTDS General
Event Category: Internal Processing
Event ID: 1173
Description:
Internal event: Exception e0010004 has occurred with parameters -1102 and 0 (Internal ID 2030537).
(JetDataBase ID -1102: JET_errWriteConflict -1102, Write lock failed due to outstanding write lock)
If NTDS logging is set to 4 (Verbose) or higher in the Replication Events entry of the
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NTDS\Diagnostics\ subkey, the following error ID may also be logged:
Event Type: Warning
Event Source: NTDS Replication Event
Event Category: Replication
Event ID: 1413
Description:
The following object changes were not applied to the local Active Directory database because the local metadata for the object indicates that the change is redundant.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
285858
Error message: The replication system encountered an internal error
If the remotely triggered update wins against the local update, the following system event may be logged for a user account lockout:
Event Type: Error
Event Source: SAM
Event Category: None
Event ID: 12294
User: user-SID
Description:
The SAM database was unable to lockout the account of user due to a resource error, such as a hard disk write failure (the specific error code is in the error data) . Accounts are locked after a certain number of bad passwords are provided so please consider resetting the password of the account mentioned above.
Data: 0000: c00002a5
You must analyze the error data to receive the correct error condition. DWord data hexadecimal 0xc00002a5 = decimal -1073741147: STATUS_DS_BUSY, ntstatus.h).
After the warnings, an NTDS information event is logged that reports that the queued update has already been made (with the same version ID) and is be ignored as redundant:
Event Type: Information
Event Source: NTDS Replication
Event Category: Replication
Event ID: 1413
Description:
Property 90296 (lockoutTime) of object CN=username,OU=... is not being applied to the local database because its local metadata implies the change is redundant. The local version is (version-ID).
When this condition exists, no replication error has occurred. Active Directory is consistent and you can safely ignore the resulting event logs.