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:\winnt\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 "\\.\C:" 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
 File Replication Service was not running on this computer for a
 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
The correct responce as per a MS employee is
Here is an article that will explain what a journal wrap is:
292438 Troubleshooting Journal_Wrap Errors on Sysvol and DFS Replica Sets
The main thing here is to find out why this machine wound up in journal
To fix the journal wrap, you may have to perform a D2 (non authoratative
1. Click "Start", and then click "Run".
2. In the "Open" box, type "cmd" (without the quotation marks) and then
3. In the "Command" box, type "net stop ntfrs" (without the quotation
4. Click "Start", and then click "Run".
5. In the "Open" box, type "regedit" (without the quotation marks) and then
6. Locate the following subkey in the registry:
/Restore\Process at Startup
7. In the right pane, double-click "BurFlags".
8. In the "Edit DWORD Value" dialog box, type "D2" (without the quotation
marks) and then click "OK".
9. Quit Registry Editor, and then switch to the "Command" box.
10. In the "Command" box, type "net start ntfrs" (without the quotation
11. Quit the "Command" box.
When the FRS service restarts, the following actions occur:
- The value for BurFlags registry key returns to 0.
- Files in the reinitialized FRS folders are moved to a
- The FRS database is rebuilt.
- The member performs an initial join of the replica set from an upstream
partner or from the computer that is specified in the Replica Set Parent
registry key if a parent has been specified for SYSVOL replica sets.
- The reinitialized computer performs a full replication of the affected
replica sets when the relevant replication schedule begins.
diasm...@online.microsoft.comThis posting is provided "AS IS" with no warranties, and confers no rights.