Event ID: 1312 - Please Help

D

Dave Richie

I inherited a small network with a flat domain structure
in 3 different subnets. I keep getting errors Event ID
1312 on one of the servers. After I got to looking,
someone has "cleaned up" really well, and all of the NTDS
connections are gone if I look with the sites and
services snapin. I have tried to manually re-create links
after finding out that all 6 servers in the forest had no
connections specified. Apparently, I am doing something
wrong, I can't seem to get it working again. I will
include the event log entry below. I have read some of
the white sheets, but being pretty new to AD, I'm having
a bit of trouble. Can anyone give me step-by-step's on
how to re-create the topology manually ?
Help on this would be GREATLY appreciated. Please cc
replies to my email if you can (e-mail address removed)

Thanks, and have a great day

Dave Richie
========================
Event Type: Error
Event Source: NTDS KCC
Event Category: Knowledge Consistency Checker
Event ID: 1311
Date: 8/1/2003
Time: 8:14:00 AM
User: N/A
Computer: RLSSERVER
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=coht,DC=com, 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).
---snipped------


================================
Event Type: Error
Event Source: NTDS KCC
Event Category: Knowledge Consistency Checker
Event ID: 1312
Date: 8/1/2003
Time: 8:14:00 AM
User: N/A
Computer: RLSSERVER
Description:
The call to the Intersite Messaging Service (ISM)
specifying the transport CN=IP,CN=Inter-Site
Transports,CN=Sites,CN=Configuration,DC=coht,DC=com
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 º...

==========================
 
T

Tim Springston \(MSFT\)

This message indicates that you may have a connectivity issue on one or more
of your DCs, most likely caused by a DNS problem.

Do you have these problems on all DCs or just some? On the affected
machines, does a NETDIAG /V (from the support tools) show any problems?

--
Tim Springston
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.
I inherited a small network with a flat domain structure
in 3 different subnets. I keep getting errors Event ID
1312 on one of the servers. After I got to looking,
someone has "cleaned up" really well, and all of the NTDS
connections are gone if I look with the sites and
services snapin. I have tried to manually re-create links
after finding out that all 6 servers in the forest had no
connections specified. Apparently, I am doing something
wrong, I can't seem to get it working again. I will
include the event log entry below. I have read some of
the white sheets, but being pretty new to AD, I'm having
a bit of trouble. Can anyone give me step-by-step's on
how to re-create the topology manually ?
Help on this would be GREATLY appreciated. Please cc
replies to my email if you can (e-mail address removed)

Thanks, and have a great day

Dave Richie
========================
Event Type: Error
Event Source: NTDS KCC
Event Category: Knowledge Consistency Checker
Event ID: 1311
Date: 8/1/2003
Time: 8:14:00 AM
User: N/A
Computer: RLSSERVER
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=coht,DC=com, 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).
---snipped------


================================
Event Type: Error
Event Source: NTDS KCC
Event Category: Knowledge Consistency Checker
Event ID: 1312
Date: 8/1/2003
Time: 8:14:00 AM
User: N/A
Computer: RLSSERVER
Description:
The call to the Intersite Messaging Service (ISM)
specifying the transport CN=IP,CN=Inter-Site
Transports,CN=Sites,CN=Configuration,DC=coht,DC=com
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 º...

==========================
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Event ID 1566 - NTDS KCC 1
Knowledge consistency checker issues Win2K server 3
event id 1265 2
active directory replication not worked 4
NTDS KCC Error 5
Active Directory Replication Problem... 0
AD Replication Problem 2
KCC event ID 1567 3

Top