NTDS Replication Warning

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

On a recently promoted Win2k DC am receiving the following warning in the
Directory Service Log:

Log: Event Type: Warning
Event Source: NTDS Replication
Event Category: Replication
Event ID: 1586
Date: 10/18/2006
Time: 7:19:01 PM
User: Everyone
Computer: Domain controller
Description:
The checkpoint with the PDC was unsuccessful. The checkpointing process will
be retried again in four hours. A full synchronization of the security
database to downlevel domain controllers may take place if this machine is
promoted to be the PDC before the next successful checkpoint. The error
returned was: The naming context is in the process of being removed or is not
replicated from the specified server.

This computer doesn't have DNS installed on it as yet, but is a GC server.
In its DNS settings, it is presently pointing at the local site DNS server as
preferred, with the secondary DNS server being the FSMO PDC. It's been over
10 hours since I promoted this DC on a small network. Can't figure out whay
it won't checkpoint with the PDC, though I noticed that in the AD Sites and
Services it does not have a replication link with the PDC, while all my other
DCs do.
 
Run diagnostics against your Active Directory domain.

If you don't have the tools installed, install them from your server install
disk.
d:\support\tools\setup.exe

Run dcdiag, netdiag and repadmin in verbose mode.
-> dcdiag /e /c /v /s:DC_Name /f:c:\dcdiag.log
-> netdiag.exe /v > c:\netdiag.log (On each dc)
-> repadmin.exe /showrepl dc* /verbose /all /intersite > c:\repl.txt

If you download a gui script I wrote it should be simple to set and run
(DCDiag and NetDiag). It also has the option to run individual tests
without having to learn all the switch options. The details will be output
in notepad text files that pop up automagically.

The script is located in the download section on my website at
http://www.pbbergs.com

Just select both dcdiag and netdiag make sure verbose is set. (Leave the
default settings for dcdiag as set when selected)

When complete search for fail, error and warning messages.


--
Paul Bergson
MVP - Directory Services
MCT, MCSE, MCSA, Security+, BS CSci
2003, 2000 (Early Achiever), NT

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.
 
Ran a ton of diagnostics: dcdiag, netdiag, repadmin, replmon, etc., and they
all came up without any errors, including DNS, replications, etc.. Have never
had replication issues, just the PDC checkpoint. But I did notice there was
no direct replication link between the PDC and the problem DC.

What did the trick:

The Microsoft literature recommends building a connection object to the PDC
and from the PDC to the problem child DC. That way they "both" have
ostensible inbound replication connections, one from the other. It actually
shows up that way in Repadmin commands. Long story short, so far the new
connection objects have corrected the problem and caused the warnings to
disappear.

My Win2k domain is not running in native mode, though it should be.
 
Cybersteve said:
What did the trick:

The Microsoft literature recommends building a connection object to the PDC
and from the PDC to the problem child DC. That way they "both" have
ostensible inbound replication connections, one from the other. It actually
shows up that way in Repadmin commands. Long story short, so far the new
connection objects have corrected the problem and caused the warnings to
disappear.
Click to expand...

Could you tell me how you did this? I'm having the same problem but I have
no idea how to implement your solution. Thanks!
 
Ron Hinds said:
Could you tell me how you did this? I'm having the same problem but I have
no idea how to implement your solution. Thanks!
Click to expand...

Disregard - I figured it out. Thanks anyway!
 
Ron -

I think this problem is a throwback to the old days when Win2k DC networks
had a lot of NT BDCs around who needed to checkpoint with the NT PDCs. It's
almost if the Win2k DCs suffer from a bit of NT genetic imprinting.
 
Back
Top