Error code 1727

This guide will highlight several possible causes that can lead to a crash with error code 1727, and then presents possible recovery methods that you can try to resolve.

Approved: ASR Pro

Speed up your computer’s performance now with this simple download.

• 3 blocks to read

This short article resolves the “Remote business call failed and did not complete” error. This error occurs during domain controller (DC) replication in server windows.

Applies to: Windows 10 Version 2004, Windows 10 Version 1909, Windows Server 2019, Windows Server 2012 R2, Windows Server 2016
Original Knowledge Base Number: 4019721

Symptoms

This failed Active Directory (AD) replication will appear in one or more of the following forms:

• Decimal: 1727
• Hexadecimal: 0x6bf
• Symbolic: RPC_S_CALL_FAILED_DNE
• Error message: term remote procedure failed and was not executed.

Reason

• Networking between two domain controllers (DCs). See the following sections for more information.
• Stress-induced utility problem with replication partners. This problem is less common and in most cases is temporary. More information can be found in the following areas of work.

About A Network Connection Problem

This occurs when the replication partner of the domain controller simply cannot establish an RPC connection to the AD Replication RPC service (DRSR UUID E3514235-4B06-11D1-AB04-00C04FC2DCD2). In particular, a replication partner can currently bind to an RPC endpoint mapper, but cannot bind any type of DRSR RPC.

• Firewall
• Router
• WAN Optimizer
• other intermediate mobile devices.
• Network Filter Driver

About A Performance Issue

This issue occurs when one of the following conditions is true:

• The server is lagging and does not correct the TCP ACK or Rejoinder message. The sender is canceling the TCP session.
• The network is too slow or too heavy. It cannot deliver either a TCP ACK or a response message.

Resolution

To resolve this discovery scenario, if possible, you should undo any recent changes that affect the current network between the two domain controllers. If there have been no recent changes, the network connection should be fully assessed.RPC communication between two other domain controllers. To do this, follow our own general troubleshooting instructions or detailed troubleshooting instructions.

High-level Troubleshooting Steps

1. When reproducing the problem, check your network. To do this, follow these steps:

   1. Run a network scan on both domain controllers.
   2. Start replication between these two domain controllers manually.
   3. Stop searching both ways if you get an error.

2. Examine conversational RPC between two domain controllers. Be aware that there may be a case where the message itself sent by the domain controller to the requesting party does not trigger a response from the replica partner.

Detailed Troubleshooting Instructions

Begin network exploration on both domain controllers before performing the steps to test domain controller connectivity.

Verify DC Power Connection To Target DC

1. Approved: ASR Pro

   ASR Pro is the world’s most popular and effective PC repair tool. It is trusted by millions of people to keep their systems running fast, smooth, and error-free. With its simple user interface and powerful scanning engine, ASR Pro quickly finds and fixes a broad range of Windows problems — from system instability and security issues to memory management and performance bottlenecks.

2. 1. Download ASR Pro and install it on your computer
3. 2. Launch the program and click «Scan»
4. 3. Click «Repair» to fix any issues that are found

Note

Ports in veThese areas are also DC related and assigned dynamically. However, the administrator will hard-code the appropriate port for AD replication using the following Windows registry value: Value:

hkey_local_machine system currentcontrolset services ntds parameters
Registering TCP / IP Port
Value type: REG_DWORD
Hard disk value: (available port)