Event ID/Source search
Keyword searchExample: Windows cannot unload your registry file
Event ID: 1264 Source: NTDS KCC
|Source: NTDS KCC|
A replication link for the partition DC=altairtech,DC=net from server CN=NTDS Settings,CN=DESCARTES,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=altairtech,DC=net has been added.
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is NTDS and what are the roles of its components?
What is KCC?
This event is logged by the KCC after it has properly created the replication link. As long as this event is logged, replication should occur automatically at the next scheduled time. This process can be initiated manually for each of the three naming contexts on the local domain controller by using the following commands:
repadmin /sync CN=Schema, CN=Configuration, DC=corp, DC=hay-buv, DC=com %computername% <rep_partner_GUID>
repadmin /sync CN=Configuration, DC=corp, DC=hay-buv, DC=com %computername% <rep_partner_GUID>
repadmin /sync DC=branches, DC=corp, DC=hay-buv, DC=com %computername% <rep_partner_GUID>
If event identification (ID) 1264 is not logged in Event Viewer, the replication link failed to be established. The directory services event log will then log event ID 1265 describing the reason for the failure. In this case, use the same resolution process as that used in dealing with errors generated when running the repadmin /showreps command. See the link to Technet for more details.
|Private comment: Subscribers only. See example of private comment|
|Links: TechNet - Troubleshooting Guidelines for Branch Office Environments|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated