In my case, a reboot of the DC in question fixed this for me.
This error occurred on our Main AD Server. The root cause was a faulty network card that had buffer problems. The card would not allow any IP configuration to be done. We re-booted the box and the network card worked again, as well as the AD replication. We also upgraded the NIC, since the box handles a lot of network traffic.
As per Microsoft: "This problem occurs when an Active Directory object that is currently being used is deleted from the Active Directory directory service. In this situation, the replication engine will try to delete the object later". See ME911015
for additional information about this event.
for information on how to fix this error.
As per Microsoft: "This problem can occur when an orphan object is present in the Active Directory. Objects can become orphaned after their parents are deleted and then removed from the Active Directory by the garbage collector.". A fix is available from Microsoft.
An attempt to force replication using the Replicate Now option in Active Directory Sites and Services leads to the error: The following error occurred during the attempt to synchronize the domain controllers: The replication operation encountered a database error. furthermore, an Active Directory database integrity check using the NTDSUtil.exe utility yields the following error message: The operation terminated with the following error: -528 (JET_errMissingLogFile, current log file missing) after 4.66 secs. additionally, an Active Directory database integrity check using the ESENTUtl.exe utility yields the following error message: The operation terminated with the following error: -1206 (JET_errDatabaseCorrupted, non database file or corrupted db) after 4.66 secs.
CAUSE: The domain controller's partition of the active Directory database is corrupt.
1. Boot into Safe Mode and select Directory Services Restore Mode (Windows 2000 domain controllers only)
2. Run NTDSUTIL.EXe
3. Select Files
4. At the File Maintenance prompt type Info to find out where the domain controller's Active Directory database partition is stored. The information would be similar to the following: Database: g:\winnt\ntds - 50MB
5. Type Integrity to run an integrity check. If the database if corrupt, the integrity check would fail with an error message. Make a not of the error message.
6. Type Repair to repair the NTDS.DIT database
7. Using Windows Explorer, delete or move the following NTDS log files from their \NTDS folder to another folder. - edb.log - edb0000#.log - res2.log - res1.log - edb.chk - temp.edb
8. Type Integrity to run the integrity check. make sure it completes successfully.