none
Event 4012: Error: 9061 (The replicated folder has been offline for too long.) RRS feed

  • Question

  • mainserver had replication setup with remoteserver. Remote Server died a few years back and we never replaced it. 

    It has been removed from Replication Group, though mainserver is still there in the group and we use the Namespace for mounting shared volumes in the event we wanted to add another replica. 

    We are trying to add another replica, though we are getting the error below and it won't allow the initial replication to occur. We didn't want to completely destroy the replication group, just add another server to it as we are using the namespace for it. 

    remoteserver has been replaced with another remtoeserver of the same name (it was dumped from AD and readded) It is also a AD DC. Mainserver is not a AD DC. 

    I've tried a few of the Fixes Suggested for Event 4012: Error: 9061 (The replicated folder has been offline for too long.) though they didn't help.

    Where should I start?

    Thanks!

    Log Name:      DFS Replication
    Source:        DFSR
    Date:          2/16/2016 2:34:21 PM
    Event ID:      4012
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      mainserver
    Description:
    The DFS Replication service stopped replication on the folder with the following local path: G:\corpdata\Info-Systems. This server has been disconnected from other partners for 641 days, which is longer than the time allowed by the MaxOfflineTimeInDays parameter (60). DFS Replication considers the data in this folder to be stale, and this server will not replicate the folder until this error is corrected. 
     
    To resume replication of this folder, use the DFS Management snap-in to remove this server from the replication group, and then add it back to the group. This causes the server to perform an initial synchronization task, which replaces the stale data with fresh data from other members of the replication group. 
     
    Additional Information: 
    Error: 9061 (The replicated folder has been offline for too long.) 
    Replicated Folder Name: Info-Systems 
    Replicated Folder ID: BF84D8E4-A31A-453F-8F0F-0166124CEEFB 
    Replication Group Name: Corp-Data 
    Replication Group ID: A68351BA-0BBC-4725-B945-4E7CAD43AC45 
    Member ID: C8B8C217-FBBA-412A-8F19-F75C06852C6C

    Tuesday, February 16, 2016 11:57 PM

Answers

All replies

  • Hi Scooter,

    Thanks for your post.

    Could you please check old DFS namespace server information that saves in the remoteServerName attributes which is under the CN=Dfs_Configuration in the Active Directory object.

    You may use ADSIedit.msc to check the attribute on the DCs to remove the old DFS namespace information.

    a. Open ADSIedit.msc.

    b. Connect to Default Naming Context (the domain name)

    c. Expand and locate the container, which show the DFS root information

    CN=<name_of_the_root_of_the_namespace>,CN=Dfs-Configuration,CN=System,DC=<name_of_your_domain>

    d. In the middle area of the ADSIedit console, right-click on the namespace that you created and select Properties, check the attribute "remoteServerName" of the DFS root object to see if the decommissioned DFS root server name is in that value. You may remove it in the value.

     And please verify that all the domain controllers have been awared of the medication on their AD replica

    Then you could have a check.

    Besides,  you could try to following the steps described in the section Recovering DFSR from Content Protection in the following blog to troubleshoot the issue.

    Implementing Content Freshness protection in DFSR

    http://blogs.technet.com/b/askds/archive/2009/11/18/implementing-content-freshness-protection-in-dfsr.aspx

    And here is also the article about replacing the server with same name, it might be helpful.

    https://community.spiceworks.com/how_to/75097-replace-an-old-file-server-with-a-new-file-server-using-the-same-ip-same-name-same-shares

    Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

    Best Regards,

    Mary Dong


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, February 17, 2016 5:57 AM
    Moderator
  • On Item 'c' above:

    CN=Dfs-Configuration,CN=System,DC=<myDomain>,DC=com

    In the "Dfs-Configuration" folder are three Items. We have three Replication Groups. 

    DT = ms-DFS-Namespace-Anchor  (Folder icon - works fine)

    VM = ms-DFS-Namespace-Anchor (Folder icon - Not looked at yet)

    Data = fTDfs (This is not a Folder icon - One I'm trying to Fix) 

    Properties of Data had the remoteServerName property and its values were: *, \\OldDCServer(though not the old remote server)

    There was no remoteServerName property for DT or VM.

    Why is Data have a class of: fTDfs?

    Wednesday, February 17, 2016 9:04 PM
  • Hi Scooter,

    Thanks for your reply.

     fTDfs seems to be the inconsistent or orphaned namespace. Since "Windows 2000 Server mode" namespaces have an "fTDfs" class object that is named identically to the namespace.

    Best Regards,

    Mary Dong


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, February 18, 2016 8:34 AM
    Moderator
  • So I removed the Namespace for my Replica Group and re-created it and not it is listed:

    Data = ms-DFS-Namespace-Anchor

    Though That still is not helping the Error: 9061 (The replicated folder has been offline for too long.)  issue.

    Within this one Replica Group I have three types of folders :

    1) Folders that Replicate as they should - No Issues

    2) Folders that give Error: 9061 (The replicated folder has been offline for too long.) 

    These ones I have not Touched, and have removed the Old server that used to be its replica Partner

    3) Folders that give Error: 9098 (A tombstoned content set deletion has been scheduled)

    These folders I've removed from the Replica Group, then readied to the group. 


    Monday, February 22, 2016 5:35 PM
  • Hi Scooter,

    We found that you post a one new here. You could try to reset database to have a check.

    https://social.technet.microsoft.com/Forums/windowsserver/en-US/749deab6-b325-4da0-8792-02f1e4913e50/error-9098-a-tombstoned-content-set-deletion-has-been-scheduled?forum=winserverfiles#749deab6-b325-4da0-8792-02f1e4913e50

    Best Regards,

    Mary Dong


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, February 23, 2016 7:39 AM
    Moderator