You most likely want to perform a non-authoritative restore of FRS on the DC that's in journal wrap. This shouldn't be confused with a non-authoritative restore of DS.
Basically, you set the Burflags value to D2 on the DC in journal wrap. The DC will then pull in (from a replication partner) the contents of SYSVOL. Check out the article below for details. Also, I would not use the "Enable Journal Wrap Automatic Restore" Registry value mentioned in the Event Log entry. I think it would perform an automatic D2, which may not always be what you want, or at least you may want to have more control of when it occurs. How to Rebuild SYSVOL and Its Content in a Domain http://support.microsoft.com/default.aspx?scid=kb;en-us;315457 Troubleshooting journal_wrap errors on Sysvol and DFS replica sets http://support.microsoft.com/default.aspx?scid=kb;en-us;292438 > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > [EMAIL PROTECTED] > Sent: Monday, June 28, 2004 14:18 > To: [EMAIL PROTECTED] > Subject: [ActiveDir] FRS EventID 13568 > Sensitivity: Private > > Hy, > Any have idea or it happened ? resolve NTFS USN > journal truncated ? The Server is Windows 2000 SP4. > Thanks. > > Event Type: Error > Event Source: NtFrs > Event Category: None > User: N/A > Computer: SERVERNAME > 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:\winnt\sysvol\domain" > Replica root volume is : "\\.\C <file://\\.\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 <file://\\.\C> :" has been formatted. > [2] The NTFS USN journal on volume "\\.\C <file://\\.\C> :" > has been deleted. > [3] The NTFS USN journal on volume "\\.\C <file://\\.\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 <file://\\.\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. > List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
