Sign in with
Sign up | Sign in
Your question

AD Replication failure - repost

Last response: in Windows 2000/NT
Share
Anonymous
May 31, 2005 6:07:27 AM

Archived from groups: microsoft.public.win2000.active_directory (More info?)

I am reposting this as these problems are really causing me grief!!

Please Help!!!

I the following AD replication errors are occurring on a weekly basis:

All servers in site
CN=Sheffield,CN=Sites,CN=Configuration,DC=centre,DC=co,DC=ph that can
replicate partition CN=Configuration,DC=centre,DC=co,DC=ph over transport
CN=SMTP,CN=Inter-Site
Transports,CN=Sites,CN=Configuration,DC=centre,DC=co,DC=ph are currently
unavailable.

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

and:

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=centre,DC=co,DC=ph, 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=centre,DC=co,DC=ph 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.

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

When I reboot the DC in the site Sheffield all works again for approx 1 week
then it fails again.

Any help would be much appreciated.

Richard


Below is one of the failure messages that I recieve in replmon.exe:

"DateTime","16/05/2005 09:42:51"
"PartnerType",">> Direct Replication Partner Data <<"
"DirectPartnerUSN","Property Update USN: 532702"
"DirectPartnerFailure","Changes have not been successfully replicated from
PH-SHEF-1 for 21 attempt(s)."
"DirectPartnerFailure","The reason is: The remote procedure call failed."
"DirectPartnerFailure","The last replication attempt was: 5/16/2005 9:14:25
AM (local)"
"DateTime","16/05/2005 10:34:13"
"USNData","532704"

If I reboot the server PH-SHEF-1 then replication begins again.

Also we don't have DNS Scavenging turned on.

Many thanks

Richard

"ptwilliams" wrote:

> Install the support tools and run replmon.exe (replication monitor).
>
> This will enable you to see if all is well or not. You need to fix any
> replication problems.
>
> However, this looks a little familiar...are you using a somewhat strict
> [DNS] scavenging routine by any chance?
>
> --
> Paul Williams
> Microsoft MVP - Windows Server - Directory Services
> http://www.msresource.net | http://forums.msresource.net
>
>
>

Just had a quick look at the replication topology and it looks a bit funny to
me.

We have 4 AD servers in 3 sites, servers 1 & 2 are in site a, server 3 is in
site b and server 4 is in site c. Server 1 is a replication partner to server
2, 3 and 4. Server 2 is a replication partner to server 1. Both server 3 & 4
are replication partners to server 1. These are all automaically created
connections. Does this seen right?

