A colleague of mine stopped by and reported users at one of our offices were not receiving settings from a recently updated GPO. Upon further review, we noticed the gpt.ini file for the updated GPO did not update on the domain controller at that office.
After logging into the remote DC I went to look at the File Replication Service logs to see if I could tell why the files were not replicating.
That's when I noticed Error 13568 under NtFrs. The contents of the was:
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.
 Volume "\\.\D:" has been formatted.
 The NTFS USN journal on volume "\\.\C:" has been deleted.
 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.
 File Replication Service was not running on this computer for a long time.
 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.
 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.
 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.
After doing some research, the resolution was to rebuild the SYSVOL folder on the domain controller. To do that preform the following steps
1. Stop FRS.
2. Start Registry Editor (Regedt.exe).
3. Locate and click the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore/Process at Startup
4. On the Edit menu, click Add Value , and then add the following registry value:
Value name: BurFlags
Data type: REG_DWORD
Value data: D2
5. Quit Registry Editor.
6. Restart FRS.
I ended up finding this error on a couple other domain controllers in our domain after combing for the error. (we have about 165 domain controllers in our environment)
Rebuilding the SYSVOL folder fixed the issue on each of them. We've seen this on both Windows 2003 and 2008 based servers.