Home | Site Map | How To | Windows Vista | Case Studies | Articles | Forums | Services | Donations | Careers | About Us | Contact Us|

The remote procedure call failed and did not run

Event ID 1232, 1265, 1925 and 5719

Symptoms: 1. When running Dcdiag.exe or the repadmin /showreps command, you may receive the following error message: “The replication generated an error (1727): The remote procedure call failed and did not execute”.

2. You may receive Event ID 1232 with this description: “Active Directory attempted to perform a remote procedure call (RPC) to the following server. The call timed out and was cancelled”.

3. You may receive Event ID 1925 with this description: “The attempt to establish a replication link for the following writable directory partition failed”.

4. You may receive Event ID 1265 with this description: “The remote procedure call failed and did not execute”.

5. You may receive Event ID 5719 with this description: “This computer was not able to set up a secure session with a domain controller in domain Domain_Name due to the following:
The remote procedure call failed and did not execute”.

Causes: The RPC failure that is reported in error 1727 may occur because the Faulty packets, port filtering, and firewall rules may block a port when the firewall or the network router is configured incorrectly. Also, The RPC failure may occur because Windows Server 2003 Service Pack 1 adds a new RPC element. Some firewalls, routers, and virtual private networks (VPNs) may not recognize this change to the RPC protocol. Therefore, any operation that requires an RPC Bind request may now fail if the RPC caller is a Windows Server 2003 Service Pack 1-based server.

Resolutions:

1. Make sure you have good connection.
2. By default, these dynamic ports start with 1024. Check the firewall configuration.
3. Connectivity issues after the installation of MS05-019 or Server 2003 SP1

Related Topics

Remote Procedure Call Failed
RPC Server is Unavailable