Error 1727 0x6bf
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for 1726 the remote procedure call failed Help Receive Real-Time Help Create a Freelance Project Hire for 1727 the remote procedure call failed and did not execute a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > AD Replication Problem Want to Advertise Here? Solved AD Replication Problem Posted on 2010-08-27 Active Directory Windows Server 2008 Windows Server 2003 2 Verified Solutions 19 Comments 4,013 Views Last Modified: 2012-05-10 Hi, I have a problem with the AD replication. We have two domain controller as the below. Head Office DC1 - Windows 2008 R2 Branch Office DC2 - Windows 2003 R2 When I replicate mannually from ADSS, it if fine. Also when I used REPADMIN /SHOWRES command on DC1 it is fine. But when I used REPADMIN /SHOWREPS command on DC3 it fails by time to time and success sometimes. See the message below. C:\Documents and Settings\Administrator.COMPANY>repadmin /showreps HeadOffice\DC2 DC Options: IS_GC Site Options: (none) DC object GUID: 278a591d-34e6-40e6-9b17-95950dcdc6f8 DC invocationID: 270ec0d2-ea86-495b-bb8b-1568d67dd818 ==== INBOUND NEIGHBORS ====================================== DC=COMPANY,DC=co,DC=uk HeadOffice\DC1 via RPC DC object GUID: 17724d8e-2f74-4cb9-8015-99282f2e1004 Last attempt @ 2010-08-27 14:15:45 was successful. CN=Configuration,DC=COMPANY,DC=co,DC=uk HeadOffice\DC1 via RPC DC object GUID: 17724d8e-2f74-4cb9-8015-99282f2e1004 Last attempt @ 2010-08-27 13:47:21 failed, result 1727 (0x6bf): Can't retrieve message string 1727 (0x6bf), error 1815. 1 consecutive failure(s). Last success @ 2010-08-27 12:50:04. CN=Schema,CN=Configuration,DC=COMPANY,DC=co,DC=uk HeadOffice\DC1 via RPC DC object GUID:
sites in particular seems to be a problem. Hoping for some advice ifthis looks familiar to anyone.If we get replication problems as indicated by repadmin /showrepl, rebootingthe remote DC gets things going again, but is not a great solution and alsoit take a long time for the DC to come back up.We have two local DCs both of which replicate with the remote DC. Thereplication has failed with the remote and both of these DCs, but not alwaysat the same time (i.e. one works, one doesn't).If I try to run a forced replication (repadmin /replicate...), I get thefollowing:DsReplicaSync() failed waith status 1727 (0x6bf).(I got no hits https://www.experts-exchange.com/questions/26434173/AD-Replication-Problem.html searching for that code on google BTW)Pinging between the DCs works, as does browsing. I also tried the port querytool on 135 and it works. The only other thing that seems to fail when thisis replication error occurs is that I can't remote desktop to the remote DCfrom within out local LAN while this error is occuring. However I can remoteto another server within the remote http://microsoft.public.windows.server.active-directory.narkive.com/Kh9rxeCm/fixing-replication-failures LAN and then remote from there to theDC.The other point of interest in this is that if I run AD Sites and Service onthe remote DC, its site shows that it is trying to replicate with every sitein the company. If I correct that so it just replicates with the local DCs,later I can look at it again and its changed back.Event viewer shows nothing of great value, really only errors that there wasa problem (15308).Thanks! Ace Fekay [MVP] 2007-06-14 03:47:03 UTC PermalinkRaw Message Post by BrianWe are having occasional replication errors throughout our domain,but one of the sites in particular seems to be a problem. Hoping forsome advice if this looks familiar to anyone.If we get replication problems as indicated by repadmin /showrepl,rebooting the remote DC gets things going again, but is not a greatsolution and also it take a long time for the DC to come back up.We have two local DCs both of which replicate with the remote DC. Thereplication has failed with the remote and both of these DCs, but notalways at the same time (i.e. one works, one doesn't).If I try to run a forced replication (repadmin /replicate...), I getDsReplicaSync() failed
we are using windows server 2012R2 with Domain controller ( One primary and Two Backup ) all are GC . I have issues with one of the domain http://www.networksteve.com/forum/topic.php/Active_Directory_Domain_Services_attempted_to_perform_a_remote_p/?TopicId=90486&Posts=9 controller (perform a remote procedure call (RPC) While restarting the server it took http://www.chicagotech.net/troubleshooting/rpcfailed1.htm long time for rebuild DNS activity and I have verified from operation master role ( Primary role Error Another Two Domain both are working perfectly.Only issues from remote site domain controller only Note : This Domain controller located in remote site there is no any issues related with any Security or the remote firewall Because of our network team they are enabled all access permission from PR to DR Domain controller Active Directory Domain Services attempted to perform a remote procedure call (RPC) to the following server. The call timed out and was cancelled. Server: 83d21861-ce9d-4201-bea5-fef1b117de1c._msdcs.KIMB.COM Call Timeout (Mins):5 Thread ID: 974 September 17th, 2015 4:55am Hi Could you please check the article and follow the the remote procedure steps for fix the issue, http://social.technet.microsoft.com/wiki/contents/articles/11795.troubleshooting-ad-replication-error-1818-the-remote-procedure-call-was-cancelled.aspx Check on DC's which is the fsmo roles holder...run on cmd "netdom query fsmo",if the fsmo holder is the problematic dc,you need to transfer the fsmo roles. Free Windows Admin Tool Kit Click here and download it now September 17th, 2015 5:54am Dear Boss Thanks for your support The command completed successfully. C:\Users\Administrator.KIMB>netdom query fsmo /verify Schema master Main-Domain-Pr.KIMB.COM Domain naming master Main-Domain-Pr.KIMB.COM PDC Main-Domain-Pr.KIMB.COM RID pool manager Main-Domain-Pr.KIMB.COM Infrastructure master Main-Domain-Pr.KIMB.COM The command completed successfully. DC=KIMB,DC=COM Default-First-Site-Name\MAIN-DOMAIN-PR via RPC DSA object GUID: 83d21861-ce9d-4201-bea5-fef1b117de1c Last attempt @ 2015-09-17 12:52:40 failed, result 1727 (0x6bf): The remote procedure call failed and did not execute. 552 consecutive failure(s). Last success @ 2015-09-03 07:13:49. Default-First-Site-Name\MAIN-SUBDOMAIN via RPC DSA object GUID: 2728ed7d-7fd0-4168-96fb-e83663a3d5cd Last attempt @ 2015-09-17 13:01:57 was successful. CN=Configuration,DC=KIMB,DC=COM Default-First-Site-Name\MAIN-DOMAIN-PR via RPC DSA object GUID: 83d21861-ce9d-4201-bea5-fef1b117de1c Last attempt @ 2015-09-17 12:53:18 failed, result 1727 (0x6bf): The remote procedure call failed and did not execute. 384 consecutive failure(s). Last success @ 2015-09-03 06:57:23. Default-First-Site-Name\MAIN-SUBDOMAIN via RPC DSA object GUID: 2728ed7d-7fd0-4168-96fb-e83663a3d5cd Last at
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: Make sure you have good connection. By default, these dynamic ports start with 1024. Check the firewall configuration. Connectivity issues after the installation of MS05-019 or Server 2003 SP1 Related Topics Remote Procedure Call Failed RPC Server is Unavailable This web is provided "AS IS" with no warranties. Copyright © 2002-2015 Chicago