Notes

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
======Event ID 13568======
Ik had een Domain Controller die na een "dirty" shutdown op kwam met de volgende melding in het File Replication event log:
<code>
Event Type:	Error
Event Source:	NtFrs
Event Category:	None
Event ID:	13568
Date:		13-1-2009
Time:		17:27:47
User:		N/A
Computer:	DC-01
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 http://go.microsoft.com/fwlink/events.asp.
</code>

Volgens de event log melding en [[http://support.microsoft.com/kb/292438/|KB292438]] kun je dit oplossen door te rommelen aan de "Enable Journal Wrap Automatic Restore" en "Ntfs Journal size in MB" registry keys. De "Enable Journal Wrap Automatic Restore" key werd ook gebruikt in de blogpost [[http://msmvps.com/blogs/bradley/archive/2007/12/26/fixing-a-little-bit-of-journal-wrap.aspx|SBS Diva Blog - Fixing a little bit of Journal Wrap]], maar zij kwam in een latere blogpost getiteld [[http://msmvps.com/blogs/bradley/archive/2007/12/27/help-i-ve-lost-my-sysvol-and-can-t-get-up.aspx|SBS Diva Blog - Help, I've lost my SYSVOL and can't get up....]] met de melding dat dit waarschijnlijk toch niet verstandig was aangezien waarschijnlijk als gevolg hiervan de group policies vreemd gingen doen. Een persoon in de comments adviseerde, net zoals in haar vorige post, de BurFlags key: \\
<file>
# re: Help, I've lost my SYSVOL and can't get up.... 
Saturday, December 29, 2007 8:23 PM by Pedro R. 

Hi again Susan.
I'm back to mentioning the use of the Burflags key to fix Journal Wrap Errors instead of "Enable Journal Wrap Automatic Restore". This technique also prevents you from seing the kind of errors you mention here (SYSVOL becoming empty).
Using "Enable Journal Wrap Automatic Restore" will make NTFRS reinitialize all NTFRS shares and delete all contents in those shares (a very aggressive approach).
Instead, just use the "Burflags" key and set it to "D4" and restart NTFRS. You will see it heal itself and yet, SYSVOL and NETLOGON will still be intact after the restore ;)
If it's the only DC in the network then I would go ahead with Burflags set to D4. If there is more than one DC you may wnat to set Burflags do D2.
In any case check out the official docs: "Using the BurFlags registry key to reinitialize File Replication Service replica sets" at http://support.microsoft.com/kb/290762/en-us

happy new year!!
</file>

Uiteindelijk opgelost door de ntfrs service te stoppen, de BurFlags key op D2 (non-authoritative restore, zie [[http://support.microsoft.com/kb/290762/|KB290762]], twee andere DC's waren beschikbaar om vanaf te synchroniseren) te zetten en de ntfrs service weer te starten. \\

Zie ook: \\
[[http://technet.microsoft.com/en-us/library/bb727056.aspx|Microsoft TechNet - Troubleshooting File Replication Service]] \\
[[http://www.tomshardware.co.uk/forum/190748-36-event-13568|Tom's Hardware - Forums - Event ID: 13568]] \\
[[http://www.petri.co.il/forums/archive/index.php/t-19311.html|Petri.co.il forums - NTFRS error ID 13568 (abit log)]] \\
[[http://forums.techarena.in/active-directory/968115.htm|TechArena forums - Enable Journal Wrap to fix Event ID 13568 on Win 2003?]] \\