Avatar of Corey Cheever
Corey Cheever
Flag for United States of America asked on

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

The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.
 Replica set name is    : "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
 Replica root path is   : "c:\windows\sysvol\domain"
 Replica root volume is : "\\.\C:"
 A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to read from the NTFS USN journal is not found.  This can occur because of one of the following reasons.
 [1] Volume "\\.\C:" has been formatted.
 [2] The NTFS USN journal on volume "\\.\C:" has been deleted.
 [3] The NTFS USN journal on volume "\\.\C:" has been truncated. Chkdsk can truncate the journal if it finds corrupt entries at the end of the journal.
 [4] File Replication Service was not running on this computer for a long time.
 [5] File Replication Service could not keep up with the rate of Disk IO activity on "\\.\C:".
 Setting the "Enable Journal Wrap Automatic Restore" registry parameter to 1 will cause the following recovery steps to be taken to automatically recover from this error state.
 [1] At the first poll, which will occur in 5 minutes, this computer will be deleted from the replica set. If you do not want to wait 5 minutes, then run "net stop ntfrs" followed by "net start ntfrs" to restart the File Replication Service.
 [2] At the poll following the deletion this computer will be re-added to the replica set. The re-addition will trigger a full tree sync for the replica set.
WARNING: During the recovery process data in the replica tree may be unavailable. You should reset the registry parameter described above to 0 to prevent automatic recovery from making the data unexpectedly unavailable if this error condition occurs again.
To change this registry parameter, run regedit.
Click on Start, Run and type regedit.
Click down the key path:
Double click on the value name
   "Enable Journal Wrap Automatic Restore"
and update the value.
If the value name is not present you may add it with the New->DWORD Value function under the Edit Menu item. Type the value name exactly as shown above.
Windows Server 2012* FRS

Avatar of undefined
Last Comment
Hello There

8/22/2022 - Mon

View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.

The short answer is the d2/d4 burflags the error includes the fix in the registry to set the parameter to reinitialize the database.

What is your environment?


Kevin, pointed out once you fix the FRS replication,
Transition to dfs-R if your DCs are newer than server 2003 R2
This will simplify, improve things and setup simpler transition to the new versions.
Hello There

The above means that the SYSVOL replication is broken. First, follow the instructions you posted. If this won't work, I would perform D4/D2 restore.

You have more DCs. So first you need to find out which of them is the bad one.
(event ID 13568 = bad domain controller, event ID 13516 = healthy domain controller)

Now you need to perform the D4 on a healthy DC = authoritative restore + the D2 on a bad DC = non-authoritative restore:
1. Backup the SYSVOL of all DCs you have
2. Stop File Replication service and make sure that the service is not running on any DC
3. Open HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup -> BurFlags
Healthy DC - set the D4 option
Bad DC - set the D2 option (you get a copy of the current SYSVOL and other folders from the good DC)
4. Start the File Replication service and wait for theSYSVOL folder to be synced
5. Verify that you can see event ID 13516 on all DCs
Corey Cheever

So I found this link [Solved] NTFRS – Journal Wrap Errors detected on Domain Controller (squidworks.net) and this actually worked fixing my problems.
This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.

The error that you posted actually includes the solution at the bottom of the message. The links are merely to explain what the error is and possible causes.
Hello There

Well, you marked the wrong answer as a solution.