Directory Server Diagnosis
Performing initial setup:
Trying to find home server...
Home Server = NTEDC01
* Identified AD Forest.
Done gathering initial info.
Doing initial required tests
Testing server: Paris\NTEDC01
Starting test: Connectivity
......................... NTEDC01 passed test Connectivity
Doing primary tests
Testing server: Paris\NTEDC01
Starting test: Advertising
......................... NTEDC01 passed test Advertising
Starting test: FrsEvent
......................... NTEDC01 passed test FrsEvent
Starting test: DFSREvent
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.
......................... NTEDC01 passed test DFSREvent
Starting test: SysVolCheck
......................... NTEDC01 passed test SysVolCheck
Starting test: KccEvent
A warning event occurred. EventID: 0x8000082D
Time Generated: 01/03/2013 15:18:53
Event String:
A warning event occurred. EventID: 0x8000082D
Time Generated: 01/03/2013 15:18:53
Event String:
A warning event occurred. EventID: 0x8000082D
Time Generated: 01/03/2013 15:18:53
Event String:
An error event occurred. EventID: 0xC0000748
Time Generated: 01/03/2013 15:18:53
Event String:
This is the replication status for the following directory partition on this directory server.
An error event occurred. EventID: 0xC0000748
Time Generated: 01/03/2013 15:18:53
Event String:
This is the replication status for the following directory partition on this directory server.
An error event occurred. EventID: 0xC0000748
Time Generated: 01/03/2013 15:18:53
Event String:
This is the replication status for the following directory partition on this directory server.
A warning event occurred. EventID: 0x8000061E
Time Generated: 01/03/2013 15:23:58
Event String:
All directory servers in the following site that can replicate the directory partition over this transport are currently unavailable.
An error event occurred. EventID: 0xC000051F
Time Generated: 01/03/2013 15:23:58
Event String:
The Knowledge Consistency Checker (KCC) has detected problems with the following directory partition.
A warning event occurred. EventID: 0x80000749
Time Generated: 01/03/2013 15:23:58
Event String:
The Knowledge Consistency Checker (KCC) was unable to form a complete spanning tree network topology. As a result, the following list of sites cannot be reached from the local site.
A warning event occurred. EventID: 0x8000061E
Time Generated: 01/03/2013 15:23:58
Event String:
All directory servers in the following site that can replicate the directory partition over this transport are currently unavailable.
An error event occurred. EventID: 0xC000051F
Time Generated: 01/03/2013 15:23:58
Event String:
The Knowledge Consistency Checker (KCC) has detected problems with the following directory partition.
A warning event occurred. EventID: 0x80000749
Time Generated: 01/03/2013 15:23:58
Event String:
The Knowledge Consistency Checker (KCC) was unable to form a complete spanning tree network topology. As a result, the following list of sites cannot be reached from the local site.
......................... NTEDC01 failed test KccEvent
Starting test: KnowsOfRoleHolders
......................... NTEDC01 passed test KnowsOfRoleHolders
Starting test: MachineAccount
......................... NTEDC01 passed test MachineAccount
Starting test: NCSecDesc
......................... NTEDC01 passed test NCSecDesc
Starting test: NetLogons
......................... NTEDC01 passed test NetLogons
Starting test: ObjectsReplicated
......................... NTEDC01 passed test ObjectsReplicated
Starting test: Replications
REPLICATION LATENCY WARNING
NTEDC01: This replication path was preempted by higher priority work.
from ROOTDC02 to NTEDC01
Reason: The operation completed successfully.
The last success occurred at (never).
Replication of new changes along this path will be delayed.
[Replications Check,NTEDC01] A recent replication attempt failed:
From GVADC01 to NTEDC01
Naming Context: DC=EUROPE,DC=loc
The replication generated an error (8451):
The replication operation encountered a database error.
The failure occurred at 2013-01-03 14:49:22.
The last success occurred at 2012-12-22 02:47:54.
300 failures have occurred since the last success.
A serious error is preventing replication from continuing.
Consult the error log for further information.
If a particular object is named, it may be necessary to manually
modify or delete the object.
If the condition persists, contact Microsoft Support.
[Replications Check,NTEDC01] A recent replication attempt failed:
From GVADC02 to NTEDC01
Naming Context: DC=EUROPE,DC=loc
The replication generated an error (8451):
The replication operation encountered a database error.
The failure occurred at 2013-01-03 15:06:06.
The last success occurred at 2012-12-22 02:47:54.
301 failures have occurred since the last success.
A serious error is preventing replication from continuing.
Consult the error log for further information.
If a particular object is named, it may be necessary to manually
modify or delete the object.
If the condition persists, contact Microsoft Support.
REPLICATION LATENCY WARNING
NTEDC01: This replication path was preempted by higher priority work.
from ROOTDC02 to NTEDC01
Reason: The operation completed successfully.
The last success occurred at (never).
Replication of new changes along this path will be delayed.
REPLICATION LATENCY WARNING
NTEDC01: This replication path was preempted by higher priority work.
from ROOTDC02 to NTEDC01
Reason: The operation completed successfully.
The last success occurred at (never).
Replication of new changes along this path will be delayed.
[Replications Check,NTEDC01] A recent replication attempt failed:
From GVADC01 to NTEDC01
Naming Context: DC=AFRICA,DC=loc
The replication generated an error (8606):
Insufficient attributes were given to create an object. This object may not exist because it may have been deleted and already garbage collected.
The failure occurred at 2013-01-03 14:49:49.
The last success occurred at 2012-12-18 07:47:58.
391 failures have occurred since the last success.
[Replications Check,NTEDC01] A recent replication attempt failed:
From ROOTDC01 to NTEDC01
Naming Context: DC=AFRICA,DC=loc
The replication generated an error (8606):
Insufficient attributes were given to create an object. This object may not exist because it may have been deleted and already garbage collected.
The failure occurred at 2013-01-03 14:49:58.
The last success occurred at (never).
42 failures have occurred since the last success.
[Replications Check,NTEDC01] A recent replication attempt failed:
From AFRDC01 to NTEDC01
Naming Context: DC=AFRICA,DC=loc
The replication generated an error (8606):
Insufficient attributes were given to create an object. This object may not exist because it may have been deleted and already garbage collected.
The failure occurred at 2013-01-03 14:50:02.
The last success occurred at (never).
24 failures have occurred since the last success.
[Replications Check,NTEDC01] A recent replication attempt failed:
From ROOTDC03 to NTEDC01
Naming Context: DC=AFRICA,DC=loc
The replication generated an error (8606):
Insufficient attributes were given to create an object. This object may not exist because it may have been deleted and already garbage collected.
The failure occurred at 2013-01-03 14:50:04.
The last success occurred at (never).
8 failures have occurred since the last success.
[Replications Check,NTEDC01] A recent replication attempt failed:
From AFRDC02 to NTEDC01
Naming Context: DC=AFRICA,DC=loc
The replication generated an error (8606):
Insufficient attributes were given to create an object. This object may not exist because it may have been deleted and already garbage collected.
The failure occurred at 2013-01-03 14:50:25.
The last success occurred at (never).
4 failures have occurred since the last success.
[Replications Check,NTEDC01] A recent replication attempt failed:
From AMERICADC01 to NTEDC01
Naming Context: DC=AFRICA,DC=loc
The replication generated an error (8606):
Insufficient attributes were given to create an object. This object may not exist because it may have been deleted and already garbage collected.
The failure occurred at 2013-01-03 14:50:28.
The last success occurred at (never).
2 failures have occurred since the last success.
REPLICATION LATENCY WARNING
NTEDC01: This replication path was preempted by higher priority work.
from ROOTDC02 to NTEDC01
Reason: The operation completed successfully.
The last success occurred at (never).
Replication of new changes along this path will be delayed.
[Replications Check,NTEDC01] A recent replication attempt failed:
From GVADC02 to NTEDC01
Naming Context: DC=AFRICA,DC=loc
The replication generated an error (8606):
Insufficient attributes were given to create an object. This object may not exist because it may have been deleted and already garbage collected.
The failure occurred at 2013-01-03 15:06:13.
The last success occurred at (never).
385 failures have occurred since the last success.
REPLICATION LATENCY WARNING
NTEDC01: This replication path was preempted by higher priority work.
from ROOTDC02 to NTEDC01
Reason: The operation completed successfully.
The last success occurred at (never).
Replication of new changes along this path will be delayed.
[Replications Check,NTEDC01] A recent replication attempt failed:
From GVADC01 to NTEDC01
Naming Context: DC=Asia,DC=loc
The replication generated an error (8451):
The replication operation encountered a database error.
The failure occurred at 2013-01-03 14:49:53.
The last success occurred at 2012-12-18 08:47:59.
390 failures have occurred since the last success.
A serious error is preventing replication from continuing.
Consult the error log for further information.
If a particular object is named, it may be necessary to manually
modify or delete the object.
If the condition persists, contact Microsoft Support.
[Replications Check,NTEDC01] A recent replication attempt failed:
From ROOTDC01 to NTEDC01
Naming Context: DC=Asia,DC=loc
The replication generated an error (8451):
The replication operation encountered a database error.
The failure occurred at 2013-01-03 14:50:36.
The last success occurred at (never).
42 failures have occurred since the last success.
A serious error is preventing replication from continuing.
Consult the error log for further information.
If a particular object is named, it may be necessary to manually
modify or delete the object.
If the condition persists, contact Microsoft Support.
[Replications Check,NTEDC01] A recent replication attempt failed:
From AFRDC01 to NTEDC01
Naming Context: DC=Asia,DC=loc
The replication generated an error (8451):
The replication operation encountered a database error.
The failure occurred at 2013-01-03 14:50:39.
The last success occurred at (never).
24 failures have occurred since the last success.
A serious error is preventing replication from continuing.
Consult the error log for further information.
If a particular object is named, it may be necessary to manually
modify or delete the object.
If the condition persists, contact Microsoft Support.
[Replications Check,NTEDC01] A recent replication attempt failed:
From ROOTDC03 to NTEDC01
Naming Context: DC=Asia,DC=loc
The replication generated an error (8451):
The replication operation encountered a database error.
The failure occurred at 2013-01-03 14:50:42.
The last success occurred at (never).
8 failures have occurred since the last success.
A serious error is preventing replication from continuing.
Consult the error log for further information.
If a particular object is named, it may be necessary to manually
modify or delete the object.
If the condition persists, contact Microsoft Support.
[Replications Check,NTEDC01] A recent replication attempt failed:
From AFRDC02 to NTEDC01
Naming Context: DC=Asia,DC=loc
The replication generated an error (8451):
The replication operation encountered a database error.
The failure occurred at 2013-01-03 14:50:49.
The last success occurred at (never).
4 failures have occurred since the last success.
A serious error is preventing replication from continuing.
Consult the error log for further information.
If a particular object is named, it may be necessary to manually
modify or delete the object.
If the condition persists, contact Microsoft Support.
[Replications Check,NTEDC01] A recent replication attempt failed:
From AMERICADC01 to NTEDC01
Naming Context: DC=Asia,DC=loc
The replication generated an error (8451):
The replication operation encountered a database error.
The failure occurred at 2013-01-03 14:50:52.
The last success occurred at (never).
2 failures have occurred since the last success.
A serious error is preventing replication from continuing.
Consult the error log for further information.
If a particular object is named, it may be necessary to manually
modify or delete the object.
If the condition persists, contact Microsoft Support.
REPLICATION LATENCY WARNING
NTEDC01: This replication path was preempted by higher priority work.
from ROOTDC02 to NTEDC01
Reason: The operation completed successfully.
The last success occurred at (never).
Replication of new changes along this path will be delayed.
[Replications Check,NTEDC01] A recent replication attempt failed:
From GVADC02 to NTEDC01
Naming Context: DC=Asia,DC=loc
The replication generated an error (8451):
The replication operation encountered a database error.
The failure occurred at 2013-01-03 15:06:20.
The last success occurred at (never).
385 failures have occurred since the last success.
A serious error is preventing replication from continuing.
Consult the error log for further information.
If a particular object is named, it may be necessary to manually
modify or delete the object.
If the condition persists, contact Microsoft Support.
REPLICATION LATENCY WARNING
NTEDC01: This replication path was preempted by higher priority work.
from ROOTDC02 to NTEDC01
Reason: The operation completed successfully.
The last success occurred at (never).
Replication of new changes along this path will be delayed.
......................... NTEDC01 failed test Replications
Starting test: RidManager
......................... NTEDC01 passed test RidManager
Starting test: Services
......................... NTEDC01 passed test Services
Starting test: SystemLog
An error event occurred. EventID: 0xC0001B77
Time Generated: 01/03/2013 15:20:37
Event String:
The SNMP Service service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
......................... NTEDC01 failed test SystemLog
Starting test: VerifyReferences
......................... NTEDC01 passed test VerifyReferences
Running partition tests on : DomainDnsZones
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation
Running partition tests on : ForestDnsZones
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation
Running partition tests on : EUROPE
Starting test: CheckSDRefDom
......................... EUROPE passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... EUROPE passed test CrossRefValidation
Running partition tests on : Schema
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Running partition tests on : Configuration
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Running enterprise tests on : mydomain.loc
Starting test: LocatorCheck
......................... mydomain.loc passed test LocatorCheck
Starting test: Intersite
......................... mydomain.loc passed test Intersite
Dear all,
Im facieng a replication issues bettwen difrent servers on the ADDS tomology and I need your help in order to solve it, please find attached copy of dcdiag output from the server where replication errors accured.
Thansk in advance for your help