Discussion:
NtFrs error in event viewer
(too old to reply)
Dan V
2010-04-14 01:31:50 UTC
Permalink
i have a windows 2003 SBS and the server is mainly used as a file server.
exchange has been removed, wsus and sharepoint has also been removed. The
server locks up and no users have access to it every 3 days and i have to
reboot it to get everything to work again. I ran hardware tests and the
hardware is good. I dont know if this error is the reason. Any advice will
be appreciated.




Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13568
Date: 4/13/2010
Time: 8:07:18 PM
User: N/A
Computer: SERVER
Description:
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.

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.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Dan V
2010-04-14 03:16:04 UTC
Permalink
I wanted to add that there is only 1 server so should i ignore this ntfrs
message.
Post by Dan V
i have a windows 2003 SBS and the server is mainly used as a file server.
exchange has been removed, wsus and sharepoint has also been removed. The
server locks up and no users have access to it every 3 days and i have to
reboot it to get everything to work again. I ran hardware tests and the
hardware is good. I dont know if this error is the reason. Any advice will
be appreciated.
Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13568
Date: 4/13/2010
Time: 8:07:18 PM
User: N/A
Computer: SERVER
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.
Expand HKEY_LOCAL_MACHINE.
"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.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Dave Patrick
2010-04-14 03:33:34 UTC
Permalink
Something here may help.

http://www.eventid.net/display.asp?eventid=13568&eventno=1743&source=NtFrs&phase=1
--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
Post by Dan V
I wanted to add that there is only 1 server so should i ignore this ntfrs
message.
Post by Dan V
i have a windows 2003 SBS and the server is mainly used as a file server.
exchange has been removed, wsus and sharepoint has also been removed. The
server locks up and no users have access to it every 3 days and i have to
reboot it to get everything to work again. I ran hardware tests and the
hardware is good. I dont know if this error is the reason. Any advice will
be appreciated.
Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13568
Date: 4/13/2010
Time: 8:07:18 PM
User: N/A
Computer: SERVER
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.
Expand HKEY_LOCAL_MACHINE.
"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.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Dan V
2010-04-14 03:46:56 UTC
Permalink
I saw that but i dont understand why this was working fine and then all of a
sudden im seeing these errors. Also if i dont have another dc then i dont
need to use replication. Is that correct to say? I opened a command prompt
and ran and restarted the ntfrs service and then i looked at the event log
and no errors showed up.
Post by Dave Patrick
Something here may help.
http://www.eventid.net/display.asp?eventid=13568&eventno=1743&source=NtFrs&phase=1
--
Regards,
Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
Post by Dan V
I wanted to add that there is only 1 server so should i ignore this ntfrs
message.
Post by Dan V
i have a windows 2003 SBS and the server is mainly used as a file server.
exchange has been removed, wsus and sharepoint has also been removed.
The server locks up and no users have access to it every 3 days and i
have to reboot it to get everything to work again. I ran hardware tests
and the hardware is good. I dont know if this error is the reason. Any
advice will be appreciated.
Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13568
Date: 4/13/2010
Time: 8:07:18 PM
User: N/A
Computer: SERVER
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.
Expand HKEY_LOCAL_MACHINE.
"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.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Jonathan Joffe
2011-05-03 11:11:14 UTC
Permalink
I would be interested if you followed this up any further.

I noticed the same error IDs on my SBS 2008 server, and I tried the fix. But I then lost all Domain authentications and I could not fix this. Fortunately I recovered via a recent Restore of a full backup.

JJ
Post by Dan V
i have a windows 2003 SBS and the server is mainly used as a file server.
exchange has been removed, wsus and sharepoint has also been removed. The
server locks up and no users have access to it every 3 days and i have to
reboot it to get everything to work again. I ran hardware tests and the
hardware is good. I dont know if this error is the reason. Any advice will
be appreciated.
Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13568
Date: 4/13/2010
Time: 8:07:18 PM
User: N/A
Computer: SERVER
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.
Expand HKEY_LOCAL_MACHINE.
"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.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Post by Dan V
I wanted to add that there is only 1 server so should i ignore this ntfrs
message.
Post by Dave Patrick
Something here may help.
http://www.eventid.net/display.asp?eventid=13568&eventno=1743&source=NtFrs&phase=1
--
Regards,
Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
Post by Dan V
I saw that but i dont understand why this was working fine and then all of a
sudden im seeing these errors. Also if i dont have another dc then i dont
need to use replication. Is that correct to say? I opened a command prompt
and ran and restarted the ntfrs service and then i looked at the event log
and no errors showed up.
Loading...