This article describes symptoms, cause and resolution steps for cases where Active Directory operations fail with error 1818: The remote procedure call was cancelled.

This article is part of a series on troubleshooting Active Directory replication errors, and is also one of the errors reported by the Active Directory Replication Status Tool  (ADREPLSTATUS). If you encounter a new symptom, cause, or resolution for this error, we encourage you to add information about your experience in the appropriate section.


  1.  Possible formats for the error include: 

     Decimal   Hex   Symbolic   Error string 
     1818  0x71a    RPC_S_CALL_CANCELLED   The remote procedure call was cancelled. 

  2. The following events get logged


    Event ID  Event String  


     1232  Active Directory attempted to perform a remote procedure call (RPC) to the following server. The call timed out and was cancelled.
     1188 A thread in Active Directory is waiting for the completion of a RPC made to the following domain controller.

    Domain controller:


    get changes

    Thread ID:


    Timeout period (minutes):


    Active Directory has attempted to cancel the call and recover this thread.

    User Action

    If this condition continues, restart the domain controller.

    with error status 1818
    Internal event: Active Directory has encountered the following exception and associated parameters. Exception: e0010002 Parameter: 0 Additional Data Error value: 1818 Internal ID: 5000ede
    with error status 1818
    Internal event: Active Directory could not synchronize the following directory partition with the domain controller at the following network address.

    Directory partition: <NC>

    Network address: <GUID-based DC name>

    If this error continues, the Knowledge Consistency Checker (KCC) will reconfigure the replication links and bypass the domain controller.

    User Action

    Verify that the network address can be resolved with a DNS query.

    Additional Data Error value: 1818 The remote procedure call was cancelled.

     Repadmin /showreps displays  the following error message

    <Sitename>\<DCname> via RPC DC
    DC object GUID: b8b5a0e4-92d5-4a88-a601-61971d7033af Last attempt @ 2009-11-25 10:56:55 failed, result 1818 (0x71a): Can't retrieve message string 1818
    (0x71a), error 1815. 823 consecutive failure(s). Last success @ (never).

  3. Repadmin /showreps from Domain Controller Name shows that it is failing to pull Domain NC from <Sitename> but can pull all other NCs 

    <Sitename>\<DC name>
    DC Options: IS_GC
    DC object GUID: d46a672b-f6be-431e-81c6-23b1f284f8c9
    DC invocationID: 5d74f6b0-08f1-408a-b4d5-4759adafe219
    ==== INBOUND NEIGHBORS =====================================
    <Sitename>\<DCname> via RPC DC
    DC object GUID: b8b5a0e4-92d5-4a88-a601-61971d7033af
    Last attempt @ 2011-11-11 10:45:49 failed, result 1818 (0x71a):
    Can't retrieve message string 1818 (0x71a), error 1815. 123 consecutive
    failure(s). Last success @ (never).

  4. DCPromo may fail while promoting a new domain controller and you will see the following error on the DCPROMO GUI

    Active Directory Installation Wizard.

    The Operation Failed because:
    Active Directory could not replicate the directory partition
    CN=Configuration....from the remote domain controller “server name”
    The remote procedure call was cancelled

    The following entries will be logged in the DCPROMO logs:

    06/29/2010 22:31:36 [INFO] EVENTLOG (Informational): NTDS General / Service Control : 1004
    Active Directory Domain Services was shut down successfully.
    06/29/2010 22:31:38 [INFO] NtdsInstall for <FQDN for the domain> returned 1818
    06/29/2010 22:31:38 [INFO] DsRolepInstallDs returned 1818
    06/29/2010 22:31:38 [ERROR] Failed to install to Directory Service (1818)
    06/29/2010 22:31:38 [ERROR] DsRolepFinishSysVolPropagation (Abort Promote) failed with 8001
    06/29/2010 22:31:38 [INFO] Starting service NETLOGON
    06/29/2010 22:31:38 [INFO] Configuring service NETLOGON to 2 returned 0
    06/29/2010 22:31:38 [INFO] The attempted domain controller operation has completed
    06/29/2010 22:31:38 [INFO] DsRolepSetOperationDone returned 0

  5. While trying to re-host a partition on the Global catalog 

    repadmin /rehost fail with DsReplicaAdd failed with status
    1818 (0x71a)>
    DsReplicaAdd fails with status 1818 (0x71a)


 The issue occurs when the destination DC performing inbound replication does not receive replication changes within the number of seconds specified in the “RPC Replication Timeout” registry key. You might experience this issue most frequently in one of the following situations:

  • You prpromote a new domain controller into the forest by using the Active Directory Installation Wizard (Dcpromo.exe).
  • Existing domain controllers replicate from source domain controllers that are connected over slow network links.

