capflash
asked on
Event ID:13568 The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.
Every time the server is restarted we get this error. We are using a SBS2003 1 DC only. We are running SP2 on the SBS2003.
I have searched here and on the web and everyone seems to have something different to say.
Some say disable FRS and dont worry about it. Other say to do like it says in the notes below and that will fix the problem.
What is the solution and is their any chance there will be data loss?
Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13568
Date: 11/16/2007
Time: 7:41:15 PM
User: N/A
Computer: CHOICE
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\
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.
I have searched here and on the web and everyone seems to have something different to say.
Some say disable FRS and dont worry about it. Other say to do like it says in the notes below and that will fix the problem.
What is the solution and is their any chance there will be data loss?
Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13568
Date: 11/16/2007
Time: 7:41:15 PM
User: N/A
Computer: CHOICE
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\
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.
ASKER
The link provided only takes me back here. Please resubmit.
Sorry, I pasted the wrong link. But I'll tell you what... instead of me giving you just ONE identical question, how about getting all of them...
http://snipr.com/1tsmv
Had you searched the site for the error message you got, you would have found them as well.
Jeff
TechSoEasy
http://snipr.com/1tsmv
Had you searched the site for the error message you got, you would have found them as well.
Jeff
TechSoEasy
ASKER
Yes, If you read the first couple of sentences you will see that I have searched both the web and here.
As restated from the initial post.
Some say disable FRS and dont worry about it. Other say to do like it says in the notes below and that will fix the problem.
With so many people having the same issues and many different responces I am not sure which way to go.
What is the correct solution and is there any chance there will be data loss?
Some report that they cannot login into the server after doing the fix with one DC. Some say it takes a couple of minutes and others a while. Some say they have lost data other have not. Some say the fix works and others does not.
Have you any experiance with this error yourself and what was the outcome?
With only 1 DC why is this service even running and is it safe to just turn off?
As restated from the initial post.
Some say disable FRS and dont worry about it. Other say to do like it says in the notes below and that will fix the problem.
With so many people having the same issues and many different responces I am not sure which way to go.
What is the correct solution and is there any chance there will be data loss?
Some report that they cannot login into the server after doing the fix with one DC. Some say it takes a couple of minutes and others a while. Some say they have lost data other have not. Some say the fix works and others does not.
Have you any experiance with this error yourself and what was the outcome?
With only 1 DC why is this service even running and is it safe to just turn off?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
What do you update the value to?
As it states in the error:
"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."
Jeff
TechSoEasy
"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."
Jeff
TechSoEasy
Jeff
TechSoEasy