Event or Error status | Event or error text | Implication |
AD Replication status 8606 | “Insufficient attributes were given to create an object. This object may not exist because it may have been deleted.” | Lingering objects are present on the source DC (destination DC is operating in Strict Replication Consistency mode) |
AD Replication status 8614 | The directory service cannot replicate with this server because the time since the last replication with this server has exceeded the tombstone lifetime. | Lingering objects likely exist in the environment |
AD Replication status 8240 | There is no such object on the server | Lingering object may exist on the source DC |
Directory Service event ID 1988 | Active Directory Domain Services Replication encountered the existence of objects in the following partition that have been deleted from the local domain controllers (DCs) Active Directory Domain Services database. | Lingering objects exist on the source DC specified in the event (Destination DC is running with Strict Replication Consistency) |
Directory Service eventID 1388 | This destination system received an update for an object that should have been present locally but was not. | Lingering objects were reanimated on the DC logging the event Destination DC is running with Loose Replication Consistency |
Directory Service event ID 2042 | It has been too long since this server last replicated with the named source server. | Lingering object may exist on the source DC |
Removal method | Object / Partition & and Removal Capabilities | Details |
Lingering Object Liquidator | Per-object and per-partition removal Leverages:
|
|
Repldiag /removelingeringobjects | Per-partition removal Leverages:
|
|
LDAP RemoveLingeringObjects rootDSE primative (most commonly executed using LDP.EXE or an LDIFDE import script) | Per-object removal |
|
Repadmin /removelingeringobjects | Per-partition removal Leverages:
|
|
More: | Lingering Object Liquidator automates the discovery and removal of lingering objects by using the DRSReplicaVerifyObjectsmethod used by repadmin /removelingeringobjects and repldiag combined with the removeLingeringObject rootDSE primitive used by LDP.EXE. Tool features include:
|
More: | The version of the tool is still in development and does not represent the finished product. In other words, expect crashes, quirks and everything else normally encountered with beta software. |
Note: | Lingering Object Liquidator discovery method
|
FQDN of RWDC | CNAME of RWDC | FQDN of DC to remove object from | DN of the object | Object GUID of the object | DN of the object’s partition |
sqlagent errorlog
and I get same error Windows NT group/user
'MicrosoftAccountMyEmail', error code 0x54b. ADMINRG-XXXXXXYYYYY
.XXXXXYYYYY
or MicrosoftAccountMyEmail It puked out error 3930 which I also couldn't manage to fix. @job_login
and @job_password
set to null could this be source of issue?