Replication Problems

[FN-GM]

Hi

My 2 DC's are not replicating, lovely!

i am getting this in the event log

Outbound replication has been disabled by the user.
Event ID: 1115

I haven't disabled it, not sure how its got this way. Any ideas how to get it moving again please?

I am running Windows Server 2008 & Windows Server 2003 DC's

Thanks in advance

[FN-GM]

all sorted now used this site

Disabling AD Replication - blog.scottlowe.org - The weblog of an IT pro specializing in virtualization, storage, and servers

Does anyone know how it managed to disbale itself?

[danrhodes]

Try using the MS Replication Diganosis Tools, it can be downloaded from:

http://www.microsoft.com/downloads/d...DisplayLang=en

Let me know how it goes, please also check that your replication process hasn't crashed and just needs re-starting.

D

[Michael]

I've had it whereby the File Replication Service has stopped, but not become disabled.

[DMcCoy]

Replication will also be stopped during backup, so if it happens at this time the event is normal, although it should begin again after the system state is finished.

[FN-GM]

Replication seems to be running and so does the file replication service. The AD seems to be replicating just fine. Now sysvol isn't playing, when i put i new script in netlogon it is not replicating over to the other DC even after a few hours.

I can't see anything in the event log, has anyone got any suggestions?

Thanks.

Z

[ChrisH]

I have used this before:

http://www.microsoft.com/DOWNLOADS/d...displaylang=en

Tells you a lot of info on the replication status etc. It also tells you about stuff that doesn't come up in the event log and provides a good explanation! It does need a MSDE instance though.

[Michael]

You can manually force a replication, does this help?

[FN-GM]

I have used this before:

Download details: Ultrasound - Monitoring and Troubleshooting Tool for File Replication Service (FRS)

Tells you a lot of info on the replication status etc. It also tells you about stuff that doesn't come up in the event log and provides a good explanation! It does need a MSDE instance though.

Thanks will give that a go

You can manually force a replication, does this help?

First thing i tried, thanks

[DrPerceptron]

Your NETLOGON service didn't pause as well did it?

[Michael]

You could always reboot both servers if you haven't already.

[FN-GM]

Your NETLOGON service didn't pause as well did it?

It was paused a few days ago i started it back up again


Done a reboot

[DrPerceptron]

Did you fix the problem that caused it to pause? =)

replication hates usnRollbacks (which usually cause netlogon to pause....)

[FN-GM]

Did you fix the problem that caused it to pause? =)

replication hates usnRollbacks (which usually cause netlogon to pause....)

I couldn't find why it was like that i just started it again.

What do i do to get it working?

Many thanks

Z

[DrPerceptron]

Not sure on that one, when ours paused through an epic config fail (by me :P) there were events logged somewhere as NTDS General ID 2103 (?)

We fixed ours forcing a repl from a good DC to the bad DC and it's been very happy since (after fixing my config mishap :P (helps if you get the third to replicate!))