The Knowledge Consistency Checker (KCC) could not establish a connection to site %1 using transport %2 for partition %3 because a suitable bridgehead could not be found. If explicit bridgehead servers have been specified- then only those servers will be considered- otherwise all servers in the site will be considered. In order to be a viable bridgehead- the transport must be configured for that server (check the transport-specific address attribute). Also- the partition must be instantiated on that server- and must be writeable when constructing a normal topology- or either read-only or writeable when constructing a global catalog topology.

Details
Product: Windows Operating System
Event ID: 1474
Source: Active Directory
Version: 5.0
Symbolic Name: DIRLOG_KCC_TRANSPORT_BRIDGEHEAD_NOT_FOUND
Message: The Knowledge Consistency Checker (KCC) could not establish a connection to site %1 using transport %2 for partition %3 because a suitable bridgehead could not be found. If explicit bridgehead servers have been specified- then only those servers will be considered- otherwise all servers in the site will be considered. In order to be a viable bridgehead- the transport must be configured for that server (check the transport-specific address attribute). Also- the partition must be instantiated on that server- and must be writeable when constructing a normal topology- or either read-only or writeable when constructing a global catalog topology.
   
Explanation

This is an Active Directory internal event. Internal events appear in Event Viewer only when the default logging level is changed. Most internal events are for informational purposes only. This event is logged when a viable bridgehead server could not be found to transport data to the specified site for the directory partition. If preferred bridgehead servers have been specified, then only those domain controllers will be considered viable; otherwise, all domain controllers in the site will be considered viable.

   
User Action

To set a viable preferred bridgehead server, verify that the following requirements are met:

  • • The transport object must be configured for that domain controller. To do this, verify the transport-specific address attribute using Active Directory Sites and Services. Navigate to the computer, right-click the computer name, click Properties, and then verify that SMTP or IP is displayed and available.
  • • The directory partition must be instantiated on the domain controller, and it must be writeable if you are constructing a normal topology. If you are constructing a global catalog topology, the directory partition can be either read-only or writeable.

If both of these objects are met, and you still cannot do it, then investigate further.

Related:

Leave a Reply