The default value for the RPC Replication Timeout (mins) registry setting on Windows 2000-based computers is 45 minutes. The default value for the RPC Replication Timeout (mins) registry setting on Windows Server 2003-based computers is 5 minutes. When you upgrade the operating system from Windows 2000 to Windows Server 2003, the value for the RPC Replication Timeout (mins) registry setting is changed from 45 minutes to 5 minutes. If a destination domain controller that is performing RPC-based replication does not receive the requested replication package within the time that the RPC Replication Timeout (mins) registry setting specifies, the destination domain controller ends the RPC connection with the non-responsive source domain controller and logs a Warning event.

 Some specific root causes for Active Directory logging 1818 \ 0x71a \ RPC_S_CALL_CANCELLED include:

  1. An old Network Interface Card driver installed on Domain Controllers could cause failure of a few network features like Scalable Networking Pack (SNP)
  2. Low bandwidth or network packets drops between source and destination domain controllers.
  3. The networking device between source and destination device dropping packets.


Note: A speed and duplex mismatch between the NIC and switch on a domain controller could cause dropped frames, resets, duplicate acknowledgements, and retransmitted frames


  1. Increase replication time out adding the key RPC Replication Timeout (mins) on HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters
    1. Start Registry Editor.
    2. Locate the following registry subkey:  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters
    3. Right-click Parameters, point to New, and then click DWORD Value.
    4. Type RPC Replication Timeout (mins), and then press ENTER to name the new value. 
    5. Right-click RPC Replication Timeout (mins), and then click Modify. 
    6. In the Value data box, type the number of minutes that you want to use for the RPC timeout for Active Directory replication, and then click OK.

      On a Windows Server 2003-based computer that is part of a Windows 2000 environment or that was upgraded from Windows 2000 Server, you may want to set this value to 45 minutes. This is value may depend on your network configuration and should be adjusted accordingly.

      Note You must restart the computer to activate any changes that are made to RPC Replication Timeout (mins)

  2. Update the network adapter drivers

    To determine whether an updated network adapter driver is available, contact the network adapter manufacturer or the original equipment manager (OEM) for the computer. The driver must meet Network Driver Interface Specification (NDIS) 5.2 or a later version of this specification.

    To manually disable RSS and TCP Offload yourself, follow these steps: 
    1. Click Start, click Run, type regedit, and then click OLocate the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
    2. Right-click EnableTCPChimney, and then click Modify.
    3. In the Value data box, type 0, and then click OK.
    4. Right-click EnableRSS, and then click Modify.
    5. In the Value data box, type 0, and then click OK.
    6. Right-click EnableTCPA, and then click Modify.
    7. In the Value data box, type 0, and then click OK.
    8. Exit Registry Editor.;EN-US;948496

  3. Enable PMTU Black Hole Detection on the Windows-based hosts that will be communicating over a WAN connection. Follow these steps:
    1. Start Registry Editor (Regedit.exe).
    2. Locate the following key in the registry:  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\tcpip\parameters
    3. On the Edit menu, click Add Value, and then add the following registry value: 

      Value Name: EnablePMTUBHDetect
      Data Type: REG_DWORD
      Value: 1
      Restart the machine

  4. Check the network binding order:

    To configure the network binding order:
    1. Quit any programs that are running.
    2. Right-click Network Neighborhood, and then click Properties.
    3. Click the Bindings tab. In the Show Bindings For box, click All Services.
    4. Double-click each listed service to expand it.
    5. Under each service, double-click each protocol to expand it.
    6. Under each protocol, there is a number of network adapter icons. Click the icon for your network adapter, and then click Move Up until the network adapter is at the top of the list. Leave the "Remote Access WAN Wrapper" entries in any order under the network adapter(s).

      Note: If you have more than one network adapter, place the internal adapter (with Internet Protocol [IP] address by default on a Small Business Server network) at the top of the binding order, with the external adapter(s) directly below the internal adapter.

      The final order should appear similar to:
      [1] Network adapter one
      [2] Network adapter two (if present)
      [3] Remote Access WAN Wrapper
      [n] Remote Access WAN Wrapper

    7. Repeat step f for each service in the dialog box.
    8. After you have verified the settings for each service, click All Protocols in the Show Bindings For box. The entry for "Remote Access WAN Wrapper" does not have a network adapter listed. Skip this item. Repeat steps 4 through 6 for each remaining protocol.
    9. After you have verified that the bindings are set correctly for all services and protocols, click OK. This initializes the rebinding of the services. When this is complete, you are prompted to restart the computer. Click Yes.


More Information


Active Directory changes do not replicate in Windows Server 2003;EN-US;830746

The information in this article applies to:

Windows Server 2012 R2
Windows Server 2012
Windows Server 2008 R2 Standard
Windows Server 2008 Standard 
Microsoft Windows Server 2003 R2 Standard x64 Edition 
Microsoft Windows Server 2003 R2 Standard Edition (32-bit x86) 
Microsoft Windows Server 2003, Standard x64 Edition 
Microsoft Windows Server 2003, Standard Edition (32-bit x86) 
Microsoft Windows 2000 Server