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


we had major storm on weekend caused unexpected shutdown.

i having issue 1 of domain controller event id 13568

the domain controller running windows server 2012 added couple of days ago.

i not have full backup of server yet.

it has gc role on it.

what things should out before attempt enable journal wrap automatic restore , set 1?

would safer demote server , start scratch?

thank reading!

mladen

the file replication service has detected replica set "domain system volume (sysvol share)" in jrnl_wrap_error.

 

 replica set name is    : "domain system volume (sysvol share)"

 replica root path is   : "c:\windows\sysvol\domain"

 replica root volume : "\\.\c:"

 a replica set hits jrnl_wrap_error when record trying read ntfs usn journal not found.  can occur because of 1 of following reasons.

 

 [1] volume "\\.\c:" has been formatted.

 [2] ntfs usn journal on volume "\\.\c:" has been deleted.

 [3] ntfs usn journal on volume "\\.\c:" has been truncated. chkdsk can truncate journal if finds corrupt entries @ end of journal.

 [4] file replication service not running on computer long time.

 [5] file replication service not keep rate of disk io activity on "\\.\c:".

 setting "enable journal wrap automatic restore" registry parameter 1 cause following recovery steps taken automatically recover error state.

 [1] @ first poll, occur in 5 minutes, computer deleted replica set. if not want wait 5 minutes, run "net stop ntfrs" followed "net start ntfrs" restart file replication service.

 [2] @ poll following deletion computer re-added replica set. re-addition trigger full tree sync replica set.

 

warning: during recovery process data in replica tree may unavailable. should reset registry parameter described above 0 prevent automatic recovery making data unexpectedly unavailable if error condition occurs again.

 

to change registry parameter, run regedit.

 

click on start, run , type regedit.

 

expand hkey_local_machine.

click down key path:

   "system\currentcontrolset\services\ntfrs\parameters"

double click on value name

   "enable journal wrap automatic restore"

and update value.

 

if value name not present may add new->dword value function under edit menu item. type value name shown above.

if seems healthy exception of sysvol, shouldn't need demote dc.  presume there must legacy dc's in domain ntfrs in use.  if ever 2008r2 dc's , newer i'd recommend migrating dfs, less prone issues. fix current issue, here options:

1.) walk through process in event, adding registry key restarting service.

2.) otherwise, validate sysvol healthy on 2012 server's replication partners , perform nonauthoritative restore of sysvol (d2) on server. here's link - http://support.microsoft.com/kb/290762/en-us

i helped earlier in week 2012 dc had similar issue walked through option 2 success. either should in business without trouble of repromoting.



Windows Server  >  Directory Services



Comments

Popular posts from this blog

some help on Event 540

WMI Repository 4GB limit - Win 2003 Ent Question

Event ID 1302 (error 1307) DFS replication service encountered an error while writing to the debug log file