Error 1311 Ntds
Contents |
additional information might be available elsewhere. Thank you for searching on this message; your search helps us identify those event id 1865 areas for which we need to provide more information. If the product or version you are looking for is not listed, you can use this search box to search TechNet, the Microsoft Knowledge Base, and TechNet Blogs for more information. Enter the product name, event source, and event ID. For example: Vista Application Error 1001.
Answer Questions My Profile ShortcutsDiscussion GroupsFeature RequestsHelp and SupportHow-tosIT Service ProvidersMy QuestionsApp CenterRatings and ReviewsRecent ActivityRecent PostsScript CenterSpiceListsSpiceworks BlogVendor PagesWindows Events
Event Id 1311 Kcc
Event 1311 (Error) Source: NTDS KCC How important is this event? (5 event id 1311 source activedirectory_domainservice votes) 1 2 3 4 5 not important very important Description Details Product: Windows Operating System Event ID: 1311 ad global catalog Source: NTDS KCC Version: 5.2 Symbolic Name: DIRLOG_KCC_NO_SPANNING_TREE Message: The Knowledge Consistency Checker (KCC) has detected problems with the following directory partition. Directory partition: %1 There is insufficient site connectivity http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Windows+Operating+System&ProdVer=5.2&EvtID=1311&EvtSrc=NTDS+KCC information in Active Directory Sites and Services for the KCC to create a spanning tree replication topology. Or, one or more domain controllers with this directory partition are unable to replicate the directory partition information. This is probably due to inaccessible domain controllers. User Action Use Active Directory Sites and Services to perform one of the following actions: - Publish https://community.spiceworks.com/windows_event/show/509-ntds-kcc-1311 sufficient site connectivity information so that the KCC can determine a route by which this directory partition can reach this site. This is the preferred option. - Add a Connection object to a domain controller that contains the directory partition in this site from a domain controller that contains the same directory partition in another site. If neither of the Active Directory Sites and Services tasks correct this condition, see previous events logged by the KCC that identify the inaccessible domain controllers. Explanation The Knowledge Consistency Checker (KCC) could not connect to all of the domain controllers hosting this partition. The topology is disconnected. Probable causes include: The set of site links is incomplete. The site links must span all the sites within the domain controllers. In addition, a site within the domain must be connected by site links to all the other sites within the domain. If site link bridging is disabled, a copy of the domain must exist in each site along the path. One or more domain controllers cannot be contacted. All eligible bridgeheads for a domai
Analyzer Sample report Advanced filtering Direct links to www.eventid.net Email notifications Scheduled reporting Free for subscribers EventReader Event Viewer Sample report Custom views/filters Servers http://www.eventid.net/display-eventid-1311-source-NTDS%20KCC-eventno-524-phase-1.htm list, organized in groups Integration with EventID.Net Consolidated view for all logs https://www.experts-exchange.com/questions/21844257/NTDS-KCC-Errors-with-Event-ID-1566-1311-1865.html Free for subscribers Event ID: 1311 Source: NTDS KCC Source: NTDS KCC Type: Error Description: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 event id 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 event id 1311 Naming Context DC=mycorp,DC=com in this site from a Domain Controller that contains the same Naming Context in another site. English: This information is only available to subscribers. An example of English, please! Concepts to understand: What is NTDS and what are the roles of its components? What is KCC? What is a directory service? Comments: Anonymous This event sometimes may be logged along with event id 1988 which identifies "lingering objects" on one or more DCs. In our case, replication wasn''t occurring as a result of the lingering object and after removing the lingering object (see T736571 for syntax) the replication problems were gone. x 8 Anonymous I was receiving this event followed by EventID 1312 from source NTDS KCC. The Intersite Messaging service was disabled on one of my domain controllers. Enabling and starting this service cleared up the issue. x 11 Anonymous Our environment was a mixed one, with 2k and 2k3 DCs. We installed ME913446 on the Win2k3 DCs and ME893066 on the Win2k DCs. Then, we added the f
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > NTDS KCC Errors with Event ID 1566, 1311 & 1865 Want to Advertise Here? Solved NTDS KCC Errors with Event ID 1566, 1311 & 1865 Posted on 2006-05-09 Windows Networking 1 Verified Solution 7 Comments 20,367 Views Last Modified: 2012-11-06 Setup: IN our single domain there are 3 sites, each site has a subnet, Site 1 (HQ) has 2 domain controllers running Server 2003 Standard SP1, remote Site 2 and remote Site 3 each have 1 domain controller running Server 2003 Standard Sp1. Domain is 2003 Native mode. At the HQ site the FSMO roles are split across the 2 DC's server 1 has Infrastructure master, Server 2 has PDC and RID and is a GC. The DC at each remote site is a GC. DNS is Dynamic and AD integrated and replicates to all DCs in the AD domain. Sites and subnets created in AD sites and services. Replication Links created from: HQ site server 1 from HQ Site server 3 and remote site 2 DC; HQ server 2 from HQ server 1 and remote site 2 DC; Remote site 2 from HQ server 1 and HQ server 2; Remote site 3 from HQ server 1 and HQ server 2. Time sync is internal windows time from the HQ Server 2. Each site has a firewall which is open to replication traffic as far as can be told by following other technical documents on ports needed to allow replication Issue: replication works with no issues for 7-10 days, then HQ server 2 begins to record KCC errors in the Directory service log with event ids 1566, 1311 & 1865 Along with DNS event error 6002. The text of error 1566 : All domain controllers in the following site that can replicate the directory partition over this transport are currently unavailable. Site: CN=Site2,CN=Sites,CN=Configuration,DC=mycompany,DC=co,DC=uk Directory partition: CN=Configuration,DC=mycompany,DC=co,DC=uk Transport: CN=IP,CN=Inter-Site Transports,CN=Sites,CN=Configuration,DC=mycompany,DC=co,DC=uk The text of error 1311: The Knowledge Consistency Checker (KCC) has detected problems with the following directory partition. Directory partition: CN=Configuration,DC=my