The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.

Question

Hi!
I recently took over management of a Windows 2003 domain that had only one domain controller.  I was building a second DC for redundancy and discovered that the SYSVOL share on the original DC is in "JRNL_WRAP_ERROR" after the SYSVOL and NETLOGON
share would not create on the new DC.  This error goes back as far as the log goes back so I don't know how long it has been in this state. 
The message in the event log states to enable "Enable Journal Wrap Automatic Restore" but I found a KB article that says to use the BurFlags key instead. http://support.microsoft.com/kb/290762
Should I run an authoritative restore since I don't have another domain controller with a good SYSVOL?
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.

Answer 1

> The message in the event log states to enable "Enable Journal Wrap
> Automatic Restore" but I found a KB article that says to use the
> BurFlags key instead.
http://support.microsoft.com/kb/290762
>
> Should I run an authoritative restore since I don't have another domain
> controller with a good SYSVOL?
The automatic restore process AFAIK will initiate a D2 restore. And if
there's no other DC, sysvol might be gone.
I really would prefer to have control - this means I would do a D4.
Absolutely I would :)
Martin
Mal ein
GUTES Buch über GPOs lesen?
NO THEY ARE NOT EVIL, if you know what you are doing:
Good or bad GPOs?
And if IT bothers me - coke bottle design refreshment :))