Try resolving error 1722, and then check whether the AD replication succeeds. If the port status is FILTERED, the AD replication failure is likely to fail and return error 1722 instead. To do so, run the PortQry.exe -n -e 135 command. Verify whether the source DC is listening on TCP port 135. Test the source DC connectivity from the destination DCįollow these steps on the destination DC: Start a network capture on both DCs before you take the following steps to test DC connectivity. Therefore, the TCP stack doesn't receive an ACK. But the traffic has been modified or the response doesn't actually arrive at the requester DC. Occasionally, there is a partial response that includes the piggy-back TCP ACK for the request message. Determine whether there's ever a case in which the message that's sent from the requestor DC doesn't incur a response from the replication partner. Stop both sides of the trace when you receive the error.Įxamine the RPC conversation between the two DCs.Manually start replication between the two DCs.Take a double-sided network capture while you reproduce the problem. To do so, follow either the high-level troubleshooting steps or the detailed troubleshooting steps. If there are no recent changes, you must fully examine the RPC network connectivity between the two DCs. To resolve this problem, determine any recent changes that would affect the network between the two DCs and undo those changes if possible. It can't deliver the TCP ACK or the response message. The network is too slow or unreliable.The server is backlogged and doesn't respond to the TCP ACK or the response message.This problem occurs when one of the following conditions is true: More specifically, the replication partner can bind to the RPC endpoint mapper, but can't complete the DRSR RPC bind. This problem occurs when the DC's replication partner can't complete the RPC connection to AD Replication's RPC Service (DRSR UUID E3514235-4B06-11D1-AB04-00C04FC2DCD2). This issue is less common and is often transient in nature. A load-induced performance issue on the replication partner.A network connectivity issue between the two domain controllers (DCs).This problem occurs because of one of the following reasons: Error message: The remote procedure call failed and did not execute.This Active Directory (AD) replication error appears in one or more of the following forms:
PIGGY PORT MAP WINDOWS
This error occurs during domain controller (DC) replication on Windows Server.Īpplies to: Windows 10, version 2004, Windows 10, version 1909, Windows Server 2019, Windows Server 2012 R2, Windows Server 2016 Original KB number: 4019721 Symptoms This article solves the error message "The remote procedure call failed and did not execute".