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: Fortect
- 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
-
When reproducing the problem, check your network. To do this, follow these steps:
- Run a network scan on both domain controllers.
- Start replication between these two domain controllers manually.
- Stop searching both ways if you get an error.
-
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
Approved: Fortect
Fortect 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, Fortect quickly finds and fixes a broad range of Windows problems - from system instability and security issues to memory management and performance bottlenecks.
- 1. Download Fortect and install it on your computer
- 2. Launch the program and click "Scan"
- 3. Click "Repair" to fix any issues that are found
Regardless, check to see if the DC source is listening on TCP port 135. To do this, run all the
PortQry.exe -n -e 135commands.If the open state is FILTER, AD replication will likely fail and return error 1722 instead. Try resolving error 1722, and then check if AD replication is working. If the problem persists, repeat the detailed troubleshooting steps.
If the status is not FILTER, most commands return RPC endpoint mapper information. Search the DRS interface of the MS NT directory to find the top port in the Endpoint Mapper database that monitors DC power for AD replication. You can get one or more records. Note the ports for ncacn_ip_tcp only.
For example, you will get something similar to each of the following, showing two premium shipping methods 49159 and E3514235-4b06-11d1-ab04-00c04fc2dcd2 49160:
uuid: DRS interface of MS NT directoryncacn_ip_tcp: 2012dc [49159]UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 DRS interface from MS NT directoryncacn_ip_tcp: 2012dc [49160]
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)-
Check the TCP port connectivity to your ports specified in the top field. To do this, run the following command:
PortQry.exe -n-e example, execute future commands for you:
PortQry.exe -n 2012dc -e 49159PortQry.exe -n 2012dc -e 49160
If the port is in FILTER state, trace the network you have assembled in the market to see where the packet is blocked.
-
Test DNS. Make sure that the destination domain controller can usually restore the CNAME and register the hosts on the source domain controller. Also make sure the discovered IP address is the real IP address of the original domain controller. DNS. If it is an old or invalid home IP address, an attempt will be made toTried RPC connection, which can lead to the wrong source domain controller.
Test The Connection Of The Target Domain Controller To The Source Domain Controller
Sometimes there must be a partial response containing most of the overlaid TCP ACKs for the request message. However, the traffic has changed or the response usually does not go to the domain controller of the requesting type. Therefore, receiving a TCP stack must not receive an ACK.
The ports in the upper zone are required by the DC and assigned dynamically. However, the director can hard-code the port used for AD replication using the fanbase registry value.
Speed up your computer's performance now with this simple download.
