File replication service in journal wrap on 2003 dc and no replication has occured to new 2008 dc...

i have 2003 domain added new 2008 dc. (first one.) went far concerned , proceeded move fsmo roles new dc. want remove 2003 dc domain noticed exchange server have (seperate box) not talking correctly domain though still seems work @ present...

log name:      application
source:        msexchange adaccess
date:          19/09/2011 11:49:52
event id:      2114
task category: topology
level:         error
keywords:      classic
user:          n/a
computer:      exchange.domain.internal
description:
process store.exe (pid=4216). topology discovery failed, error 0x80040a02 (dsc_e_no_suitable_cdc). lightweight directory access protocol (ldap) error code specified in event description. this, use microsoft knowledge base article 218185, "microsoft ldap error codes." use information in article learn more cause , resolution error. use ping or pathping command-line tools test network connectivity local domain controllers.
event xml:
<event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <system>
    <provider name="msexchange adaccess" />
    <eventid qualifiers="49156">2114</eventid>
    <level>2</level>
    <task>3</task>
    <keywords>0x80000000000000</keywords>
    <timecreated systemtime="2011-09-19t10:49:52.000z" />
    <eventrecordid>154297</eventrecordid>
    <channel>application</channel>
    <computer>exchange.domain.internal</computer>
    <security />
  </system>
  <eventdata>
    <data>store.exe</data>
    <data>4216</data>
    <data>80040a02</data>
    <data>dsc_e_no_suitable_cdc</data>
  </eventdata>
</event>

log name:      application
source:        msexchange adaccess
date:          19/09/2011 11:49:52
event id:      2080
task category: topology
level:         information
keywords:      classic
user:          n/a
computer:      exchange.shape.internal
description:
process store.exe (pid=4216). exchange active directory provider has discovered following servers following characteristics:
 (server name | roles | enabled | reachability | synchronized | gc capable | pdc | sacl right | critical data | netlogon | os version)
in-site:
2008dc.domain.internal cdg 1 7 7 1 0 1 1 0 1
2003dc.domain.internal --g 1 1 7 1 0 1 1 7 1
 out-of-site:
 
event xml:
<event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <system>
    <provider name="msexchange adaccess" />
    <eventid qualifiers="16388">2080</eventid>
    <level>4</level>
    <task>3</task>
    <keywords>0x80000000000000</keywords>
    <timecreated systemtime="2011-09-19t10:49:52.000z" />
    <eventrecordid>154296</eventrecordid>
    <channel>application</channel>
    <computer>exchange.domain.internal</computer>
    <security />
  </system>
  <eventdata>
    <data>store.exe</data>
    <data>4216</data>
    <data>2008dc.domain.internal cdg 1 7 7 1 0 1 1 0 1
2003dc.domain.internal --g 1 1 7 1 0 1 1 7 1
</data>
    <data>
    </data>
  </eventdata>
</event>

in troubleshooting noticed sysvol , netlogon shares had not replicated 2008 dc:

log name:      file replication service
source:        ntfrs
date:          18/09/2011 03:36:01
event id:      13508
task category: none
level:         warning
keywords:      classic
user:          n/a
computer:     2008dc.domain.internal
description:
file replication service having trouble enabling replication 2003dc to 2008dc c:\windows\sysvol\domain using dns name 2003dc.domain.internal. frs keep retrying.
 following of reasons see warning.
 
 [1] frs can not correctly resolve dns name 2003dc.domain.internal computer.
 [2] frs not running on 2003dc.domain.internal.
 [3] topology information in active directory domain services replica has not yet replicated domain controllers.
 
 this event log message appear once per connection, after problem fixed see event log message indicating connection has been established.
event xml:
<event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <system>
    <provider name="ntfrs" />
    <eventid qualifiers="32768">13508</eventid>
    <level>3</level>
    <task>0</task>
    <keywords>0x80000000000000</keywords>
    <timecreated systemtime="2011-09-18t02:36:01.000z" />
    <eventrecordid>479</eventrecordid>
    <channel>file replication service</channel>
    <computer>2008dc.domain.internal</computer>
    <security />
  </system>
  <eventdata>
    <data>2003dc</data>
    <data>2008dc</data>
    <data>c:\windows\sysvol\domain</data>
    <data>2003dc.domain.internal</data>
    <binary>d5040000</binary>
  </eventdata>
</event>

 i looked on 2003 dc , noticed frs service not running. started , following error:

event type: error
event source: ntfrs
event category: none
event id: 13568
date:  14/09/2011
time:  20:19:09
user:  n/a
computer: 2003dc
description:
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.
 
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"
, 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.

researching online has lead me 2 options:

1. above regedit on 2003dc , see happens....
2.  reset burflags, either autoritively or non-authoritively in http://support.microsoft.com/kb/290762

i not sure way proceed. can assist? thanks,

 

 

hello,

it seems use exchange 2003, make sure exchange 2003 sp2 is installed must windows server 2008 dcs use them.

for mentioned "jrnl_wrap_error" see: http://social.technet.microsoft.com/forums/en/winserverds/thread/1a29d21e-2779-46b4-a015-94b5d4f915a6

---

best regards meinolf weber disclaimer: posting provided "as is" no warranties or guarantees , , confers no rights.

Windows Server  >  Directory Services