Event ID: 13568 (DC1) & Event ID: 13555/13552 (DC2)
we have tusdc01 (dc #1) , tusdc02 (dc #2) both machines running w2k3 sp2. tusdc01 , tusdc02 errors listed below in following sections.
********************************************************************************
tusdc01
********************************************************************************
event type: error
event source: ntfrs
event category: none
event id: 13568
date: 1/12/2011
time: 9:38:19 am
user: n/a
computer: tusdc01
description:
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. this 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.
for more information, see , support center @ http://go.microsoft.com/fwlink/events.asp.
********************************************************************************
tusdc02
********************************************************************************
event type: error
event source: ntfrs
event category: none
event id: 13555
date: 1/12/2011
time: 10:02:57 am
user: n/a
computer: tusdc02
description:
the file replication service in error state. files not replicate or 1 or of replica sets on computer until following recovery steps performed:
recovery steps:
[1] error state may clear if stop , restart frs service. can done performing following in command window:
net stop ntfrs
net start ntfrs
if fails clear problem proceed follows.
[2] active directory domain controllers not host dfs alternates or other replica sets replication enabled:
if there @ least 1 other domain controller in domain restore "system state" of dc backup (using ntbackup or other backup-restore utility) , make non-authoritative.
if there no other domain controllers in domain restore "system state" of dc backup (using ntbackup or other backup-restore utility) , choose advanced option marks sysvols primary.
if there other domain controllers in domain of them have event log message restore 1 of them primary (data files primary replicate everywhere) , others non-authoritative.
[3] active directory domain controllers host dfs alternates or other replica sets replication enabled:
(3-a) if dfs alternates on dc not have other replication partners copy data under dfs share safe location.
(3-b) if server active directory domain controller domain then, before going (3-c), make sure server not have inbound or outbound connections other servers formerly domain controllers domain off net (and never coming online) or have been fresh installed without being demoted. delete connections use sites , services snapin ,
sites->name_of_site->servers->name_of_server->ntds settings->connections.
(3-c) restore "system state" of dc backup (using ntbackup or other backup-restore utility) , make non-authoritative.
(3-d) copy data step (3-a) above original location after sysvol share published.
[4] other windows servers:
(4-a) if of dfs alternates or other replica sets hosted server not have other replication partners copy data under share or replica tree root safe location.
(4-b) net stop ntfrs
(4-c) rd /s /q c:\windows\ntfrs\jet
(4-d) net start ntfrs
(4-e) copy data step (4-a) above original location after service has initialized (5 minutes safe waiting time).
note: if error message in eventlog of members of particular replica set perform steps (4-a) , (4-e) above on 1 of members.
for more information, see , support center @ http://go.microsoft.com/fwlink/events.asp.
event type: error
event source: ntfrs
event category: none
event id: 13552
date: 1/12/2011
time: 10:40:39 am
user: n/a
computer: tusdc02
description:
the file replication service unable add computer following replica set:
"domain system volume (sysvol share)"
this caused number of problems such as:
-- an invalid root path,
-- a missing directory,
-- a missing disk volume,
-- a file system on volume not support ntfs 5.0
the information below may resolve problem:
computer dns name "tusdc02.naustusp2.tus.michelin.com"
replica set member name "tusdc02"
replica set root path "c:\windows\sysvol\domain"
replica staging directory path "c:\windows\sysvol\staging\domain"
replica working directory path "c:\windows\ntfrs\jet"
windows error status code is
frs error status code frserrormismatchedjournalid
other event log messages may determine problem. correct problem , service attempt restart replication automatically @ later time.
for more information, see , support center @ http://go.microsoft.com/fwlink/events.asp.
found information via google indicated ntfrs jet database possibly corrupted @ http://www.eventid.net/display.asp?eventid=13555&eventno=572&source=ntfrs&phase=1 in relation 13552/13555 excluded c:\windows\ntfrs folder tree savce scans on both tusdc01 , tusdc02 first. other thing noticed both dc’s @ w2k3 sp1 not sp2 upgraded tusdc02 first sp2 retest.
joe
since others mentioned doing tusdc01 authoritative restore (d4) tried first after power-off of tusdc02 , verified tusdc01 operations master fsmo roles. found tusdc01 missing it's sysvol\policies & scripts folders/files after d4 restore previous d2 restore created c:\windows\sysvol\sysvol\naustusp2.tus.michelin.com\ntfrs_preexisting see eventlog folder/files sysvol folder. still didn’t start replication tusdc02->tusdc01 powered-on tusdc02 , did non-authoritative (d2) restore , restarted ntfrs service , on tusdc01 showing event id 13509 (the file replication service has enabled replication tusdc02 tusdc01 c:\windows\sysvol\domain after repeated retries.) , event id 13516 on both dc’s. did ntfrs stop/start on both tusdc01/tusdc02 see events occur now.
ran following scripts on both tusdc01/tusdc02 see current health:
dcdiag /v /c /d /e /s:dcname >c:\dcdiag.txt
repadmin /showrepl dc* /verbose /all /intersite >c:\repl.txt
i did quick ntfrs replication test creating joe.bat in \\tusdc01\sysvol\naustusp2.tus.michelin.com\scripts folder , watching see if auto-created on \\tusdc02\sysvol\naustusp2.tus.michelin.com\scripts , , vice-versa. logged tustbl2 , verified domain logon had no event entries or sluggishness , ok.
found in dcdiag run did above i’m missing netlogin share (normally in c:\windows\sysvol\sysvol\<domain>\scripts). so, on tusdc01 restarted net logon service , saw netlogon share on tusdc01 re-created , ntfrs replicated netlogon share tusdc02 automatically. in dcdiag logs see test “netlogons” succeeding now.
Windows Server > Directory Services
Comments
Post a Comment