Windows Server

CO-DBA-SC-EL · Guest

What does this mean? None of the causes listed could have caused by any
admin or user action. Is this system just bent on corrupting itself? The
explanation and the prompt as to what to do are confusing to say the least.
This is a SBS 2003 Standard server, SP1 installed a couple of weeks ago, no
other server in domain, just 3 client computers.

C_O

Source=NtFrs Evend ID=13568 Last Occurence 7/29/2005 7:55 PM Total
Occurrences 2

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.

Susan Bradley, CPA aka Eb · Guest

Did you check out www.eventid.net for that error?

Dave Nickason [SBS MVP] · Guest

The instructions for fixing this are right in the error info you posted
below. I'm not sure how Microsoft defines "a long time" but maybe this
happened during the mystery 140 minutes.

CO-DBA-SC-EL · Guest

Thanks, Susan, but all I find there is ever more confused "explanations" for
what is clearly an intermittent bug dating back to Win2K server.

I could make the error repeat reliably with
net stop ntfrs
net start ntfrs
(wait 2 minutes, then the same event occurs)

So... I followed the steps listed (added nonexistent flag in the registry,
stop/start ntfrs). Got some scary warnings. Changed the registry entry back
to 0, stop/start ntfrs, got info event 13516 saying "
The File Replication Service is no longer preventing the computer SNJWHQ
from becoming a domain controller. The system volume has been successfully
initialized and the Netlogon service has been notified that the system
volume is now ready to be shared as SYSVOL. "

Black magic...

-- Claude

line47 · Joined: 21 Feb 2006 Posts: 1

NTFRS 13568 on SBS2003 Standard single DC/Server

Hi CO-DBA-SC-EL and Susan,

I'm confused.
We have only 1 SBS2003 Standard server and 10 workstations on our LAN.

I have the exact problem and our server goes down or hangs each day, probably because of this problem. Login on is only possible after reboot.
I would like to know if you permanently fixed this problem by the solution suggested in the error report.
Should i put the value of the journal wrap registry key to 1 or 0 or put it to 1 first, reboot and change it back to 0?
Plze help.

Thanx in advance, Line.

	Windows Server Forum Index -> Small Business Server 2003	All times are GMT
Page 1 of 1