Troubleshooting File Replication Service Issues

Use the following general approach to fixing replication problems:

1. How to use Ntfrsutl.exe tool to troubleshoot FRS

2. Create a test file. If you use logon script, you may create a script on one of DCs. Make sure the file is copied to another DCs. Or you can create a group policy on a DC. The policy should be copied to another DCs. If not, you may have a replication issue.

3. Make sure the DC has enough disk spaces.

4. Check any errors in the Event Viewer.

5. Make sure DCs are Available on the Network with correct FQDN. You can ping DCs using FQDN, for example, ping ms-mvps.chicagotech.net.

6. Make sure File Replication Service is running.

7. Examine the Log Files.  The log files are located in the %Systemroot%\Debug folder. The file names are listed from NtFrs_001.log to NtFrs_005.log.

8. Monitor replication health by using Repadmin.exe to retrieve replication status.

Related Topics

Causes of Active Directory replication issues

FRS Tools

Perform a non-authoritative restore of the data

How to Repadmin.exe Tool to diagnose Replication Status

Troubleshooting File Replication Service Issues

Event ID 13568 - The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.

Event ID 1058 - Windows cannot access the file gpt.ini for GPO

Logon scripts don’t synchronize between two domain controllers

Group Policies may not update between DCs

“INFO: The policy object does not exist”

“RSoP data invalid. Likely causes are, data is corrupt, data has been deleted or data has never been created."

Bob Lin Photography services

Real Estate Photography services