Wednesday, September 17, 2008

Troubleshooting Event ID 1311: Knowledge Consistency Checker KCC

Troubleshooting Event ID 1311: Knowledge Consistency Checker
View products that this article applies to.
Article ID : 214745
Last Review : October 30, 2006
Revision : 4.1
This article was previously published under Q214745
You may see the following entry (with ID 1311 from event source "NTDS KCC") in the Directory Service log:
The Directory Service consistency checker has determined that there is not enough physical connectivity published via the Active Directory Sites and Services Manager to create a spanning tree connecting all the sites containing the Naming Context DC=mycorp,DC=com.

Please use the Active Directory Sites and Services Manager to do one of the following:
Publish sufficient site connectivity information such that the system can infer a route by which this Naming Context can reach this site. This option is preferred.
Add an ntdsConnection object to a Domain Controller that contains the Naming Context DC=mycorp,DC=com in this site from a Domain Controller that contains the same Naming Context in another site.

Back to the top
This behavior can occur if the Knowledge Consistency Checker (KCC) has determined that a site has been orphaned from the replication topology.

Back to the top
One computer in any given site owns the role of creating inbound replication connection objects between bridgehead servers from other sites. This domain controller is known as the Inter-Site Topology Generator. While analyzing the Site Link and Site Link Bridge structure to determine the most cost-effective route to synchronize a naming context between two points, it may determine that a site does not have membership in any Site Link and therefore has no means to create a replication object to a bridgehead server in that site.

The first site in the Active Directory (named "Default-First-Site-Name"), is created automatically for the administrator. This site is a member of the default Site Link ("DEFAULTIPSITELINK"), which is also created automatically for the administrator, and is used for RPC communication over TCP/IP. If the administrator were to create two additional sites ("Site1" and "Site2" for example), the administrator must define a Site Link that the site will be a member of before they can be written to the Active Directory.

However, the administrator can open the properties of a Site Link and modify which sites reside in the Site Link. If the administrator were to remove a site from all Site Links, the KCC displays the error message listed above to indicate that a correction needs to be made to the configuration.

1. Go to Active Directory Sites and Services > Sites > Inter-Site Transports > IP > on detail pane, right click on "DefaultIPSiteLinke" > properties > Add sites to the site link

No comments: