Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Event ID 13568 - Source NTFRS

Status
Not open for further replies.

pjscott13

Technical User
Mar 12, 2008
37
AU
Hi All,

We are running Small Business Server 2003 with no additional DC's. I have been checking the event logs of late for anything out of the ordinary and have just noticed that the following error has appeared in the File Replication Service Log.

This error message only occurs when I restart the server. Do I need to follow the steps as listed in the event? I am a little weary because at this stage we do not have a second DC is anything were to go wrong?

Any help would be greatly appreciated!

Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13568
Date: 24/03/2008
Time: 8:06:17 PM
User: N/A
Computer: SBServer
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
 
Thanks.. I have found plenty of information on this error by searching google etc, but my concern is going through with the resolutions that everyone suggests when we only have the SBS server... there is nothing that the server is replicating with... so:

1.) why are we getting this error message?
2.) if i go through with the troubleshooting steps i have found what problems am I going to be faced with given that we are not replicating with another server? Could I damage our AD and Group Policies? Because if that happens I would have to restore from backup... which is only going to restore the problem!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top