none
Error with DSFR RRS feed

  • Question

  • Hi,

    I have installed windows 2008 R2 x64 on two servers and deployed DFS-Replication. Error 5014, 5008,5002 keeps on coming after certain days and replication starts after it. I'm worried why these error are occuring. can anyone help?

    EVENT 5014

    The DFS Replication service is stopping communication with partner EKTW2K8FSRV2 for replication group Photos due to an error. The service will retry the connection periodically.
    Additional Information:

    Error: 1723 (The RPC server is too busy to complete this operation.)

    Connection ID: 17ED06AD-C3FD-40E1-ABAB-73139A5C0097

    Replication Group ID: E980F065-7465-4523-A899-293133BEFDAA

    EVENT 5008The DFS Replication service failed to communicate with partner EKTW2K8FSRV2 for replication group Photos. This error can occur if the host is unreachable, or if the DFS Replication service is not running on the server.

    Partner DNS Address: EKTW2K8FSRV2.snpl.net.np

     Optional data if available:

    Partner WINS Address: EKTW2K8FSRV2

    Partner IP Address: 192.168.70.126

     The service will retry the connection periodically.

     Additional Information:

    Error: 1722 (The RPC server is unavailable.)

    Connection ID: 17ED06AD-C3FD-40E1-ABAB-73139A5C0097

    Replication Group ID: E980F065-7465-4523-A899-293133BEFDAA

    EVENT 5002

    The DFS Replication service encountered an error communicating with partner EKTW2K8FSRV2 for replication group Photos.

    Partner DNS address: EKTW2K8FSRV2.snpl.net.np

     Optional data if available:

    Partner WINS Address: EKTW2K8FSRV2

    Partner IP Address: 192.168.70.126

     The service will retry the connection periodically.

     Additional Information:

    Error: 1753 (There are no more endpoints available from the endpoint mapper.)

    Connection ID: 17ED06AD-C3FD-40E1-ABAB-73139A5C0097

    Replication Group ID: E980F065-7465-4523-A899-293133BEFDAA

    EVENT 5004

    The DFS Replication service successfully established an inbound connection with partner EKTW2K8FSRV2 for replication group Information.

    Additional Information:

    Connection Address Used: EKTW2K8FSRV2.snpl.net.np

    Connection ID: 455CB401-0DAF-4BA6-882C-8E0206C3A6A9

    Replication Group ID: B4BA1C7A-378E-4DE0-8522-CB9BB9E0B192

    Monday, March 19, 2012 5:35 AM

Answers

  • Hi,

    The RPC server unavailable or too busy errors can occur for the following reasons:

    • DNS problems
    • Time synchronization problem between DCs
    • RPC service is not running

    Based on your description, after those EVENT 5014, 5008, 5002, the replication starts again. I suspect the issue is related with an unstable WAN connection. You can capture the network trace to determine whether the cause of the problem is at the network layer. To examine the TCP ports that the DFS Replication service is using on replication partners, run the command: NETSTAT –ANOBP TCP in a Command Prompt windows.

    Meanwhile, I suggest you check the DFS Replication debug logs, which are located in the %systemroot%\debug folder.

    These documents may help you troubleshoot the DFS Replication issue

    Troubleshooting DFS Replication

    Understanding DFSR Debug Logging

    Regards,
    Miya


    Miya Yao

    TechNet Community Support

    Monday, March 19, 2012 9:58 AM
    Moderator

All replies

  • Hi,

    The RPC server unavailable or too busy errors can occur for the following reasons:

    • DNS problems
    • Time synchronization problem between DCs
    • RPC service is not running

    Based on your description, after those EVENT 5014, 5008, 5002, the replication starts again. I suspect the issue is related with an unstable WAN connection. You can capture the network trace to determine whether the cause of the problem is at the network layer. To examine the TCP ports that the DFS Replication service is using on replication partners, run the command: NETSTAT –ANOBP TCP in a Command Prompt windows.

    Meanwhile, I suggest you check the DFS Replication debug logs, which are located in the %systemroot%\debug folder.

    These documents may help you troubleshoot the DFS Replication issue

    Troubleshooting DFS Replication

    Understanding DFSR Debug Logging

    Regards,
    Miya


    Miya Yao

    TechNet Community Support

    Monday, March 19, 2012 9:58 AM
    Moderator
  • Hi,

    I have this same problem between two DCs (Windows Server 2008 R2 Std.) that reside in the same LAN/Subnet. Any suggestions?

    Regards,

    Pantelis Chasapis

    Saturday, November 15, 2014 7:09 PM
  • I suspect your problem is due to DFSR being an unreliable POS.
    Tuesday, March 31, 2020 5:21 PM