Active Directory Replication Problem

[joe_ista]

Dear All,
two days ago I have crashed on my Windows 2008 Server, then I restored my server from my last image back up. now my server is running but I have a problem on active directory replication error. I got this info from dcdiag.exe :

From JBGSRV18 to JABUNG-FIELD
Naming Context: DC=jabung,DC=com
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 2010-06-04 07:10:54.
The last success occurred at 2010-05-15 14:26:10.
1500 failures have occurred since the last success.
[Replications Check,JABUNG-FIELD] A recent replication attempt failed:
From JBGSRV11 to JABUNG-FIELD
Naming Context: DC=jabung,DC=com
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 2010-06-04 07:11:57.
The last success occurred at 2010-05-15 14:25:52.
1552 failures have occurred since the last success.
[Replications Check,JABUNG-FIELD] A recent replication attempt failed:
From JBGSRV15 to JABUNG-FIELD
Naming Context: DC=jabung,DC=com
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 2010-06-04 07:12:02.
The last success occurred at (never).
4 failures have occurred since the last success.
......................... JABUNG-FIELD failed test Replications
Starting test: RidManager
......................... JABUNG-FIELD passed test RidManager
Starting test: Services
w32time Service is stopped on [JABUNG-FIELD]
......................... JABUNG-FIELD failed test Services
Starting test: SystemLog
An Warning Event occurred. EventID: 0x825A000C
Time Generated: 06/04/2010 07:10:07
Event String:
Time Provider NtpClient: This machine is configured to use the domai
n hierarchy to determine its time source, but it is the AD PDC emulator for the
domain at the root of the forest, so there is no machine above it in the domain
hierarchy to use as a time source. It is recommended that you either configure a
reliable time service in the root domain, or manually configure the AD PDC to s
ynchronize with an external time source. Otherwise, this machine will function a
s the authoritative time source in the domain hierarchy. If an external time sou
rce is not configured or used for this computer, you may choose to disable the N
tpClient.
......................... JABUNG-FIELD failed test SystemLog
Starting test: VerifyReferences
......................... JABUNG-FIELD passed test VerifyReferences


Running partition tests on : ForestDnsZones
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation

Running partition tests on : DomainDnsZones
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... DomainDnsZones 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 partition tests on : jabung
Starting test: CheckSDRefDom
......................... jabung passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... jabung passed test CrossRefValidation

Running enterprise tests on : jabung.com
Starting test: LocatorCheck
Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
A Time Server could not be located.
The server holding the PDC role is down.
Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error
1355
A Good Time Server could not be located.
......................... jabung.com failed test LocatorCheck
Starting test: Intersite
......................... jabung.com passed test Intersite

[Devasis]

Have troubleshooted active directory? If not then so it first. There are some of the tools are available on the Microsoft which are best to know about the problem and the solution of the same. One of then is known as the Repadmin tool. Hope you will like it. To Know more about the troubleshoot and active directory replication error problem visit here.