Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

replication issues

Status
Not open for further replies.

weinmatt

IS-IT--Management
Dec 30, 2004
113
US
I have multiple locations all connected via ptp t1s.

I have a PDC running in the central location with DC's at each satallite location.

One locations dv decided to stop replicating. When i tried to force it i got the tombstone time as expired.

Now when i try i get the target principal name is incorrect.

Here are the dc diag results for each server. The first one listed is the main PDC.

If anyone can offer some help that would be great. Thanks.

Mgg-dc-pdc dcdiag

C:\Documents and Settings\orkinman>dcdiag

Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site\MGG-DC-PDC
Starting test: Connectivity
......................... MGG-DC-PDC passed test Connectivity

Doing primary tests

Testing server: Default-First-Site\MGG-DC-PDC
Starting test: Replications
[Replications Check,MGG-DC-PDC] A recent replication attempt failed:
From MGG-DC-CAM to MGG-DC-PDC
Naming Context: DC=ForestDnsZones,DC=metrogastro,DC=com
The replication generated an error (8418):
The replication operation failed because of a schema mismatch betwee
n the servers involved.
The failure occurred at 2006-11-05 10:46:19.
The last success occurred at 2006-06-02 07:56:25.
3408 failures have occurred since the last success.
[Replications Check,MGG-DC-PDC] A recent replication attempt failed:
From MGG-DC-CAM to MGG-DC-PDC
Naming Context: DC=DomainDnsZones,DC=metrogastro,DC=com
The replication generated an error (8418):
The replication operation failed because of a schema mismatch betwee
n the servers involved.
The failure occurred at 2006-11-05 10:46:18.
The last success occurred at 2006-09-21 00:50:31.
25 failures have occurred since the last success.
[Replications Check,MGG-DC-PDC] A recent replication attempt failed:
From MGG-DC-CAM to MGG-DC-PDC
Naming Context: CN=Configuration,DC=metrogastro,DC=com
The replication generated an error (8418):
The replication operation failed because of a schema mismatch betwee
n the servers involved.
The failure occurred at 2006-11-05 10:46:18.
The last success occurred at 2006-09-21 00:50:30.
30 failures have occurred since the last success.
REPLICATION LATENCY WARNING
ERROR: Expected notification link is missing.
Source MGG-DC-CAM
Replication of new changes along this path will be delayed.
This problem should self-correct on the next periodic sync.
[Replications Check,MGG-DC-PDC] A recent replication attempt failed:
From MGG-DC-CAM to MGG-DC-PDC
Naming Context: DC=metrogastro,DC=com
The replication generated an error (8418):
The replication operation failed because of a schema mismatch betwee
n the servers involved.
The failure occurred at 2006-11-05 10:49:10.
The last success occurred at 2006-06-02 07:56:24.
3596 failures have occurred since the last success.
REPLICATION LATENCY WARNING
ERROR: Expected notification link is missing.
Source MGG-DC-CAM
Replication of new changes along this path will be delayed.
This problem should self-correct on the next periodic sync.
REPLICATION-RECEIVED LATENCY WARNING
MGG-DC-PDC: Current time is 2006-11-05 11:31:36.
DC=ForestDnsZones,DC=metrogastro,DC=com
Last replication recieved from MGG-DC-CAM at 2006-06-02 07:56:25.

WARNING: This latency is over the Tombstone Lifetime of 60 days!

DC=DomainDnsZones,DC=metrogastro,DC=com
Last replication recieved from MGG-DC-CAM at 2006-09-21 00:50:31.

CN=Configuration,DC=metrogastro,DC=com
Last replication recieved from MGG-DC-CAM at 2006-09-21 00:50:30.

DC=metrogastro,DC=com
Last replication recieved from MGG-DC-CAM at 2006-06-02 07:56:24.

WARNING: This latency is over the Tombstone Lifetime of 60 days!

......................... MGG-DC-PDC passed test Replications
Starting test: NCSecDesc
......................... MGG-DC-PDC passed test NCSecDesc
Starting test: NetLogons
......................... MGG-DC-PDC passed test NetLogons
Starting test: Advertising
......................... MGG-DC-PDC passed test Advertising
Starting test: KnowsOfRoleHolders
......................... MGG-DC-PDC passed test KnowsOfRoleHolders
Starting test: RidManager
......................... MGG-DC-PDC passed test RidManager
Starting test: MachineAccount
......................... MGG-DC-PDC passed test MachineAccount
Starting test: Services
......................... MGG-DC-PDC passed test Services
Starting test: ObjectsReplicated
......................... MGG-DC-PDC passed test ObjectsReplicated
Starting test: frssysvol
......................... MGG-DC-PDC passed test frssysvol
Starting test: frsevent
......................... MGG-DC-PDC passed test frsevent
Starting test: kccevent
......................... MGG-DC-PDC passed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0xC0002719
Time Generated: 11/05/2006 11:00:03
(Event String could not be retrieved)
An Error Event occured. EventID: 0xC0002719
Time Generated: 11/05/2006 11:00:57
(Event String could not be retrieved)
An Error Event occured. EventID: 0xC0002719
Time Generated: 11/05/2006 11:01:51
(Event String could not be retrieved)
An Error Event occured. EventID: 0xC0002719
Time Generated: 11/05/2006 11:02:45
(Event String could not be retrieved)
......................... MGG-DC-PDC failed test systemlog
Starting test: VerifyReferences
......................... MGG-DC-PDC passed test VerifyReferences

