Solved

event id: 1787

Posted on 2009-04-10
3
912 Views
Last Modified: 2012-05-06
I am getting an error on a Windows 2003 domain controller that it says it cannor communicate with a dc on the network. This is a dc tyhat was demoted and removed from the system. I am now getting errors from the global catalog server that says baisicly that it can no longer communicate with this server and it is correct because this server does not exist anymore. Below you will find some of the error information that I get out of the directory services section of the event viewer

The site link bridge object CN=WestDC to York,CN=IP,CN=Inter-Site Transports,CN=Sites,CN=Configuration,DC=aaron,DC=local contains fewer than two sites links. The site link bridge will be ignored.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

The following site link bridge object references a site link, but that site link was not found in the Knowledge Consistency Checker (KCC) master list of site links.
 
Site link bridge object:
CN=WestDC to York,CN=IP,CN=Inter-Site Transports,CN=Sites,CN=Configuration,DC=aaron,DC=local
Site link:
CN=Hwy76 to York,CN=IP,CN=Inter-Site Transports,CN=Sites,CN=Configuration,DC=aaron,DC=local
 
This may affect the ability to generate intersite topology.

For more information, see Help and Support Center at
0
Comment
Question by:rehooks
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 57

Assisted Solution

by:Mike Kline
Mike Kline earned 100 total points
ID: 24116942
Was this box cleanly demoted, if not you may have to go and run a metadata cleanup
http://support.microsoft.com/kb/216498
Also did you delete the old DC out of sites and servcies?
Thanks
Mike
0
 

Author Comment

by:rehooks
ID: 24121070
DCPROMO ran without errors when the DC was demoted. The KCC errors started after the demotion. I will look at The link provided when I get back to the office on Monday (off now for Easter holiday).

Thanks
Bob
0
 

Accepted Solution

by:
rehooks earned 0 total points
ID: 24142852
I have been able to resolve the problem. There were 2 obsolete site link bridge setting in the
Sites and Services
  Inter-Site Transports
     IP

I deleted the obsolete site link bridges and and the errors stopped.
 
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article outlines the process to identify and resolve account lockout in an Active Directory environment.
Did you know that more than 4 billion data records have been recorded as lost or stolen since 2013? It was a staggering number brought to our attention during last week’s ManageEngine webinar, where attendees received a comprehensive look at the ma…
This tutorial will walk an individual through the process of configuring their Windows Server 2012 domain controller to synchronize its time with a trusted, external resource. Use Google, Bing, or other preferred search engine to locate trusted NTP …
This video shows how to use Hyena, from SystemTools Software, to bulk import 100 user accounts from an external text file. View in 1080p for best video quality.

705 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question