JRNL_WRAP_ERROR on SYSVOL

[Todd]

Getting the following error on a Windows 2000 domain
controller running SP3. I've increased the Ntfs Journal
size in MB from 128 to 1024 and it still I still get the
error. This error occurs immediately (4-6 seconds) after
I restart the NtFrs service. When checking some of the
files in the SYSVOL versus files in the SYSVOL of other
domain controllers it doesn't appear that the item I am
looking at (It was a policy) has replicated since December
2002!

We've also increased the staging area to 1Gb. I don't
know if I need to perform the non-authoritative restore or
not.

Thanks ahead of time for any assistance.



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.

[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.

Expand HKEY_LOCAL_MACHINE.
Click down the key path:
"System\CurrentControlSet\Services\NtFrs\Parameters"
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.

 

[Simon Geary]

When you get this error you have to do the non authoritative restore of FRS.
Note that this is not the same as performing a non-authoritative restore of
Active Directory, you just have to set the burflags registry key to D2. I
think (maybe someone could confirm) that doing a D2 after a Journal Wrap is
mandatory and it cannot be resolved without one. No matter how big you make
the journal size it wont undo the wrap, FRS still knows that it has
overwritten some data before it was replicated.

Journal wrap is sometimes accompanied by morphed folders in Sysvol. These
folders will have _ntfrs in the foldername. You should check for these as
well.

http://support.microsoft.com/?id=292438
http://support.microsoft.com/?id=328492

Getting the following error on a Windows 2000 domain
controller running SP3. I've increased the Ntfs Journal
size in MB from 128 to 1024 and it still I still get the
error. This error occurs immediately (4-6 seconds) after
I restart the NtFrs service. When checking some of the
files in the SYSVOL versus files in the SYSVOL of other
domain controllers it doesn't appear that the item I am
looking at (It was a policy) has replicated since December
2002!

We've also increased the staging area to 1Gb. I don't
know if I need to perform the non-authoritative restore or
not.

Thanks ahead of time for any assistance.



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.

[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.

Expand HKEY_LOCAL_MACHINE.
Click down the key path:
"System\CurrentControlSet\Services\NtFrs\Parameters"
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.

 

[Chriss3]

Hello Todd, in the end of the log you will get a description about a task
you can do to restore the Journal Warp. Follow that description or look at
the first KB in this post.

Click on Start, Run and type regedit.

Expand HKEY_LOCAL_MACHINE.
Click down the key path:
"System\CurrentControlSet\Services\NtFrs\Parameters"
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, then restart ntfrs.

Take a look at this KB-Articel:
http://support.microsoft.com/default.aspx?scid=kb;en-us;292438
Related Information:
http://www.microsoft.com/windowsserver2003/technologies/fileandprint/file/df
s/tshootfrs.mspx
Related KB-Articels:
http://support.microsoft.com/search...ON&QuerySource=gsfxSearch_Query&srchExtraQry=

//Christoffer Andersson

Getting the following error on a Windows 2000 domain
controller running SP3. I've increased the Ntfs Journal
size in MB from 128 to 1024 and it still I still get the
error. This error occurs immediately (4-6 seconds) after
I restart the NtFrs service. When checking some of the
files in the SYSVOL versus files in the SYSVOL of other
domain controllers it doesn't appear that the item I am
looking at (It was a policy) has replicated since December
2002!

We've also increased the staging area to 1Gb. I don't
know if I need to perform the non-authoritative restore or
not.

Thanks ahead of time for any assistance.



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.

[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.

Expand HKEY_LOCAL_MACHINE.
Click down the key path:
"System\CurrentControlSet\Services\NtFrs\Parameters"
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.