JRNL_WRAP_ERROR in FRS event log

M

Michael Honkomp

I am getting this errror in a single server AD install. What is the
best way to recover?



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

Richard McCall [MSFT]

When a single server get journal wrap errors use the article and make sure
that you set burflags to D4 and restart FRS.

--
Richard McCall [MSFT]

"This posting is provided "AS IS" with no warranties, and confers no
rights."
Todd Maxey said:
Michael,

Please take a look at the following article

Troubleshooting Journal_Wrap Errors on Sysvol and DFS Replica Sets
http://support.microsoft.com/?kbid=292438


Michael Honkomp said:
I am getting this errror in a single server AD install. What is the
best way to recover?



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

Michael Honkomp

Are there any necessary backup steps I need to take. Is there any
concern about losing this info when you do the D4?

Mike

Richard McCall said:
When a single server get journal wrap errors use the article and make sure
that you set burflags to D4 and restart FRS.

--
Richard McCall [MSFT]

"This posting is provided "AS IS" with no warranties, and confers no
rights."
Todd Maxey said:
Michael,

Please take a look at the following article

Troubleshooting Journal_Wrap Errors on Sysvol and DFS Replica Sets
http://support.microsoft.com/?kbid=292438


Michael Honkomp said:
I am getting this errror in a single server AD install. What is the
best way to recover?



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

Michael Honkomp

Any precautions I need to take before running the D4 rebuild? Any
backups and issues that may come up as a result?

Mike

Are there any necessary backup steps I need to take. Is there any
concern about losing this info when you do the D4?

Mike

Richard McCall said:
When a single server get journal wrap errors use the article and make sure
that you set burflags to D4 and restart FRS.

--
Richard McCall [MSFT]

"This posting is provided "AS IS" with no warranties, and confers no
rights."
Todd Maxey said:
Michael,

Please take a look at the following article

Troubleshooting Journal_Wrap Errors on Sysvol and DFS Replica Sets
http://support.microsoft.com/?kbid=292438


I am getting this errror in a single server AD install. What is the
best way to recover?



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.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top