ok, i started to get this out of the blue everything was replicating fine, then my InterSite Messaging service shutdown on one server and i can't get it to start up
I get these 2 errors in my event viewer on ONE server:
Event Type: Error
Event Source: NTDS KCC
Event Category: Knowledge Consistency Checker
Event ID: 1311
Date: 10/1/2002
Time: 11:20:38 AM
User: N/A
Computer: NTSERVER2
Description:
The Directory Service consistency checker has determined that either (a) 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 Partition CN=Configuration,DC=bhwal,DC=local, or (b) replication cannot be performed with one or more critical servers in order for changes to propagate across all sites (most often due to the servers being unreachable).
For (a), please use the Active Directory Sites and Services Manager to do one of the following:
1. Publish sufficient site connectivity information such that the system can infer a route by which this Partition can reach this site. This option is preferred.
2. Add an ntdsConnection object to a Domain Controller that contains the Partition CN=Configuration,DC=bhwal,DC=local in this site from a Domain Controller that contains the same Partition in another site.
For (b), please see previous events logged by the NTDS KCC source that identify the servers that could not be contacted.
Event Type: Error
Event Source: NTDS KCC
Event Category: Knowledge Consistency Checker
Event ID: 1312
Date: 10/1/2002
Time: 11:20:38 AM
User: N/A
Computer: NTSERVER2
Description:
The call to the Intersite Messaging Service (ISM) specifying the transport CN=IP,CN=Inter-Site Transports,CN=Sites,CN=Configuration,DC=bhwal,DC=local failed with the following status:
The RPC server is unavailable.
This condition is causing the Directory Service consistency checker to fail to correctly configure an inter site replication topology. Please verify that the ISM is running and the correct plug-in dll for the transport is available.
The record data is the status code.
Data:
0000: ba 06 00 00 º...
Im in a huge bind, i gotta get Exchange Server2k up this week and i just don't think that will happen if i have this crap going on.
I get these 2 errors in my event viewer on ONE server:
Event Type: Error
Event Source: NTDS KCC
Event Category: Knowledge Consistency Checker
Event ID: 1311
Date: 10/1/2002
Time: 11:20:38 AM
User: N/A
Computer: NTSERVER2
Description:
The Directory Service consistency checker has determined that either (a) 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 Partition CN=Configuration,DC=bhwal,DC=local, or (b) replication cannot be performed with one or more critical servers in order for changes to propagate across all sites (most often due to the servers being unreachable).
For (a), please use the Active Directory Sites and Services Manager to do one of the following:
1. Publish sufficient site connectivity information such that the system can infer a route by which this Partition can reach this site. This option is preferred.
2. Add an ntdsConnection object to a Domain Controller that contains the Partition CN=Configuration,DC=bhwal,DC=local in this site from a Domain Controller that contains the same Partition in another site.
For (b), please see previous events logged by the NTDS KCC source that identify the servers that could not be contacted.
Event Type: Error
Event Source: NTDS KCC
Event Category: Knowledge Consistency Checker
Event ID: 1312
Date: 10/1/2002
Time: 11:20:38 AM
User: N/A
Computer: NTSERVER2
Description:
The call to the Intersite Messaging Service (ISM) specifying the transport CN=IP,CN=Inter-Site Transports,CN=Sites,CN=Configuration,DC=bhwal,DC=local failed with the following status:
The RPC server is unavailable.
This condition is causing the Directory Service consistency checker to fail to correctly configure an inter site replication topology. Please verify that the ISM is running and the correct plug-in dll for the transport is available.
The record data is the status code.
Data:
0000: ba 06 00 00 º...
Im in a huge bind, i gotta get Exchange Server2k up this week and i just don't think that will happen if i have this crap going on.
