Problem: NTDS Replication Errors, Due to missing Domain Controller “Event ID: 1864”
Running Windows Server 2003 running as Primary Domain Controller. I have another Windows 2003 server running Exchange 2003 and also a Secondary Domain Controller. Also have a third server which is also Windows 2003 which is a Secondary Domain and Secondary DNS Server.
The following errors occur for SERVER12. SERVER12 is a server I built and then scrapped. I install the domain controller role on the server, but never demoted or removed the role before wiping out the server.
Below is the error I am receiving. I also posted a copy of the results from a DCDIAG on the primary Domain Controller.
What are the best practices for removing SERVER12 from my network so I do not receive these messages again?
————————————-
Event Type: Error
Event Source: NTDS Replication
Event Category: Replication
Event ID: 1864
Date: 12/4/2005
Time: 6:01:27 PM
User: NT AUTHORITYANONYMOUS LOGON
Computer: SERVER0
Description:
This is the replication status for the following directory partition on the local domain controller.
Directory partition:
CN=Schema,CN=Configuration,DC=DOMAIN,DC=local
The local domain controller has not recently received replication information from a number of domain controllers. The count of domain controllers is shown, divided into the following intervals.
More than 24 hours:
1
More than a week:
1
More than one month:
1
More than two months:
0
More than a tombstone lifetime:
0
Tombstone lifetime (days):
60
Domain controllers that do not replicate in a timely manner may encounter errors. It may miss password changes and be unable to authenticate. A DC that has not replicated in a tombstone lifetime may have missed the deletion of some objects, and may be automatically blocked from future replication until it is reconciled.
To identify the domain controllers by name, install the support tools included on the installation CD and run dcdiag.exe.
You can also use the support tool repadmin.exe to display the replication latencies of the domain controllers in the forest. The command is “repadmin /showvector /latency “.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
————————————-
————————————-
Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.
P:>dcdiag
Domain Controller Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-SiteSERVER0
Starting test: Connectivity
……………………. SERVER0 passed test Connectivity
Doing primary tests
Testing server: Default-First-SiteSERVER0
Starting test: Replications
[Replications Check,SERVER0] A recent replication attempt failed:
From SERVER12 to SERVER0
Naming Context: CN=Schema,CN=Configuration,DC=DOMAIN,DC=local
The replication generated an error (1722):
The RPC server is unavailable.
The failure occurred at 2005-12-05 09:46:37.
The last success occurred at 2005-11-02 15:48:28.
788 failures have occurred since the last success.
[SERVER12] DsBindWithSpnEx() failed with error 1722,
The RPC server is unavailable..
The source remains down. Please check the machine.
[Replications Check,SERVER0] A recent replication attempt failed:
From SERVER12 to SERVER0
Naming Context: CN=Configuration,DC=DOMAIN,DC=local
The replication generated an error (1722):
The RPC server is unavailable.
The failure occurred at 2005-12-05 09:46:16.
The last success occurred at 2005-11-02 15:49:17.
788 failures have occurred since the last success.
The source remains down. Please check the machine.
[Replications Check,SERVER0] A recent replication attempt failed:
From SERVER12 to SERVER0
Naming Context: DC=DOMAIN,DC=local
The replication generated an error (1722):
The RPC server is unavailable.
The failure occurred at 2005-12-05 09:45:55.
The last success occurred at 2005-11-02 16:08:40.
788 failures have occurred since the last success.
The source remains down. Please check the machine.
REPLICATION-RECEIVED LATENCY WARNING
SERVER0: Current time is 2005-12-05 09:47:37.
CN=Schema,CN=Configuration,DC=DOMAIN,DC=local
Last replication recieved from SERVER12 at 2005-11-02 15:58:42.
CN=Configuration,DC=DOMAIN,DC=local
Last replication recieved from SERVER12 at 2005-11-02 15:58:42.
DC=DOMAIN,DC=local
Last replication recieved from SERVER12 at 2005-11-02 16:08:43.
……………………. SERVER0 passed test Replications
Starting test: NCSecDesc
……………………. SERVER0 passed test NCSecDesc
Starting test: NetLogons
……………………. SERVER0 passed test NetLogons
Starting test: Advertising
……………………. SERVER0 passed test Advertising
Starting test: KnowsOfRoleHolders
……………………. SERVER0 passed test KnowsOfRoleHolders
Starting test: RidManager
……………………. SERVER0 passed test RidManager
Starting test: MachineAccount
……………………. SERVER0 passed test MachineAccount
Starting test: Services
……………………. SERVER0 passed test Services
Starting test: ObjectsReplicated
……………………. SERVER0 passed test ObjectsReplicated
Starting test: frssysvol
……………………. SERVER0 passed test frssysvol
Starting test: frsevent
There are warning or error events within the last 24 hours after the
SYSVOL has been shared. Failing SYSVOL replication problems may cause
Group Policy problems.
……………………. SERVER0 failed test frsevent
Starting test: kccevent
……………………. SERVER0 passed test kccevent
Starting test: systemlog
……………………. SERVER0 passed test systemlog
Starting test: VerifyReferences
……………………. SERVER0 passed test VerifyReferences
Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
……………………. ForestDnsZones passed test CrossRefValidation
Starting test: CheckSDRefDom
……………………. ForestDnsZones passed test CheckSDRefDom
Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
……………………. DomainDnsZones passed test CrossRefValidation
Starting test: CheckSDRefDom
……………………. DomainDnsZones passed test CheckSDRefDom
Running partition tests on : Schema
Starting test: CrossRefValidation
……………………. Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
……………………. Schema passed test CheckSDRefDom
Running partition tests on : Configuration
Starting test: CrossRefValidation
……………………. Configuration passed test CrossRefValidation
Starting test: CheckSDRefDom
……………………. Configuration passed test CheckSDRefDom
Running partition tests on : SERVER
Starting test: CrossRefValidation
……………………. DOMAIN passed test CrossRefValidation
Starting test: CheckSDRefDom
……………………. DOMAIN passed test CheckSDRefDom
Running enterprise tests on : SERVER.local
Starting test: Intersite
……………………. DOMAIN.local passed test Intersite
Starting test: FsmoCheck
……………………. DOMAIN.local passed test FsmoCheck
P:>
————————————-
Solution : NTDS Replication Errors, Due to missing Domain Controller “Event ID: 1864”
First, clean out your AD:
How to remove data in Active Directory after an unsuccessful domain controller demotion
http://support.microsoft.com/?kbid=216498
Then check AD Sites and Services, if the old server still shows up.
