locked
Errors with DFSR RRS feed

  • Question

  • I've just deployed a Windows Data Center Edition File Server to replace an Enterprise Edition Server.

    I have 3 DFS roots with a total of about 12 DFS links.

    All of my DFS links are setup to replicate one copy of the data offsite.

    The largest DFS folder that I have is the "Users" folder.

    Since I have replaced the file server at the Data Center, i've been waiting for a month and a half so far to replicate one folder over a 10 meg fiber connection.

    What's happening on the Data Center Ed host for that one folder is i'm getting event id: 5014 every 15 minutes or so. 

    Event Type: Warning
    Event Source: DFSR
    Event Category: None
    Event ID: 5014
    Date:  3/26/2009
    Time:  11:26:57 AM
    User:  N/A
    Computer: FP-XYY
    Description:
    The DFS Replication service is stopping communication with partner FP-XYZ for replication group XXX due to an error. The service will retry the connection periodically.
     
    Additional Information:
    Error: 9027 (A failure was reported by the remote partner)
    Connection ID: ADF258BB-DAEF-4350-A68A-166A2BD31B57
    Replication Group ID: CC8BC711-CCA6-41A9-9FC3-39283CB2DB5E

    I have about 5 replicated folders between the two hosts in the replication group that's having this problem and if I remove the "Users" folder, the error messages cease.

    I've tried stopping the DFSR service and deleting the dfsr.db file on the drive where the user's folder is located on FP-XYZ. This didn't change anything.

    I also see the following error:

    Event Type: Warning
    Event Source: DFSR
    Event Category: None
    Event ID: 5014
    Date:  3/26/2009
    Time:  8:54:10 AM
    User:  N/A
    Computer: FP-XYY
    Description:
    The DFS Replication service is stopping communication with partner FP-XYZ for replication group XXX due to an error. The service will retry the connection periodically.
     
    Additional Information:
    Error: 1726 (The remote procedure call failed.)
    Connection ID: ADF258BB-DAEF-4350-A68A-166A2BD31B57
    Replication Group ID: CC8BC711-CCA6-41A9-9FC3-39283CB2DB5E


    If anyone has any help it would be appreciated.

    Otherwise, I think i'll just get rid of DFSR. We've lost too many files because of it and a lot of users are afraid to put files on the network because of this.

    There have been some real strange things with DFSR like deleting files for no reason.


    Thursday, March 26, 2009 6:47 PM

Answers

  • Hi Jerico99,

    Thanks for posting here.

    To troubleshoot the issue, we may need to collect some information to confirm with you first.

    1. What is the operation system of the problematic server? Windows Server 2003 SP2 or Windows Server 2008?

    2. do you also can view Event ID: 5008 error message in the event viewer?

    3. could you please tell us what do you save in the problematic "Users" folder? Does the content of the “users” folder frequently change?

    For your reference, here are some steps you may try on the problematic server.

    1. Add these registry values to all DFSR replications partners that are having the issues. You will need to reboot for these changes to take effect.

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

    Value =DisableTaskOffload
    Type = DWORD
    Data = 1

    Value =EnableTCPChimney
    Type = DWORD
    Data = 0

    Value =EnableTCPA
    Type = DWORD
    Data = 0

    Value =EnableRSS
    Type = DWORD
    Data = 0

    2. Please apply the following update on the problematic server

    An update to turn off default SNP features is available for Windows Server 2003-based and Small Business Server 2003-based computers
    http://support.microsoft.com/kb/948496


    3. Please reboot the server and wait for some while to monitor if the replication is normal.


    4. if the issue still continues, please refer to the following link to create a diagnostic report for further research.

    Create a diagnostic report for DFS Replication

    http://technet.microsoft.com/en-us/library/cc778105.aspx


    Please note: you may send the report to tfwst@microsoft.com


    Hope it helps.

     


    This posting is provided "AS IS" with no warranties, and confers no rights.
    • Marked as answer by David Shen Thursday, April 2, 2009 3:44 AM
    Monday, March 30, 2009 2:04 AM
  • Thanks for your reply.

    The problem turned out to be a network issue.

    I had an application layer filter on a cisco router that was falsley identifying the DFSR traffic as a p2p downloader.

    • Marked as answer by David Shen Thursday, April 2, 2009 6:35 AM
    Thursday, April 2, 2009 6:31 AM

All replies

  • Hi Jerico99,

    Thanks for posting here.

    To troubleshoot the issue, we may need to collect some information to confirm with you first.

    1. What is the operation system of the problematic server? Windows Server 2003 SP2 or Windows Server 2008?

    2. do you also can view Event ID: 5008 error message in the event viewer?

    3. could you please tell us what do you save in the problematic "Users" folder? Does the content of the “users” folder frequently change?

    For your reference, here are some steps you may try on the problematic server.

    1. Add these registry values to all DFSR replications partners that are having the issues. You will need to reboot for these changes to take effect.

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

    Value =DisableTaskOffload
    Type = DWORD
    Data = 1

    Value =EnableTCPChimney
    Type = DWORD
    Data = 0

    Value =EnableTCPA
    Type = DWORD
    Data = 0

    Value =EnableRSS
    Type = DWORD
    Data = 0

    2. Please apply the following update on the problematic server

    An update to turn off default SNP features is available for Windows Server 2003-based and Small Business Server 2003-based computers
    http://support.microsoft.com/kb/948496


    3. Please reboot the server and wait for some while to monitor if the replication is normal.


    4. if the issue still continues, please refer to the following link to create a diagnostic report for further research.

    Create a diagnostic report for DFS Replication

    http://technet.microsoft.com/en-us/library/cc778105.aspx


    Please note: you may send the report to tfwst@microsoft.com


    Hope it helps.

     


    This posting is provided "AS IS" with no warranties, and confers no rights.
    • Marked as answer by David Shen Thursday, April 2, 2009 3:44 AM
    Monday, March 30, 2009 2:04 AM
  • Thanks for your reply.

    The problem turned out to be a network issue.

    I had an application layer filter on a cisco router that was falsley identifying the DFSR traffic as a p2p downloader.

    • Marked as answer by David Shen Thursday, April 2, 2009 6:35 AM
    Thursday, April 2, 2009 6:31 AM
  • Hi Jerico99,

    Thank you for the sharing of the solution, this could be helpful for the other community members.

    This posting is provided "AS IS" with no warranties, and confers no rights.
    Thursday, April 2, 2009 6:35 AM
  • Hi ,

    I am facing the same issue in my organization.

    On-prem Source server : WS2008r2, Azure Destination Serer : WS2012.(On-prem to azure configuring DFSR).

    I am facing the error RPC failed, event ids 5014, 6006.

    The data is replicating but it is replicating onle one 1GB per day.

    For every 30 sec I am getting the warning like RPC failed.

    Please help me out this.

    Regards,

    satish426

    Friday, September 19, 2014 11:51 AM
  • Hi ,

    Can anyone help me on the below DFS replication issue.

    The DFS Replication service is stopping communication with partner OCBOMNAS01 for replication group On-Prem to Cloud Replication due to an error. The service will retry the connection periodically.
     
    Additional Information:
    Error: 1726 (The remote procedure call failed.)
    Connection ID: A4C3A83C-C34D-49CB-9E0A-BDE6F44D2720
    Replication Group ID: 1D229F31-16EC-4A24-AB65-F4C86CC1B947

    Eagerly waiting for your quick response!

    Satish426

    Thursday, September 25, 2014 6:05 AM