Share via

Problems with DFS

Михаил Андросов 476 Reputation points
2026-03-25T21:23:05.5866667+00:00

Hi!

Do I have a number of Windows Server 2012 R2 servers? They make up the replication group. Today I found an error in the event log on one of the servers:

Source: DFSR

ID: 2104

The DFS Replication service failed to recover from an internal database error on volume C:. Replication has been stopped for all replicated folders on this volume.

Additional Information:

Error: 9214 (Internal database error (-1086))

Volume: 607959FF-CEB1-11E4-80B4-806E6F6E6963

Database: C:\System Volume Information\DFSR

I stopped DFS Replication service.

Rename System Volume Information\DFSR folder.

And started DFS Replication service.

Replication is not performed. I see errors in the event log.

Source: DFSR

ID: 2104

The DFS Replication service failed to recover from an internal database error on volume C:. Replication has been stopped for all replicated folders on this volume.

Additional Information:

Error: 9214 (Internal database error (-1121))

Volume: 607959FF-CEB1-11E4-80B4-806E6F6E6963

Database: C:\System Volume Information\DFSR

Source: DFSR

ID: 2004

The DFS Replication service stopped replication on volume C:. This failure can occur because the disk is full, the disk is failing, or a quota limit has been reached. This can also occur if the DFS Replication service encountered errors while attempting to stage files for a replicated folder on this volume.

Additional Information:

Error: 9014 (Database failure)

Volume: 607959FF-CEB1-11E4-80B4-806E6F6E6963

Source: DFSR

ID 2104

The DFS Replication service failed to recover from an internal database error on volume C:. Replication has been stopped for all replicated folders on this volume.

Additional Information:

Error: 9214 (Internal database error (-1121))

Volume: 607959FF-CEB1-11E4-80B4-806E6F6E6963

Database: C:\System Volume Information\DFSR

I don't understand, what's the mistake? What should be done to overcome the mistake?

Windows for business | Windows Server | User experience | Other
0 comments
Answer accepted by question author
  1. Jason Nguyen Tran 14,440 Reputation points Independent Advisor
    2026-03-26T03:48:54.56+00:00

    Hi Михаил Андросов,

    The error codes you’re seeing all point to corruption or failure in the DFSR database located under System Volume Information. Renaming the DFSR folder and restarting the service was a good first attempt, but since replication still fails, it suggests the database cannot rebuild itself properly.

    The most common causes are disk issues, insufficient free space, or corruption in the DFSR database files. Please start by checking the health of the C: drive with tools like chkdsk and confirm that there is adequate free space. Also verify that antivirus or backup software is not locking the DFSR folder. If the disk is healthy, the recommended fix is to rebuild the DFSR database by stopping the DFS Replication service, deleting the DFSR folder under System Volume Information, and then restarting the service. This forces DFSR to create a fresh database and resync from its partners.

    Keep in mind that rebuilding the database can trigger a full initial sync, which may take time depending on the size of your replicated data. If the errors persist even after a rebuild, you may need to remove and re‑add the server to the replication group, or escalate to Microsoft Support for deeper analysis.

    I hope the response provided some helpful insight. If it clarified the issue for you, please consider marking it as Accept Answer so others with the same issue can find the solution.

    Jason.

    1 person found this answer helpful.

2 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Kate Pham (WICLOUD CORPORATION) 585 Reputation points Microsoft External Staff Moderator
    2026-03-26T07:08:07.1333333+00:00

    Hi sir,

    Thank you for reaching to Microsoft Q&A community! Please help refer bellow answer to address the issue:

    The errors you are seeing (Event IDs 2104 and 2004 with internal database errors and database failure) indicate that the DFS Replication service is unable to recover from a database error and has stopped replication for all folders on the affected volume. Common causes include disk space issues, disk failure, or corruption in the DFSR database files.

    Recommended steps to resolve this issue are:

    1. Check the free disk space on the problematic server and ensure there is enough available.
    2. Verify that the NT AUTHORITY\System account has Full Control permissions on the "System Volume Information" folder.
    3. If there is sufficient free space and permissions are correct, stop the DFS Replication service, backup the DFSR folder in "System Volume Information," and delete the DFSR folder. Restart the DFS Replication service to allow it to recreate the folder and rebuild the database.
    4. If the error persists, run chkdsk C: /r to check for disk errors.
    5. If none of the above steps resolve the issue, consider removing the problematic server from the replication group and testing replication without it.

    For more details, please refer to the documents: https://learn.microsoft.com/en-us/archive/msdn-technet-forums/821d16d9-1f79-4104-bc23-b263c9454e7a

    https://learn.microsoft.com/en-us/archive/msdn-technet-forums/efaaaef1-ba42-4b1c-8b5b-6b58ff8c8e70

    Thanks and Regards!

    Kate

    0 comments
  2. Q&A Assist
    2026-03-25T21:23:25.1+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The errors indicate that the DFSR database on volume C: is corrupted and DFS Replication has stopped for all replicated folders on that volume. Simply renaming the C:\System Volume Information\DFSR folder caused DFSR to try to rebuild the database as a non‑primary member, which can lead to conflicts and data being moved into ConflictAndDeleted or PreExisting.

    To recover and resume replication while preserving this server as the source of truth, the affected member must be reinitialized as the designated primary member for its replicated folders. The supported recovery approach is:

    1. Disable the replicated folder(s) on all members
      • In DFS Management, set the replicated folder(s) to disabled on every member in the replication group.
      • Wait for DFSR Event ID 4008 on all members confirming the disabled state.
    2. Ensure AD replication and DFSR config refresh
      • Force Active Directory replication between sites if members are in different AD sites.
      • On each DFSR member, run DFSRDIAG POLLAD /MEM:<MemberName> so the DFSR service picks up the configuration changes after each change.
    3. Enable the affected server as primary first
      • On the server with the crashed database (the one that should keep its local data), enable the replicated folder(s) first.
      • Wait for DFSR Event ID 4112: “This member is the designated primary member for this replicated folder.”
      • This step ensures that during the database rebuild and initial sync, this server’s content is treated as authoritative.
    4. Re‑enable the other members
      • After Event ID 4112 is logged on the affected server, enable the replicated folder(s) on the remaining members.
      • Wait for DFSR Event ID 4104 on those members: “The DFS Replication service successfully finished initial replication on the replicated folder.”

    This sequence rebuilds the DFSR database on the failed member in a controlled way and avoids unnecessary movement of files into ConflictAndDeleted or PreExisting.

    If the DFSR database loss occurs during initial replication and no primary member is currently designated in AD, use Dfsradmin membership /set /isprimary:true on the intended primary member to restore the primary designation, but only if initial replication has not successfully completed previously. Using this on a member after normal replication is in place can create a rogue primary and cause conflicts.

    If files are already in ConflictAndDeleted or PreExisting, they can be recovered with the Get-DfsrPreservedFiles and Restore-DfsrPreservedFiles PowerShell cmdlets.

    References:

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.