Share via

File server replication is not working

Anonymous
2025-01-14T13:12:03+00:00

File server replication is not working

DFSR on the source server is in the wrong state. Its in an initial SYNC state 2, not a normal State 4

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-15T08:55:36+00:00

    Hi

    Thank you for posting in Microsoft Community.

    When DFS Replication is not working and the source server is in State 2: Initial Synchronization, this usually indicates that DFS replication cannot continue from the initial synchronization phase. This can be due to a variety of reasons such as network problems, corrupt replication databases, permissions issues, or missing configurations.

    Checking the DFS Replication Service Status

    Ensure that the DFS replication service is running on both the source and target servers.

    Check the status of the service by running the following command in PowerShell or at a command prompt:

    Get-Service -Name DFSR

    If the service is not started, use the following command to start it:

    Start-Service -Name DFSR

    Viewing DFS Replication Logs

    View the event logs of the source and target servers for errors related to DFS replication. 

    Open the Event Viewer (eventvwr.msc) and navigate to Application and Service Logs > DFS Replication. 

Look for logs with event IDs 4000, 4004, 5004, or 5014. These logs may provide more information about replication failures.

    Common error messages: 

    Event ID 4000: General replication error. 

Event ID 5004: DFS replication could not communicate with partner. 

Event ID 4012: Insufficient disk space on server.

    Check disk space

    Ensure that there is enough disk space on the source and target servers. If there is insufficient disk space, DFS replication will not proceed. 

    Run dfsrdiag replicationstate to check the status of DFS replication. 

Check the disk space on the volume where the DFS replication staging area and replicated files are stored.

    Checking the Staging Folder

    DFS replication uses staging folders to temporarily store changes. If there is a problem with the staging folder, it can cause replication to become stuck.

    The staging folder is usually located at:

    C:\System Volume Information\DFSR\staging

    Make sure that the staging folder has enough space and that there are no corrupted files.

    You can also check to see if the DFSR database is corrupt, if so, you may need to rebuild it.

    Verifying Permissions and Configuration

    Ensure that the DFS replication system has the required NTFS permissions to access the folders being replicated.

    Verify that the DFS replication share is properly configured on the source and target servers.

    Ensure that the DFS namespaces are configured correctly and that the replication group is using the correct folder targets.

    Checking for Network Problems

    If there are network problems between servers, such as firewalls blocking ports or connectivity issues, replication may be delayed or fail.

    Ensure that the ports required for DFS replication are open (e.g. TCP 5722 for replication communication).

    Check the SYSVOL folder (for domain controllers)

    If DFSR is having problems on a domain controller and it is related to the SYSVOL folder, verify the SYSVOL replication status:

    Event ID 13556 is a common event when SYSVOL replication fails.

    Ensure that you are not still using File Replication Service (FRS) for SYSVOL replication (in newer versions of Windows Server, DFSR is used by default).

    I hope you find the above information helpful.

    Best regards

    Runjie Zhai

    0 comments