Plus, whenever these problems occur they are followed by failures in the
exchange smtp connectors that i have running between my exchange routing
groups, is the replication issues preventing smtp authentication or is it
coincidence (personaly i don't believe in coincidences)

Also, after looking through messages posted here I have run both dnslint and
a dcdiag reports and there are no errors reported.
Anonymous
June 1, 2005 1:01:48 AM

Archived from groups: microsoft.public.win2000.active_directory (More info?)

http://support.microsoft.com/default.aspx?scid=kb;en-us;899148

could be related ..


--
Andrei Ungureanu
www.eventid.net
Free Windows event logs reports
http://www.altairtech.ca/evlog/

"Richardw" <Richardw@discussions.microsoft.com> wrote in message
news:D 1FA02A3-A59D-4CBD-A212-98FC1344EEAB@microsoft.com...
>I am reposting this as these problems are really causing me grief!!
>
> Please Help!!!
>
> I the following AD replication errors are occurring on a weekly basis:
>
> All servers in site
> CN=Sheffield,CN=Sites,CN=Configuration,DC=centre,DC=co,DC=ph that can
> replicate partition CN=Configuration,DC=centre,DC=co,DC=ph over transport
> CN=SMTP,CN=Inter-Site
> Transports,CN=Sites,CN=Configuration,DC=centre,DC=co,DC=ph are currently
> unavailable.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
> and:
>
> 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=centre,DC=co,DC=ph, 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=centre,DC=co,DC=ph 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.
>
> For more information, see Help and Support Centre at
> http://go.microsoft.com/fwlink/events.asp.
>
> When I reboot the DC in the site Sheffield all works again for approx 1
> week
> then it fails again.
>
> Any help would be much appreciated.
>
> Richard
>
>
> Below is one of the failure messages that I recieve in replmon.exe:
>
> "DateTime","16/05/2005 09:42:51"
> "PartnerType",">> Direct Replication Partner Data <<"
> "DirectPartnerUSN","Property Update USN: 532702"
> "DirectPartnerFailure","Changes have not been successfully replicated from
> PH-SHEF-1 for 21 attempt(s)."
> "DirectPartnerFailure","The reason is: The remote procedure call failed."
> "DirectPartnerFailure","The last replication attempt was: 5/16/2005
> 9:14:25
> AM (local)"
> "DateTime","16/05/2005 10:34:13"
> "USNData","532704"
>
> If I reboot the server PH-SHEF-1 then replication begins again.
>
> Also we don't have DNS Scavenging turned on.
>
> Many thanks
>
> Richard
>
> "ptwilliams" wrote:
>
>> Install the support tools and run replmon.exe (replication monitor).
>>
>> This will enable you to see if all is well or not. You need to fix any
>> replication problems.
>>
>> However, this looks a little familiar...are you using a somewhat strict
>> [DNS] scavenging routine by any chance?
>>
>> --
>> Paul Williams
>> Microsoft MVP - Windows Server - Directory Services
>> http://www.msresource.net | http://forums.msresource.net
>>
>>
>>
>
> Just had a quick look at the replication topology and it looks a bit funny
> to
> me.
>
> We have 4 AD servers in 3 sites, servers 1 & 2 are in site a, server 3 is
> in
> site b and server 4 is in site c. Server 1 is a replication partner to
> server
> 2, 3 and 4. Server 2 is a replication partner to server 1. Both server 3 &
> 4
> are replication partners to server 1. These are all automaically created
> connections. Does this seen right?
>
> Plus, whenever these problems occur they are followed by failures in the
> exchange smtp connectors that i have running between my exchange routing
> groups, is the replication issues preventing smtp authentication or is it
> coincidence (personaly i don't believe in coincidences)
>
> Also, after looking through messages posted here I have run both dnslint
> and
> a dcdiag reports and there are no errors reported.
>
Anonymous
June 1, 2005 11:16:03 AM

Archived from groups: microsoft.public.win2000.active_directory (More info?)

Thanks for this, unfortunately it doesn't help as we are using Windows 2000
Server on SP4 and all servers are on a private WAN and therefore do not route
through either a firewall or a VPN.

Also, these servers have been running fine for the past 12 - 14 months and
there have been no configuration changes.

"Andrei Ungureanu" wrote:

> http://support.microsoft.com/default.aspx?scid=kb;en-us;899148
>
> could be related ..
>
>
> --
> Andrei Ungureanu
> www.eventid.net
> Free Windows event logs reports
> http://www.altairtech.ca/evlog/
>
> "Richardw" <Richardw@discussions.microsoft.com> wrote in message
> news:D 1FA02A3-A59D-4CBD-A212-98FC1344EEAB@microsoft.com...
> >I am reposting this as these problems are really causing me grief!!
> >
> > Please Help!!!
> >
> > I the following AD replication errors are occurring on a weekly basis:
> >
> > All servers in site
> > CN=Sheffield,CN=Sites,CN=Configuration,DC=centre,DC=co,DC=ph that can
> > replicate partition CN=Configuration,DC=centre,DC=co,DC=ph over transport
> > CN=SMTP,CN=Inter-Site
> > Transports,CN=Sites,CN=Configuration,DC=centre,DC=co,DC=ph are currently
> > unavailable.
> >
> > For more information, see Help and Support Center at
> > http://go.microsoft.com/fwlink/events.asp.
> >
> > and:
> >
> > 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=centre,DC=co,DC=ph, 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=centre,DC=co,DC=ph 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.
> >
> > For more information, see Help and Support Centre at
> > http://go.microsoft.com/fwlink/events.asp.
> >
> > When I reboot the DC in the site Sheffield all works again for approx 1
> > week
> > then it fails again.
> >
> > Any help would be much appreciated.
> >
> > Richard
> >
> >
> > Below is one of the failure messages that I recieve in replmon.exe:
> >
> > "DateTime","16/05/2005 09:42:51"
> > "PartnerType",">> Direct Replication Partner Data <<"
> > "DirectPartnerUSN","Property Update USN: 532702"
> > "DirectPartnerFailure","Changes have not been successfully replicated from
> > PH-SHEF-1 for 21 attempt(s)."
> > "DirectPartnerFailure","The reason is: The remote procedure call failed."
> > "DirectPartnerFailure","The last replication attempt was: 5/16/2005
> > 9:14:25
> > AM (local)"
> > "DateTime","16/05/2005 10:34:13"
> > "USNData","532704"
> >
> > If I reboot the server PH-SHEF-1 then replication begins again.
> >
> > Also we don't have DNS Scavenging turned on.
> >
> > Many thanks
> >
> > Richard
> >
> > "ptwilliams" wrote:
> >
> >> Install the support tools and run replmon.exe (replication monitor).
> >>
> >> This will enable you to see if all is well or not. You need to fix any
> >> replication problems.
> >>
> >> However, this looks a little familiar...are you using a somewhat strict
> >> [DNS] scavenging routine by any chance?
> >>
> >> --
> >> Paul Williams
> >> Microsoft MVP - Windows Server - Directory Services
> >> http://www.msresource.net | http://forums.msresource.net
> >>
> >>
> >>
> >
> > Just had a quick look at the replication topology and it looks a bit funny
> > to
> > me.
> >
> > We have 4 AD servers in 3 sites, servers 1 & 2 are in site a, server 3 is
> > in
> > site b and server 4 is in site c. Server 1 is a replication partner to
> > server
> > 2, 3 and 4. Server 2 is a replication partner to server 1. Both server 3 &
> > 4
> > are replication partners to server 1. These are all automaically created
> > connections. Does this seen right?
> >
> > Plus, whenever these problems occur they are followed by failures in the
> > exchange smtp connectors that i have running between my exchange routing
> > groups, is the replication issues preventing smtp authentication or is it
> > coincidence (personaly i don't believe in coincidences)
> >
> > Also, after looking through messages posted here I have run both dnslint
> > and
> > a dcdiag reports and there are no errors reported.
> >
>
>
>
June 9, 2005 2:41:50 PM

Archived from groups: microsoft.public.win2000.active_directory (More info?)

Maybe you can try this:

http://support.microsoft.com/kb/898060



"Richardw" <Richardw@discussions.microsoft.com> wrote in message
news:2447AE15-FC76-456F-ABCB-EF3B82A5886D@microsoft.com...
> Thanks for this, unfortunately it doesn't help as we are using Windows
> 2000
> Server on SP4 and all servers are on a private WAN and therefore do not
> route
> through either a firewall or a VPN.
>
> Also, these servers have been running fine for the past 12 - 14 months and
> there have been no configuration changes.
>
> "Andrei Ungureanu" wrote:
>
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;899148
>>
>> could be related ..
>>
>>
>> --
>> Andrei Ungureanu
>> www.eventid.net
>> Free Windows event logs reports
>> http://www.altairtech.ca/evlog/
>>
>> "Richardw" <Richardw@discussions.microsoft.com> wrote in message
>> news:D 1FA02A3-A59D-4CBD-A212-98FC1344EEAB@microsoft.com...
>> >I am reposting this as these problems are really causing me grief!!
>> >
>> > Please Help!!!
>> >
>> > I the following AD replication errors are occurring on a weekly basis:
>> >
>> > All servers in site
>> > CN=Sheffield,CN=Sites,CN=Configuration,DC=centre,DC=co,DC=ph that can
>> > replicate partition CN=Configuration,DC=centre,DC=co,DC=ph over
>> > transport
>> > CN=SMTP,CN=Inter-Site
>> > Transports,CN=Sites,CN=Configuration,DC=centre,DC=co,DC=ph are
>> > currently
>> > unavailable.
>> >
>> > For more information, see Help and Support Center at
>> > http://go.microsoft.com/fwlink/events.asp.
>> >
>> > and:
>> >
>> > 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=centre,DC=co,DC=ph, 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=centre,DC=co,DC=ph 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.
>> >
>> > For more information, see Help and Support Centre at
>> > http://go.microsoft.com/fwlink/events.asp.
>> >
>> > When I reboot the DC in the site Sheffield all works again for approx 1
>> > week
>> > then it fails again.
>> >
>> > Any help would be much appreciated.
>> >
>> > Richard
>> >
>> >
>> > Below is one of the failure messages that I recieve in replmon.exe:
>> >
>> > "DateTime","16/05/2005 09:42:51"
>> > "PartnerType",">> Direct Replication Partner Data <<"
>> > "DirectPartnerUSN","Property Update USN: 532702"
>> > "DirectPartnerFailure","Changes have not been successfully replicated
>> > from
>> > PH-SHEF-1 for 21 attempt(s)."
>> > "DirectPartnerFailure","The reason is: The remote procedure call
>> > failed."
>> > "DirectPartnerFailure","The last replication attempt was: 5/16/2005
>> > 9:14:25
>> > AM (local)"
>> > "DateTime","16/05/2005 10:34:13"
>> > "USNData","532704"
>> >
>> > If I reboot the server PH-SHEF-1 then replication begins again.
>> >
>> > Also we don't have DNS Scavenging turned on.
>> >
>> > Many thanks
>> >
>> > Richard
>> >
>> > "ptwilliams" wrote:
>> >
>> >> Install the support tools and run replmon.exe (replication monitor).
>> >>
>> >> This will enable you to see if all is well or not. You need to fix
>> >> any
>> >> replication problems.
>> >>
>> >> However, this looks a little familiar...are you using a somewhat
>> >> strict
>> >> [DNS] scavenging routine by any chance?
>> >>
>> >> --
>> >> Paul Williams
>> >> Microsoft MVP - Windows Server - Directory Services
>> >> http://www.msresource.net | http://forums.msresource.net
>> >>
>> >>
>> >>
>> >
>> > Just had a quick look at the replication topology and it looks a bit
>> > funny
>> > to
>> > me.
>> >
>> > We have 4 AD servers in 3 sites, servers 1 & 2 are in site a, server 3
>> > is
>> > in
>> > site b and server 4 is in site c. Server 1 is a replication partner to
>> > server
>> > 2, 3 and 4. Server 2 is a replication partner to server 1. Both server
>> > 3 &
>> > 4
>> > are replication partners to server 1. These are all automaically
>> > created
>> > connections. Does this seen right?
>> >
>> > Plus, whenever these problems occur they are followed by failures in
>> > the
>> > exchange smtp connectors that i have running between my exchange
>> > routing
>> > groups, is the replication issues preventing smtp authentication or is
>> > it
>> > coincidence (personaly i don't believe in coincidences)
>> >
>> > Also, after looking through messages posted here I have run both
>> > dnslint
>> > and
>> > a dcdiag reports and there are no errors reported.
>> >
>>
>>
>>
!