Running partition tests on : TAPI3Directory
Starting test: CrossRefValidation
......................... TAPI3Directory passed test CrossRefValidation

Starting test: CheckSDRefDom
......................... TAPI3Directory passed test CheckSDRefDom

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 : metrogastro
Starting test: CrossRefValidation
......................... metrogastro passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... metrogastro passed test CheckSDRefDom

Running enterprise tests on : metrogastro.com
Starting test: Intersite
......................... metrogastro.com passed test Intersite
Starting test: FsmoCheck
......................... metrogastro.com passed test FsmoCheck

Mgg-dc-cam dcdiag

Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site\MGG-DC-CAM
Starting test: Connectivity
......................... MGG-DC-CAM passed test Connectivity

Doing primary tests

Testing server: Default-First-Site\MGG-DC-CAM
Starting test: Replications
[Replications Check,MGG-DC-CAM] A recent replication attempt failed:
From MGG-CC-BDC to MGG-DC-CAM
Naming Context: DC=metrogastro,DC=com
The replication generated an error (-2146893022):
The target principal name is incorrect.
The failure occurred at 2006-11-05 10:58.12.
The last success occurred at 2006-02-13 16:02.41.
46450 failures have occurred since the last success.
[MGG-CC-BDC] DsBind() failed with error -2146893022,
The target principal name is incorrect..
[Replications Check,MGG-DC-CAM] A recent replication attempt failed:
From MGG-DC-PDC to MGG-DC-CAM
Naming Context: DC=metrogastro,DC=com
The replication generated an error (-2146893022):
The target principal name is incorrect.
The failure occurred at 2006-11-05 10:58.12.
The last success occurred at 2006-02-13 16:09.01.
317478 failures have occurred since the last success.
[MGG-DC-PDC] DsBind() failed with error -2146893022,
The target principal name is incorrect..
[Replications Check,MGG-DC-CAM] A recent replication attempt failed:
From MGG-DC-PDC to MGG-DC-CAM
Naming Context: CN=Configuration,DC=metrogastro,DC=com
The replication generated an error (-2146893022):
The target principal name is incorrect.
The failure occurred at 2006-11-05 10:58.11.
The last success occurred at 2006-02-13 16:05.18.
3675 failures have occurred since the last success.
[Replications Check,MGG-DC-CAM] A recent replication attempt failed:
From MGG-CC-BDC to MGG-DC-CAM
Naming Context: CN=Configuration,DC=metrogastro,DC=com
The replication generated an error (-2146893022):
The target principal name is incorrect.
The failure occurred at 2006-11-05 10:58.11.
The last success occurred at 2006-02-13 16:05.54.
3669 failures have occurred since the last success.
[Replications Check,MGG-DC-CAM] A recent replication attempt failed:
From MGG-CC-BDC to MGG-DC-CAM
Naming Context: CN=Schema,CN=Configuration,DC=metrogastro,DC=com
The replication generated an error (-2146893022):
The target principal name is incorrect.
The failure occurred at 2006-11-05 10:58.12.
The last success occurred at 2006-02-13 15:50.41.
2251 failures have occurred since the last success.
[Replications Check,MGG-DC-CAM] A recent replication attempt failed:
From MGG-DC-PDC to MGG-DC-CAM
Naming Context: CN=Schema,CN=Configuration,DC=metrogastro,DC=com
The replication generated an error (-2146893022):
The target principal name is incorrect.
The failure occurred at 2006-11-05 10:58.12.
The last success occurred at 2006-02-13 15:50.41.
2250 failures have occurred since the last success.
[Replications Check,MGG-DC-CAM] A recent replication attempt failed:
From MGG-CC-BDC to MGG-DC-CAM
Naming Context: DC=DomainDnsZones,DC=metrogastro,DC=com
The replication generated an error (-2146893022):
The target principal name is incorrect.
The failure occurred at 2006-10-30 00:50.01.
The last success occurred at 2006-02-13 15:50.41.
135 failures have occurred since the last success.
[Replications Check,MGG-DC-CAM] A recent replication attempt failed:
From MGG-DC-PDC to MGG-DC-CAM
Naming Context: DC=DomainDnsZones,DC=metrogastro,DC=com
The replication generated an error (-2146893022):
The target principal name is incorrect.
The failure occurred at 2006-10-30 00:50.35.
The last success occurred at 2006-02-13 15:50.41.
138 failures have occurred since the last success.
[Replications Check,MGG-DC-CAM] A recent replication attempt failed:
From MGG-CC-BDC to MGG-DC-CAM
Naming Context: DC=ForestDnsZones,DC=metrogastro,DC=com
The replication generated an error (-2146893022):
The target principal name is incorrect.
The failure occurred at 2006-10-30 00:50.13.
The last success occurred at 2006-02-13 15:50.42.
135 failures have occurred since the last success.
[Replications Check,MGG-DC-CAM] A recent replication attempt failed:
From MGG-DC-PDC to MGG-DC-CAM
Naming Context: DC=ForestDnsZones,DC=metrogastro,DC=com
The replication generated an error (-2146893022):
The target principal name is incorrect.
The failure occurred at 2006-10-30 00:50.47.
The last success occurred at 2006-02-13 15:50.42.
139 failures have occurred since the last success.
......................... MGG-DC-CAM passed test Replications
Starting test: NCSecDesc
......................... MGG-DC-CAM passed test NCSecDesc
Starting test: NetLogons
......................... MGG-DC-CAM passed test NetLogons
Starting test: Advertising
......................... MGG-DC-CAM passed test Advertising
Starting test: KnowsOfRoleHolders
Warning: MGG-DC-PDC is the Schema Owner, but is not responding to DS RP
C Bind.
[MGG-DC-PDC] LDAP bind failed with error 8341,
A directory service error has occurred..
Warning: MGG-DC-PDC is the Schema Owner, but is not responding to LDAP
Bind.
Warning: MGG-DC-PDC is the Domain Owner, but is not responding to DS RP
C Bind.
Warning: MGG-DC-PDC is the Domain Owner, but is not responding to LDAP
Bind.
Warning: MGG-DC-PDC is the PDC Owner, but is not responding to DS RPC B
ind.
Warning: MGG-DC-PDC is the PDC Owner, but is not responding to LDAP Bin
d.
Warning: MGG-DC-PDC is the Rid Owner, but is not responding to DS RPC B
ind.
Warning: MGG-DC-PDC is the Rid Owner, but is not responding to LDAP Bin
d.
Warning: MGG-DC-PDC is the Infrastructure Update Owner, but is not resp
onding to DS RPC Bind.
Warning: MGG-DC-PDC is the Infrastructure Update Owner, but is not resp
onding to LDAP Bind.
......................... MGG-DC-CAM failed test KnowsOfRoleHolders
Starting test: RidManager
[MGG-DC-CAM] DsBindWithCred() failed with error -2146893022. The target
principal name is incorrect.
......................... MGG-DC-CAM failed test RidManager
Starting test: MachineAccount
......................... MGG-DC-CAM passed test MachineAccount
Starting test: Services
RPCLOCATOR Service is stopped on [MGG-DC-CAM]
TrkWks Service is stopped on [MGG-DC-CAM]
TrkSvr Service is stopped on [MGG-DC-CAM]
......................... MGG-DC-CAM failed test Services
Starting test: ObjectsReplicated
......................... MGG-DC-CAM passed test ObjectsReplicated
Starting test: frssysvol
Error: No record of File Replication System, SYSVOL started.
The Active Directory may be prevented from starting.
There are errors after the SYSVOL has been shared.
The SYSVOL can prevent the AD from starting.
......................... MGG-DC-CAM passed test frssysvol
Starting test: kccevent
An Warning Event occured. EventID: 0x80000785
Time Generated: 11/05/2006 11:27:04
Event String: The attempt to establish a replication link for
An Warning Event occured. EventID: 0x80000785
Time Generated: 11/05/2006 11:27:04
Event String: The attempt to establish a replication link for
An Warning Event occured. EventID: 0x80000785
Time Generated: 11/05/2006 11:27:04
Event String: The attempt to establish a replication link for
An Warning Event occured. EventID: 0x80000785
Time Generated: 11/05/2006 11:27:04
Event String: The attempt to establish a replication link for
An Warning Event occured. EventID: 0x80000785
Time Generated: 11/05/2006 11:27:04
Event String: The attempt to establish a replication link for
An Warning Event occured. EventID: 0x80000785
Time Generated: 11/05/2006 11:27:04
Event String: The attempt to establish a replication link for
An Warning Event occured. EventID: 0x80000785
Time Generated: 11/05/2006 11:27:04
Event String: The attempt to establish a replication link for
An Warning Event occured. EventID: 0x80000785
Time Generated: 11/05/2006 11:27:04
Event String: The attempt to establish a replication link for
An Warning Event occured. EventID: 0x80000785
Time Generated: 11/05/2006 11:27:04
Event String: The attempt to establish a replication link for
An Warning Event occured. EventID: 0x80000785
Time Generated: 11/05/2006 11:27:04
Event String: The attempt to establish a replication link for
......................... MGG-DC-CAM failed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0x40000004
Time Generated: 11/05/2006 10:33:13
Event String: The kerberos client received a
An Error Event occured. EventID: 0x40000004
Time Generated: 11/05/2006 10:39:30
Event String: The kerberos client received a
An Error Event occured. EventID: 0x40000004
Time Generated: 11/05/2006 10:39:39
Event String: The kerberos client received a
An Error Event occured. EventID: 0x40000004
Time Generated: 11/05/2006 10:40:28
Event String: The kerberos client received a
An Error Event occured. EventID: 0x40000004
Time Generated: 11/05/2006 10:42:01
Event String: The kerberos client received a
An Error Event occured. EventID: 0x40000004
Time Generated: 11/05/2006 10:42:02
Event String: The kerberos client received a
An Error Event occured. EventID: 0x40000004
Time Generated: 11/05/2006 10:42:02
Event String: The kerberos client received a
An Error Event occured. EventID: 0x40000004
Time Generated: 11/05/2006 10:42:02
Event String: The kerberos client received a
An Error Event occured. EventID: 0x40000004
Time Generated: 11/05/2006 10:42:59
Event String: The kerberos client received a
An Error Event occured. EventID: 0x40000004
Time Generated: 11/05/2006 10:42:59
Event String: The kerberos client received a
An Error Event occured. EventID: 0x40000004
Time Generated: 11/05/2006 10:45:40
Event String: The kerberos client received a
An Error Event occured. EventID: 0x40000004
Time Generated: 11/05/2006 10:55:47
Event String: The kerberos client received a
An Error Event occured. EventID: 0x40000004
Time Generated: 11/05/2006 10:57:17
Event String: The kerberos client received a
An Error Event occured. EventID: 0x40000004
Time Generated: 11/05/2006 10:57:20
Event String: The kerberos client received a
An Error Event occured. EventID: 0x40000004
Time Generated: 11/05/2006 10:58:27
Event String: The kerberos client received a
An Error Event occured. EventID: 0x40000004
Time Generated: 11/05/2006 10:58:28
Event String: The kerberos client received a
An Error Event occured. EventID: 0x40000004
Time Generated: 11/05/2006 11:04:46
Event String: The kerberos client received a
An Error Event occured. EventID: 0x40000004
Time Generated: 11/05/2006 11:05:06
Event String: The kerberos client received a
An Error Event occured. EventID: 0x40000004
Time Generated: 11/05/2006 11:06:00
Event String: The kerberos client received a
An Error Event occured. EventID: 0x40000004
Time Generated: 11/05/2006 11:13:59
Event String: The kerberos client received a
An Error Event occured. EventID: 0x40000004
Time Generated: 11/05/2006 11:18:40
Event String: The kerberos client received a
An Error Event occured. EventID: 0x40000004
Time Generated: 11/05/2006 11:27:56
Event String: The kerberos client received a
An Error Event occured. EventID: 0x40000004
Time Generated: 11/05/2006 11:28:12
Event String: The kerberos client received a
An Error Event occured. EventID: 0x40000004
Time Generated: 11/05/2006 11:28:12
Event String: The kerberos client received a
An Error Event occured. EventID: 0x40000004
Time Generated: 11/05/2006 11:28:12
Event String: The kerberos client received a
An Error Event occured. EventID: 0x40000004
Time Generated: 11/05/2006 11:28:12
Event String: The kerberos client received a
An Error Event occured. EventID: 0x40000004
Time Generated: 11/05/2006 11:28:12
Event String: The kerberos client received a
......................... MGG-DC-CAM failed test systemlog

Running enterprise tests on : metrogastro.com
Starting test: Intersite
......................... metrogastro.com passed test Intersite
Starting test: FsmoCheck
[MGG-LAB-PDC] LDAP bind failed with error 8341,
A directory service error has occurred..
......................... metrogastro.com passed test FsmoCheck
 
Sounds like you need to fix the replication error.

Run replmon.exe from the support tools of the Windows 2003 CD.

This should give you more detailed information as to why replication is failing.



 
I demoted the domain controller at the remote site. Cleaned the primary pdc of all remnants of the remote server. Then promoted the remote server back to a domain controller. Did the trick.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top