Wondering how to resolve Event ID 1388 or 1988? We can help you.

At Bobcares, we offer solutions for every query, big and small, as a part of our Server Management Service.

Let’s take a look at how our Support Team is ready to help customers to resolve Event ID 1388 or 1988 error.

How to resolve Event ID 1388 or 1988?

Usually, if a destination domain controller logs Event ID 1388 or Event ID 1988, a lingering object has detect and one of two conditions exists on the destination domain controller:

Event ID 1388: Inbound replication of the lingering object has occurred on the destination domain controller.
Event ID 1988: Inbound replication of the directory partition of the lingering object has block on the destination domain controller.

An object that is permanently delete from AD DS remains on a disconnect domain controller.

The domain controller failed to receive direct or transitive replication of the object deletion because it was disconnected from the replication topology for a period that exceeded a tombstone lifetime.

Then the domain controller is now reconnect to the topology and that object has update on the domain controller, causing a replication notification to the replication partner that an update is ready for replication.

The replication partner respond according to its replication consistency setting.

This notification applies to attempted replication of a writable object.

A copy of the writable lingering object might also exist on a global catalog server.

Today, let us see the troubleshooting steps followed by our Support Techs to resolve it:

If replication of a lingering object is detect, you can remove the object from AD DS, along with any read-only replicas of the object, by identifying the domain controllers that might store this object and running a repadmin command to remove lingering objects on these servers.

To remove lingering objects, do the following:

1. Firstly, use the event text to identify the following:

• The directory partition of the object
• Then, the source domain controller that attempted replication of the lingering object

2. Then, use Repadmin to identify the GUID of an authoritative domain controller.

3. Next, use Repadmin to remove lingering objects.

4. Then, enable strict replication consistency, if necessary.

5. Finally, ensure that strict replication consistency is enable for newly promoted domain controllers, if necessary.

[Looking for a solution to another query? We are just a click away.]

Conclusion

To conclude, our skilled Support Engineers at Bobcares demonstrated how to resolve Event ID 1388 or 1988 error.