Share via

Windows server 2022 - DFS problem - error 9014

Anonymous
2025-01-27T12:37:03+00:00

Hello,

We use DFS to synchronize a specific folder across multiple Windows Server 2022 machines.
Recently, some servers stopped synchronizing, and in the Event Viewer, we see this error:

The DFS Replication service stopped replication on volume E:. 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: AAEA562F-0000-0000-0000-100000000000

Can someone help me with this issue? I have already run a checkdisk, but nothing unusual was found. (also free space available on all volume)

Windows Server Identity and access

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2025-01-28T07:25:18+00:00

    Hello

    Thank you for posting in Microsoft Community.

    The DFS Replication error 9014 (Database failure) you're encountering generally points to an issue with the DFS Replication database or its underlying files. Since you've already verified that there is sufficient disk space and no disk corruption via chkdsk, there are a few other things you can try to resolve the issue.

    Steps to Troubleshoot DFS Error 9014:

    1. Check DFS Replication Database

    The DFS Replication service relies on its internal database (DFSR database) to track the replication state. If this database becomes corrupted, you could see error 9014.

    Repair the DFS Replication Database:

    You can try to rebuild the DFS database:

    Open a Command Prompt as Administrator.

    Stop the DFS Replication service:

    net stop dfsr

    Rename the database folder (e.g., DFSR_DB to DFSR_DB.old) to force a rebuild. This folder is usually located at:

    C:\System Volume Information\DFSR\Private

    ren "C:\System Volume Information\DFSR\Private" "DFSR_DB.old"

    Restart the DFS Replication service:

    net start dfsr

    This will force DFS to recreate the database. However, note that any replication metadata might be lost, and you may need to resynchronize the data depending on the replication topology.

    1. Check for Disk or File System Issues

    While you mentioned that you’ve already run chkdsk without any issues, it may still be worth verifying the disk's health and integrity in more detail:

    Run wmic diskdrive get status to check for any warnings or errors related to disk health.

    Check the volume shadow copy and system restore services to ensure no conflicting services are affecting DFS.

    1. Check Permissions on DFS Folder

    Ensure that the DFS Replication service account has full access permissions to the folder being replicated. If permissions were changed recently or there are conflicts with other services, it could prevent DFS from accessing the folder correctly.

    To reset permissions:

    Right-click the folder being replicated.

    Go to Properties > Security and check that the DFS Replication service account has proper permissions.

    1. Ensure Proper Replication Configuration

    Sometimes, DFS issues arise due to misconfigurations or time synchronization problems.

    Verify replication settings:

    Open DFS Management.

    Ensure the replication group settings are correct.

    Check if there are any conflicts with the schedule or bandwidth throttling that could impact replication.

    Check DFS Replication logs:

    Use the Event Viewer or PowerShell commands to find more details about the error. Look for specific issues in the DFS Replication logs that might give more context on the failure:

    Open Event Viewer (eventvwr.msc), and navigate to Applications and Services Logs > DFS Replication to check for any additional errors or warnings.

    You can also use PowerShell to check replication status:

    Get-DfsrReplicatedFolder

    1. Check DFS Replication Service Logs

    The error you are seeing might also have more context in the DFS replication logs.

    Open the Event Viewer and go to Applications and Services Logs > Microsoft > DFS Replication.

    Look for any additional errors or warnings that might shed more light on the root cause.

    1. Force Synchronization (Optional)

    If the database and permissions seem fine, and if the DFS replication is still stuck, you can try forcing a manual synchronization:

    Open DFS Management and right-click on the problematic replication group.

    Choose Replicate Now to trigger a manual sync.

    I hope the above information is helpful to you.

    Best regards

    Runjie Zhai

    0 comments