Domain Controller Replication Issues...
Hi,
I've got an issue with our domain controller where I believe the domain is no longer replicating.
As you can see, it doesn't appear to have worked succesfully since 2007!!
Can anyone help or offer any advice?
dcdiag log below... I also keep getting this error in the eventlog:
Following is the summary of warnings and errors encountered by File Replication Service while polling the Domain Controller LVL3-liveSQL-02.managedser
Could not bind to a Domain Controller. Will try again at next polling cycle.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Domain Controller Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\LV
Starting test: Connectivity
......................... LVL3-liveSQL-02 passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\LV
Starting test: Replications
[Replications Check,LVL3-liveSQL-02] A recent replication attempt faile
d:
From LVL3-liveSQL-03 to LVL3-liveSQL-02
Naming Context: DC=ForestDnsZones,DC=manag
The replication generated an error (8614):
Win32 Error 8614
The failure occurred at 2009-07-04 04:48:07.
The last success occurred at 2007-09-26 15:46:27.
11 failures have occurred since the last success.
[LVL3-liveSQL-03] DsBindWithSpnEx() failed with error -2146893022,
Win32 Error -2146893022.
[Replications Check,LVL3-liveSQL-02] A recent replication attempt faile
d:
From LVL3-liveSQL-03 to LVL3-liveSQL-02
Naming Context: DC=DomainDnsZones,DC=manag
The replication generated an error (8614):
Win32 Error 8614
The failure occurred at 2009-07-04 04:48:07.
The last success occurred at 2007-09-26 15:46:27.
11 failures have occurred since the last success.
[Replications Check,LVL3-liveSQL-02] A recent replication attempt faile
d:
From LVL3-liveSQL-03 to LVL3-liveSQL-02
Naming Context: CN=Schema,CN=Configuration
s,DC=net
The replication generated an error (-2146893022):
Win32 Error -2146893022
The failure occurred at 2009-07-06 09:48:05.
The last success occurred at 2007-09-26 15:46:27.
15573 failures have occurred since the last success.
[Replications Check,LVL3-liveSQL-02] A recent replication attempt faile
d:
From LVL3-liveSQL-03 to LVL3-liveSQL-02
Naming Context: CN=Configuration,DC=manage
The replication generated an error (-2146893022):
Win32 Error -2146893022
The failure occurred at 2009-07-06 09:51:07.
The last success occurred at 2007-09-26 15:46:27.
36466 failures have occurred since the last success.
[Replications Check,LVL3-liveSQL-02] A recent replication attempt faile
d:
From LVL3-liveSQL-03 to LVL3-liveSQL-02
Naming Context: DC=managedservices,DC=net
The replication generated an error (-2146893022):
Win32 Error -2146893022
The failure occurred at 2009-07-06 10:03:17.
The last success occurred at 2007-09-26 15:46:27.
19762 failures have occurred since the last success.
REPLICATION-RECEIVED LATENCY WARNING
LVL3-liveSQL-02: Current time is 2009-07-06 10:03:19.
DC=ForestDnsZones,DC=manag
Last replication recieved from LVL3-liveSQL-03 at 2007-09-26 15:4
6:31.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
DC=DomainDnsZones,DC=manag
Last replication recieved from LVL3-liveSQL-03 at 2007-09-26 15:4
6:31.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
CN=Schema,CN=Configuration
Last replication recieved from LVL3-liveSQL-03 at 2007-09-26 15:4
6:31.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
CN=Configuration,DC=manage
Last replication recieved from LVL3-liveSQL-03 at 2007-09-26 15:4
6:31.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
DC=managedservices,DC=net
Last replication recieved from LVL3-liveSQL-03 at 2007-09-26 15:4
6:31.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
......................... LVL3-liveSQL-02 passed test Replications
Starting test: NCSecDesc
......................... LVL3-liveSQL-02 passed test NCSecDesc
Starting test: NetLogons
......................... LVL3-liveSQL-02 passed test NetLogons
Starting test: Advertising
......................... LVL3-liveSQL-02 passed test Advertising
Starting test: KnowsOfRoleHolders
Warning: LVL3-liveSQL-03 is the Schema Owner, but is not responding to
DS RPC Bind.
[LVL3-liveSQL-03] LDAP bind failed with error 8341,
Win32 Error 8341.
Warning: LVL3-liveSQL-03 is the Schema Owner, but is not responding to
LDAP Bind.
Warning: LVL3-liveSQL-03 is the Domain Owner, but is not responding to
DS RPC Bind.
Warning: LVL3-liveSQL-03 is the Domain Owner, but is not responding to
LDAP Bind.
Warning: LVL3-liveSQL-03 is the PDC Owner, but is not responding to DS
RPC Bind.
Warning: LVL3-liveSQL-03 is the PDC Owner, but is not responding to LDA
P Bind.
Warning: LVL3-liveSQL-03 is the Rid Owner, but is not responding to DS
RPC Bind.
Warning: LVL3-liveSQL-03 is the Rid Owner, but is not responding to LDA
P Bind.
Warning: LVL3-liveSQL-03 is the Infrastructure Update Owner, but is not
responding to DS RPC Bind.
Warning: LVL3-liveSQL-03 is the Infrastructure Update Owner, but is not
responding to LDAP Bind.
......................... LVL3-liveSQL-02 failed test KnowsOfRoleHolder
s
Starting test: RidManager
......................... LVL3-liveSQL-02 failed test RidManager
Starting test: MachineAccount
......................... LVL3-liveSQL-02 passed test MachineAccount
Starting test: Services
......................... LVL3-liveSQL-02 passed test Services
Starting test: ObjectsReplicated
......................... LVL3-liveSQL-02 passed test ObjectsReplicated
Starting test: frssysvol
......................... LVL3-liveSQL-02 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.
......................... LVL3-liveSQL-02 failed test frsevent
Starting test: kccevent
......................... LVL3-liveSQL-02 passed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0x40000004
Time Generated: 07/06/2009 10:03:19
Event String: The kerberos client received a
An Error Event occured. EventID: 0x40000004
Time Generated: 07/06/2009 10:03:19
Event String: The kerberos client received a
An Error Event occured. EventID: 0x40000004
Time Generated: 07/06/2009 10:03:19
Event String: The kerberos client received a
......................... LVL3-liveSQL-02 failed test systemlog
Starting test: VerifyReferences
......................... LVL3-liveSQL-02 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 : managedservices
Starting test: CrossRefValidation
......................... managedservices passed test CrossRefV
alidation
Starting test: CheckSDRefDom
......................... managedservices passed test CheckSDRe
fDom
Running enterprise tests on : managedservices.net
Starting test: Intersite
......................... managedservices.net passed test Inter
site
Starting test: FsmoCheck
......................... managedservices.net passed test FsmoC
heck
C:\Program Files\Support Tools>
I've got an issue with our domain controller where I believe the domain is no longer replicating.
As you can see, it doesn't appear to have worked succesfully since 2007!!
Can anyone help or offer any advice?
dcdiag log below... I also keep getting this error in the eventlog:
Following is the summary of warnings and errors encountered by File Replication Service while polling the Domain Controller LVL3-liveSQL-02.managedser
Could not bind to a Domain Controller. Will try again at next polling cycle.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Domain Controller Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\LV
Starting test: Connectivity
......................... LVL3-liveSQL-02 passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\LV
Starting test: Replications
[Replications Check,LVL3-liveSQL-02] A recent replication attempt faile
d:
From LVL3-liveSQL-03 to LVL3-liveSQL-02
Naming Context: DC=ForestDnsZones,DC=manag
The replication generated an error (8614):
Win32 Error 8614
The failure occurred at 2009-07-04 04:48:07.
The last success occurred at 2007-09-26 15:46:27.
11 failures have occurred since the last success.
[LVL3-liveSQL-03] DsBindWithSpnEx() failed with error -2146893022,
Win32 Error -2146893022.
[Replications Check,LVL3-liveSQL-02] A recent replication attempt faile
d:
From LVL3-liveSQL-03 to LVL3-liveSQL-02
Naming Context: DC=DomainDnsZones,DC=manag
The replication generated an error (8614):
Win32 Error 8614
The failure occurred at 2009-07-04 04:48:07.
The last success occurred at 2007-09-26 15:46:27.
11 failures have occurred since the last success.
[Replications Check,LVL3-liveSQL-02] A recent replication attempt faile
d:
From LVL3-liveSQL-03 to LVL3-liveSQL-02
Naming Context: CN=Schema,CN=Configuration
s,DC=net
The replication generated an error (-2146893022):
Win32 Error -2146893022
The failure occurred at 2009-07-06 09:48:05.
The last success occurred at 2007-09-26 15:46:27.
15573 failures have occurred since the last success.
[Replications Check,LVL3-liveSQL-02] A recent replication attempt faile
d:
From LVL3-liveSQL-03 to LVL3-liveSQL-02
Naming Context: CN=Configuration,DC=manage
The replication generated an error (-2146893022):
Win32 Error -2146893022
The failure occurred at 2009-07-06 09:51:07.
The last success occurred at 2007-09-26 15:46:27.
36466 failures have occurred since the last success.
[Replications Check,LVL3-liveSQL-02] A recent replication attempt faile
d:
From LVL3-liveSQL-03 to LVL3-liveSQL-02
Naming Context: DC=managedservices,DC=net
The replication generated an error (-2146893022):
Win32 Error -2146893022
The failure occurred at 2009-07-06 10:03:17.
The last success occurred at 2007-09-26 15:46:27.
19762 failures have occurred since the last success.
REPLICATION-RECEIVED LATENCY WARNING
LVL3-liveSQL-02: Current time is 2009-07-06 10:03:19.
DC=ForestDnsZones,DC=manag
Last replication recieved from LVL3-liveSQL-03 at 2007-09-26 15:4
6:31.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
DC=DomainDnsZones,DC=manag
Last replication recieved from LVL3-liveSQL-03 at 2007-09-26 15:4
6:31.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
CN=Schema,CN=Configuration
Last replication recieved from LVL3-liveSQL-03 at 2007-09-26 15:4
6:31.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
CN=Configuration,DC=manage
Last replication recieved from LVL3-liveSQL-03 at 2007-09-26 15:4
6:31.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
DC=managedservices,DC=net
Last replication recieved from LVL3-liveSQL-03 at 2007-09-26 15:4
6:31.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
......................... LVL3-liveSQL-02 passed test Replications
Starting test: NCSecDesc
......................... LVL3-liveSQL-02 passed test NCSecDesc
Starting test: NetLogons
......................... LVL3-liveSQL-02 passed test NetLogons
Starting test: Advertising
......................... LVL3-liveSQL-02 passed test Advertising
Starting test: KnowsOfRoleHolders
Warning: LVL3-liveSQL-03 is the Schema Owner, but is not responding to
DS RPC Bind.
[LVL3-liveSQL-03] LDAP bind failed with error 8341,
Win32 Error 8341.
Warning: LVL3-liveSQL-03 is the Schema Owner, but is not responding to
LDAP Bind.
Warning: LVL3-liveSQL-03 is the Domain Owner, but is not responding to
DS RPC Bind.
Warning: LVL3-liveSQL-03 is the Domain Owner, but is not responding to
LDAP Bind.
Warning: LVL3-liveSQL-03 is the PDC Owner, but is not responding to DS
RPC Bind.
Warning: LVL3-liveSQL-03 is the PDC Owner, but is not responding to LDA
P Bind.
Warning: LVL3-liveSQL-03 is the Rid Owner, but is not responding to DS
RPC Bind.
Warning: LVL3-liveSQL-03 is the Rid Owner, but is not responding to LDA
P Bind.
Warning: LVL3-liveSQL-03 is the Infrastructure Update Owner, but is not
responding to DS RPC Bind.
Warning: LVL3-liveSQL-03 is the Infrastructure Update Owner, but is not
responding to LDAP Bind.
......................... LVL3-liveSQL-02 failed test KnowsOfRoleHolder
s
Starting test: RidManager
......................... LVL3-liveSQL-02 failed test RidManager
Starting test: MachineAccount
......................... LVL3-liveSQL-02 passed test MachineAccount
Starting test: Services
......................... LVL3-liveSQL-02 passed test Services
Starting test: ObjectsReplicated
......................... LVL3-liveSQL-02 passed test ObjectsReplicated
Starting test: frssysvol
......................... LVL3-liveSQL-02 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.
......................... LVL3-liveSQL-02 failed test frsevent
Starting test: kccevent
......................... LVL3-liveSQL-02 passed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0x40000004
Time Generated: 07/06/2009 10:03:19
Event String: The kerberos client received a
An Error Event occured. EventID: 0x40000004
Time Generated: 07/06/2009 10:03:19
Event String: The kerberos client received a
An Error Event occured. EventID: 0x40000004
Time Generated: 07/06/2009 10:03:19
Event String: The kerberos client received a
......................... LVL3-liveSQL-02 failed test systemlog
Starting test: VerifyReferences
......................... LVL3-liveSQL-02 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 : managedservices
Starting test: CrossRefValidation
......................... managedservices passed test CrossRefV
alidation
Starting test: CheckSDRefDom
......................... managedservices passed test CheckSDRe
fDom
Running enterprise tests on : managedservices.net
Starting test: Intersite
......................... managedservices.net passed test Inter
site
Starting test: FsmoCheck
......................... managedservices.net passed test FsmoC
heck
C:\Program Files\Support Tools>
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Glen Knight
if that is a no go then as Mike has said it's a force demotion and repromote.