none
Problem dfsr RRS feed

All replies

  • Hi,

    Could you provide some more information how you are receiving this warning?

    What has been done in the environment?

    The event ID 2109 can occur for example if a restore of the SYSVOL has been done, because it is replicated with DFS Replication.

    Are you receiving any other warnings/errors after the event id 2109?


    Best regards,
    Leon

    Blog: https://thesystemcenterblog.com LinkedIn:

    Wednesday, September 11, 2019 1:00 PM
  • exactly I did a system restore,after this error I receive the errors n °:2212,2004
    Wednesday, September 11, 2019 1:14 PM
  • thank you for your reply

    do you think I have to do a second  system restore (Sysvol Authoritative Restore)

    Wednesday, September 11, 2019 6:37 PM
  • I don't know how you performed the restore, but if there are errors you could try performing the restore again by following the previously mentioned links.

    Blog: https://thesystemcenterblog.com LinkedIn:

    Wednesday, September 11, 2019 6:39 PM
  • I made the first restore without any procedures, after the first restore the server it can not start I had a lot of problems now all the problems are fixed except a hard disk that can not replicate the other  hard drive it works very well
    Wednesday, September 11, 2019 6:50 PM
  • which is weird that I managed to unlock the replication for the second disk
    Wednesday, September 11, 2019 6:56 PM
  • Hi,

    Thanks for your posting here。

    How is your situation now?

    If there is anything else we can do for you, please feel free to post in the forum.

    Fan


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

    Thursday, September 12, 2019 5:49 AM

  • unfortunately it does not work
    Thursday, September 12, 2019 8:32 AM
  • thanks, the problem is not solved yet

    ----------------------------------

    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider Name="DFSR" />
      <EventID Qualifiers="32768">2109</EventID>
      <Level>3</Level>
      <Task>0</Task>
      <Keywords>0x80000000000000</Keywords>
      <TimeCreated SystemTime="2019-09-12T08:20:39.885260600Z" />
      <EventRecordID>40787</EventRecordID>
      <Channel>DFS Replication</Channel>
      <Computer>serveur.citindustrie.com</Computer>
      <Security />
      </System>
    - <EventData>
      <Data>302EEE1D-D229-11E4-AAE1-9C8E994DDC35</Data>
      <Data>F:</Data>
      <Data>54C4D790-E029-4100-BB29-1628EBCDFEA2</Data>
      </EventData>

     </Event>

    -------------------------------

    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider Name="DFSR" />
      <EventID Qualifiers="32768">2212</EventID>
      <Level>3</Level>
      <Task>0</Task>
      <Keywords>0x80000000000000</Keywords>
      <TimeCreated SystemTime="2019-09-12T07:55:50.399894400Z" />
      <EventRecordID>40745</EventRecordID>
      <Channel>DFS Replication</Channel>
      <Computer>serveur.citindustrie.com</Computer>
      <Security />
      </System>
    - <EventData>
      <Data>302EEE1D-D229-11E4-AAE1-9C8E994DDC35</Data>
      <Data>F:</Data>
      </EventData>

     </Event>

    --------------------

    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider Name="DFSR" />
      <EventID Qualifiers="49152">2004</EventID>
      <Level>2</Level>
      <Task>0</Task>
      <Keywords>0x80000000000000</Keywords>
      <TimeCreated SystemTime="2019-09-12T07:56:14.306166800Z" />
      <EventRecordID>40746</EventRecordID>
      <Channel>DFS Replication</Channel>
      <Computer>serveur.citindustrie.com</Computer>
      <Security />
      </System>
    - <EventData>
      <Data>302EEE1D-D229-11E4-AAE1-9C8E994DDC35</Data>
      <Data>F:</Data>
      <Data>32</Data>
      <Data>Le processus ne peut pas accéder au fichier car ce fichier est utilisé par un autre processus.</Data>
      </EventData>
      </Event>

    Thursday, September 12, 2019 8:39 AM
  • Hi,

    I saw that Leon provided some advice for you already, i would like to confirm that what did you have already done for the problem.

    Did the event log still show the same event:2109/2004/2212?

    Would you please check the DFSR state by creating the diagnostic report again ?

    Best Regards,

    Fan


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

    Friday, September 13, 2019 1:16 AM
  • I tried everything but the problem did not solve

    yes I always have event:2109/2004/2212

    I find subject https://jorgequestforknowledge.wordpress.com/2010/08/12/restoring-the-sysvol-non-authoritatively-when-either-using-ntfrs-or-dfs-r-part-3/

    I tried this solution and the result was that all the hard drives were responding to the process, except for the hard drive f:


        REG ADD "HKLM\SYSTEM\CurrentControlSet\Services\DFSR\Restore" /v SYSVOL /t REG_SZ /d "authoritative" /f        
        [1] REG ADD
        "HKLM\SYSTEM\CurrentControlSet\Control\BackupRestore\SystemStateRestore"
         /v LastRestoreId /t REG_SZ /d "70000000-0000-0000-0000-000000000000" /f

        NET STOP DFSR        
        NET START DFSR        

    after all that he tells me the following error: 2004

    The DFS Replication service stopped replication on the F: volume. This problem may occur when the disk is full or down, or when a quota limit is reached. It can also occur if the DFS Replication Service encounters errors when creating files for a replicated folder on this volume.   Additional Information : Error: 32 (The process can not access the file because this file is being used by another process.) Volume: 302EEE1D-D229-11E4-AAE1-9C8E994DDC35

                
    • Edited by farhi2 Sunday, September 15, 2019 3:18 PM
    Sunday, September 15, 2019 9:47 AM
  • Hi,

    From what you described , i would recommend you check that are there files opened on other clients, since files only replicated by after the file were closed.Or any Virus software caused this.

    At the same time , check the disk space.

    For your reference:

    https://support.microsoft.com/en-sg/help/2517913/distributed-file-system-replication-dfsr-no-longer-replicates-files-af

    Best Regards,

    Fan


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

    Monday, September 16, 2019 6:56 AM