Re: Replication errors - NTDS KCC
- From: "Jorge Silva" <jorgesilva_pt@xxxxxxxxxxx>
- Date: Wed, 26 Jul 2006 17:29:03 +0100
EventID 1925 is connectivity related problems:
Check:
Event ID 1925: Attempt to establish a replication link failed due to
connectivity problem
http://technet2.microsoft.com/WindowsServer/en/Library/7fcaa311-bc19-479d-9a4e-179704dfe08f1033.mspx?mfr=true
--
I hope that the information above helps you
Good Luck
Jorge Silva
MCSA
Systems Administrator
"sctrojans83" <gundamdiep@xxxxxxxxx> wrote in message
news:82DA57CD-4202-4EF9-86F5-96E97E3984FF@xxxxxxxxxxxxxxxx
Yes, all sites belong to one site link. Everything has been working well
for
about 1 1/2 years now but for some reason, it stopped working for a week
now.
We are no longer getting error 1311 but are now getting 1925 all the time
now. It looks like the Remote site cannot replicate back to the HQ site
but
HQ has no issue replicating to the Remote site. We are only having one
way
replication traffic.
"Jorge Silva" wrote:
Hi
Ensure all sites belong to at least one site link. Make sure the site
links
provide a path between all domain controllers containing a replica of a
given directory partition. Make sure "Bridge All Site Links" is set
correctly. If you have manually assigned preferred bridge-head servers,
make
sure they are online.
--
I hope that the information above helps you
Good Luck
Jorge Silva
MCSA
Systems Administrator
"sctrojans83" <gundamdiep@xxxxxxxxx> wrote in message
news:FEC18067-8CA4-450C-AC57-8944874ED2D8@xxxxxxxxxxxxxxxx
We are having issues with a remote site (RM01) not replicating data
back
to
our HQ site. From HQ to RM01 there is no issue. The two sites are
connected
via a VPN connection. All traffic between the 2 sites is allowed to
pass
freely without any ports being blocked. We are getting the following
errors
in the event viewer in the server in HQ every 15 minutes
Error 1311, Warnings 1865, 1566, 1232
The following 1311 error gave us concern.
- - - - - - - - - -
Event Type: Error
Event Source: NTDS KCC
Event Category: Knowledge Consistency Checker
Event ID: 1311
Date: 7/24/2006
Time: 1:26:30 PM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: HQW3DC2
Description:
The Knowledge Consistency Checker (KCC) has detected problems with the
following directory partition.
Directory partition:
CN=Configuration,DC=internal,DC=dhome,DC=com
There is insufficient site connectivity 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 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. For more information, see Help and
Support
Center at http://go.microsoft.com/fwlink/events.asp.
- - - - - - - - - -
We have 7 sites total and only 2 sites are having issues. We though it
may
be this issue with Windows Server SP1 and the Firewall so we applied
the
following hotfix, http://support.microsoft.com/kb/899148/en-us but that
didn't fix our issue. When then tried manually creating the Active
Directory
Connection in the Sites and Services but that did not resolve our
issue,
so
we deleted all the connections to the remote site (RM01) and let the
KCC
automatically rebuild the connections.
The KCC did recreate the <automatically generated> connections for HQ
to
RM01 and we can see this from all our DCs. But from RM01 to HQ it does
not
show an <automatically generated> connection when viewing the AD Sites
and
Services from any DC besides RM01.
So it looks like replication traffic is still flowing only in one
direction.
From HQ to RM01 is fine but nothing going the other direction. For the
past
3 hours we have not gotten any 1311 errors but warnings 1925 in random
intervals.
- - - - - - - - - -
Event Type: Warning
Event Source: NTDS KCC
Event Category: Knowledge Consistency Checker
Event ID: 1925
Date: 7/25/2006
Time: 2:38:56 PM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: HQW3DC2
Description:
The attempt to establish a replication link for the following writable
directory partition failed.
Directory partition:
CN=Configuration,DC=internal,DC=dhome,DC=com
Source domain controller:
CN=NTDS
Settings,CN=ELMW3DC1,CN=Servers,CN=ElM,CN=Sites,CN=Configuration,DC=internal,DC=decorehome,DC=com
Source domain controller address:
63cec3b5-c130-4313-805c-6a0f0d19ff4c._msdcs.internal.decorehome.com
Intersite transport (if any):
CN=IP,CN=Inter-Site
Transports,CN=Sites,CN=Configuration,DC=internal,DC=decorehome,DC=com
This domain controller will be unable to replicate with the source
domain
controller until this problem is corrected.
User Action
Verify if the source domain controller is accessible or network
connectivity
is available.
Additional Data
Error value:
1727 The remote procedure call failed and did not execute.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
- - - - - - - - - -
Any help would be greatly appreciated. Thank you.
.
- References:
- Replication errors – NTDS KCC
- From: sctrojans83
- Re: Replication errors - NTDS KCC
- From: Jorge Silva
- Re: Replication errors - NTDS KCC
- From: sctrojans83
- Replication errors – NTDS KCC
- Prev by Date: Re: PC pointing to DC in other locations
- Next by Date: Re: Home Folder Owner
- Previous by thread: Re: Replication errors - NTDS KCC
- Next by thread: Re: Home Folder Owner
- Index(es):
Relevant Pages
|
