Event ID 1188 — Replication Changes
Applies To: Windows Server 2008 R2
.jpg)
The replication process in Active Directory Domain Services (AD DS) ensures that domain controllers are able to maintain a consistent and updated Active Directory database. Because the Active Directory database holds essential information about user, group, and computer accounts, as well as other resources and services and the network configuration, keeping this information consistent on all the domain controllers is important. Failure of the Active Directory replication process can result in the following problems:
- Failure of applications that rely on consistent Active Directory information to function properly
- Logon rejections
- Password change failures
- Network service failures
- Incorrect or outdated information retrieval
For more information, see How Active Directory Replication Topology Works (https://go.microsoft.com/fwlink/?LinkID=93526).
Event Details
| Product: | Windows Operating System |
| ID: | 1188 |
| Source: | Microsoft-Windows-ActiveDirectory_DomainService |
| Version: | 6.0 |
| Symbolic Name: | DIRLOG_DRA_DISPATCHER_VILLIAN |
| Message: | A thread in AD_TERM is waiting for the completion of a RPC made to the following directory service. Directory service: %1 Operation: %3 Thread ID: %2 Timeout period (minutes): %4 MC_CONCAT( ,AD_TERM) has attempted to cancel the call and recover this thread. User Action If this condition continues, restart the directory service. |
Resolve
Check the health of the replication partner
Perform the following procedure using the domain controller that is identified as the replication partner that is indicated as having failed in the event message text.
To perform this procedure, you must have membership in Domain Admins, or you must have been delegated the appropriate authority.
To check the health of the replication partner:
- Open a command prompt as an administrator. To open a command prompt as an administrator, click Start. In Start Search, type Command Prompt. At the top of the Start menu, right-click Command Prompt, and then click Run as administrator. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
- Run the command repadmin /showrepl. This command displays the status reports on all replication links for the domain controller. Active Directory replication is functioning properly on that domain controller if all status messages report that the last attempt was successful: If there are any indications of failure or error after the last attempted status report, restart the domain controller that is identified as the replica domain controller, and then perform this step again. If the replica domain controller appears to be healthy, restart the domain controller that reported Event ID 1188. If repadmin reports that replication was delayed for a normal reason, wait and try the repadmin command again in a few minutes.
Verify
Perform the following tasks using the domain controller from which you want to verify that Active Directory replication is functioning properly.
To perform this procedure, you must have membership in Domain Admins, or you must have been delegated the appropriate authority.
To verify that Active Directory replication is functioning properly:
- Open a command prompt as an administrator. To open a command prompt as an administrator, click Start. In Start Search, type Command Prompt. At the top of the Start menu, right-click Command Prompt, and then click Run as administrator. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
- Run the command repadmin /showrepl. This command displays the status reports on all replication links for the domain controller. Active Directory replication is functioning properly on this domain controller if all status messages report that the last replication attempt was successful.
If there are any indications of failure or error in the status report following the last replication attempt, Active Directory replication on the domain controller is not functioning properly. If the repadmin command reports that replication was delayed for a normal reason, wait and try repadmin again in a few minutes.