Scenario:
DC1 / Windows Server 2016 (ver 1607 GUI)
DC2 / Windows Server 2016 (ver 1607 GUI)
This domain have migrated from server 2000 > 2003 > 2008 > 2016 , Same name/ip have been used after migratrion and metadata cleanup have done properly
All servers / clients are on same single subnet with 1 G network connectivity, no delay no timeouts.
in DC1 > Event viewer > Directory Services , I am seeing following errors on a daily basis
Error: 1863
This is the replication status for the following directory partition on this directory server.
Directory partition:
DC=ForestDnsZones,DC=MYDOMAIN
This directory server has not received replication information from a number of directory servers within the configured latency interval.
Latency Interval (Hours):
24
Number of directory servers in all sites:
1
Number of directory servers in this site:
1
The latency interval can be modified with the following registry key.
Registry Key:
HKLM\System\CurrentControlSet\Services\NTDS\Parameters\Replicator latency error interval (hours)
To identify the directory servers by name, use the dcdiag.exe tool.
You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency <partition-dn>".
& same errors with
Directory partition:CN=Schema,CN=Configuration,
DC=MYDOMAIN
Directory partition:
DC=MYDOMAIN
I have Attached DC1 diagnostic log which contain all the test results
-
dcdiag /s:DC1 /v
-
repadmin /showrepl
-
repadmin /replsummary
-
dcdiag /test:dfsrevent
-
DCDiag /Test:DNS
-
NET SHARE
-
gpotool /verbose
How can I sort this? Kindly advise.
Best Answer
We got the same problem, error 1863 or error 1864. What we did:
All checks I made were ok, no error was triggered. I did not understand why?
My thoughts: Now we have old Objects with the same name, but they are out of sync (and thats ok, they are removed).
I think its a bug, and I thing the matching was done by the name and not the ID of the object.
The object will be delete by the Tombstone lifetime, I decresed the value (adsiedit -> configuration) (was immediated transferred to alle DCs, so they are in sync).
The result of this is, that the Object is gone and only the ID availible any more.
Now the error has disappeared.
Reset the Tombstonelifetime to 180 days.