New domain controller not replicating

[Tim Howell]

I have a Windows 2000 domain with one domain controller. Yesterday I
ran dcpromo on a second machine. dcpromo completed, but said that
replication encountered an error, and that replication would be
completed at the next restart. After restarting the machine, however,
replication still does not seem to be happening properly. At the end
of this message I've pasted messages that appear in the event log of
the new DC many times (I've changed the computer names and domain
names. dc1 in the error message is the name of the original DC).

Dcdiag shows both machines passing most tests. The new DC fails the
advertising test (as it hasn't completed an initial replication).
Under the replications test it shows that it is 0.00% complete with
initial replication.

Both machines are SP4.

Any ideas?

Thanks! =)

--TWH

Event Type: Information
Event Source: NTDS Replication
Event Category: (5)
Event ID: 1203
Date: 12/17/2005
Time: 4:18:56 PM
User: Everyone
Computer: AAA-YYYYY
Description:
A schema mismatch encountered while replicating object
DC=..SerialNo-dc1.xxxxx,DC=xxxxx,CN=MicrosoftDNS,CN=System,DC=xxxxx,DC=com
from server bb1015b3-88cb-44b9-8b7e-87dec51f85eb._msdcs.xxxxx.com.
A schema sync has been queued and sync on NC
DC=xxxxx,DC=com will be retried after the schema sync.

Event Type: Information
Event Source: NTDS Replication
Event Category: (5)
Event ID: 1557
Date: 12/17/2005
Time: 4:02:41 PM
User: Everyone
Computer: AAA-YYYYY
Description:
This DRA has never completed a full synchronization of partition
DC=xxxxx,DC=com. It will not be advertised as an
available directory until this condition is met.

This server was recently installed from a source server. Please
verify that that source server is still available to finish providing
data to this system.

The synchronization will be retried.

 

[chriss3 [MVP]]

Ensure that your domain controllers can replicate, this is most time a DNS
issue. Active Directory is depended on DNS to communicate, ensure that all
DCs can resolve FQDN of your Active Directory domain.

Use the command line based tool repadmin within Windows Support Tools (Found
on your Windows CD) to verify the replication health.
Run repadmin with the follow syntax:
repadmin /showreps

--
Regards
Christoffer Andersson
Microsoft MVP - Directory Services


No email replies please - reply in the newsgroup

 

[Tim Howell]

I've pasted the output from repadmin /showreps.

Where do I go from here?

Thanks! =)

--TWH

Here's the output from repadmin /showreps:

C:\Program Files\Support Tools>repadmin /showreps
Fullerton\INK-FULLERTON
DSA Options : (none)
objectGuid : 895bb46c-1486-42a2-ad7b-60f86ac6287e
invocationID: da86ed60-50c1-4489-9a67-b536c3a103cf

==== INBOUND NEIGHBORS ======================================

CN=Schema,CN=Configuration,DC=inkinvitations,DC=com
LaHabra\INK via RPC
objectGuid: bb1015b3-88cb-44b9-8b7e-87dec51f85eb
Last attempt @ 2005-12-19 15:33.53 was successful.

CN=Configuration,DC=inkinvitations,DC=com
LaHabra\INK via RPC
objectGuid: bb1015b3-88cb-44b9-8b7e-87dec51f85eb
Last attempt @ 2005-12-19 15:33.47 was successful.

DC=inkinvitations,DC=com
LaHabra\INK via RPC
objectGuid: bb1015b3-88cb-44b9-8b7e-87dec51f85eb
Last attempt @ 2005-12-19 15:33.53 failed, result 8418:
The replication operation failed because of a schema
mismatch betwee
n the servers involved.
Last success @ (never).
0 consecutive failure(s).

==== OUTBOUND NEIGHBORS FOR CHANGE NOTIFICATIONS ============

CN=Schema,CN=Configuration,DC=inkinvitations,DC=com
LaHabra\INK via RPC
objectGuid: bb1015b3-88cb-44b9-8b7e-87dec51f85eb

 

[Jorge de Almeida Pinto]

Before normal replication succeeds the schema partition must be in sync
between DCs. If a schema (version) mismatch exists, normal replication is
stopped and the replication of the schema partition gains priority as it
will be sync-ed first before other partitions. This could happen just after
a schema upgrade.

You could also try using REPLMON and with that force the replication of the
schema partition to that DC

 

[Jorge de Almeida Pinto]

also take a look at the following:
http://support.microsoft.com/kb/838179/?sd=RMVP&fr=1

 

[Tim Howell]

Well, as far as I know, nothing should have changed the schema on
either machine. Neither has Exchange or other schema-changing software
installed.

How do I use replmon to force the replication?

Thanks! =)

--TWH