Event ID 1863 and 1864 after in-place DC refresh from 2008 R2 to 2012

our environment quite simple, have 3 dcs , 1 site.

dc1 (fsmo holder)

dc2

dc3

they 2008 r2 servers dfl , ffl both on 2008 r2. have been upgrading 1 @ time server 2012. when upgrade, building brand new server 2012 cutting old server on , renaming/re-iping new server match old server. following similar steps provided here: http://msmvps.com/blogs/acefekay/archive/2010/10/09/remove-an-old-dc-and-introduce-a-new-dc-with-the-same-name-and-ip-address.aspx

immediately after moving dc3 2012, started receiving 3 errors per day under directory service event log. event id 1864 (replication) ,

"this directory server has not received replication information number of directory servers within configured latency interval. "

there 1 event for each of following:

directory partition:

cn=schema,cn=configuration,dc=intra,dc=cas,dc=org

cn=configuration,dc=intra,dc=cas,dc=org

dc=intra,dc=cas,dc=org

interesting enough, after 60 days event went away (i believe our tombstone life set 60 days). past weekend did dc2 , have exact same error 3 times day. time labeled event id 1863 has exact same wording. suspect after 60 days disappear. curious why getting it. can make go away , did wrong? our dcs replicate every 5 minutes , there @ least 10-15 minutes in-between demoting old server (and removing domain) and promoting new one.

when running repadmin /showrepl  - of replications successful.

when running

repadmin /showvector /latency <partition-dn>   (as suggested in error details)

i get:

c:\users\ouruser>repadmin /showvector /latency <our partition-dn info>
caching guids.
..
e11c3ac2-18e7-4eb8-834c-c6670d1f4f8d @ usn     81230 @ time (unknown)
ba407c28-b8ce-449a-89fe-f27b1521ec98 @ usn   1628347 @ time (unknown)
5856b6d1-cd55-43c9-a00e-e3a9ffdf6fe8 @ usn      7799 @ time (unknown)
54457437-3ad4-448a-900d-cdee9386828e @ usn     21734 @ time (unknown)
e8b40225-5392-4a7e-9473-69f6007f0e30 @ usn  25005091 @ time (unknown)
65a00f16-4842-46b1-a4fc-7c63eb53c3d8 @ usn  30991256 @ time 2005-10-27 17:33:58
8e4f8edc-2df5-4d3f-a83e-7fe303dd5bb8 @ usn   3141255 @ time 2007-09-14 16:40:24
378eb54f-bbd1-4f31-8ee0-bb363e3baa54 @ usn   2332345 @ time 2008-12-13 03:09:10
12dafb44-873d-472a-af81-1dcbce83d691 @ usn   3410119 @ time 2011-02-19 12:04:20
e4cdc57d-87a9-44a6-9462-59258377e449 @ usn 134210124 @ time 2011-09-17 20:46:50
6fa89ebc-26d2-439c-b481-4db8c8a1ead0 @ usn 117915771 @ time 2011-09-17 22:09:06
b9f30932-31f3-496d-baa7-e6dba9436373 @ usn  77103549 @ time 2014-02-15 18:32:20
oursite\dc2 (deleted dsa)     @ usn  94389169 @ time 2014-04-19 18:05:39
oursite\dc3                   @ usn   6690499 @ time 2014-04-22 11:46:45
oursite\dc1                   @ usn 127299088 @ time 2014-04-22 11:46:55
oursite\dc2                   @ usn    398281 @ time 2014-04-22 11:46:58

from i've read, information provided static , cannot changed/deleted/cleaned up. once oursite\dc2 (deleted dsa) runs course of being tombstoned , becomes guid listed, think our errors go away.

doesn't demotion take care of metadata have worry about? have suspicion having these issues due keeping same name , ip, not sure went wrong.

 

hi,

can clarify 1 point first of all, demoted original server promoted new server same name of old server? didn't promote rename server did you? 

also can run dcdiag /v , post output both dc's , 1 still on 2003. 

thanks

---

regards,

denis cooper

mcitp ea - mct

help keep forums tidy, if has helped please mark answer

blog: http://www.windows-support.co.uk  twitter:   linkedin:

Windows Server  >  Directory Services