FN-GM Posted January 19, 2009 Posted January 19, 2009 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 Posted January 19, 2009 Author Posted January 19, 2009 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 Posted January 19, 2009 Posted January 19, 2009 Try using the MS Replication Diganosis Tools, it can be downloaded from: http://www.microsoft.com/downloads/details.aspx?FamilyID=96a35011-fd83-419d-939b-9a772ea2df90&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 Posted January 19, 2009 Posted January 19, 2009 I've had it whereby the File Replication Service has stopped, but not become disabled.
DMcCoy Posted January 19, 2009 Posted January 19, 2009 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 Posted January 19, 2009 Author Posted January 19, 2009 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 Posted January 19, 2009 Posted January 19, 2009 I have used this before: http://www.microsoft.com/DOWNLOADS/details.aspx?familyid=61ACB9B9-C354-4F98-A823-24CC0DA73B50&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 Posted January 19, 2009 Posted January 19, 2009 You can manually force a replication, does this help?
FN-GM Posted January 19, 2009 Author Posted January 19, 2009 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 Posted January 19, 2009 Posted January 19, 2009 Your NETLOGON service didn't pause as well did it?
Michael Posted January 19, 2009 Posted January 19, 2009 You could always reboot both servers if you haven't already.
FN-GM Posted January 19, 2009 Author Posted January 19, 2009 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 Posted January 19, 2009 Posted January 19, 2009 Did you fix the problem that caused it to pause? =) replication hates usnRollbacks (which usually cause netlogon to pause....)
FN-GM Posted January 19, 2009 Author Posted January 19, 2009 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 Posted January 19, 2009 Posted January 19, 2009 Not sure on that one, when ours paused through an epic config fail (by me ) 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 (helps if you get the third to replicate!))
FN-GM Posted January 19, 2009 Author Posted January 19, 2009 what a pain this is bening, but i think i have found a solution... http://uzar.files.wordpress.com/2007/08/daemon_hammer.jpg Does anyone have any more advice please?
DrPerceptron Posted January 19, 2009 Posted January 19, 2009 that guy gets all the work! Have you done dcdiag and netdiag on all your DC's and they didn't have any errors? There's a replication tool somewhere too... repladmin?
FN-GM Posted January 19, 2009 Author Posted January 19, 2009 ah ha i think i have found it, i thinkmy hard drive has a bad block. Could that be it? Thanks
Ric_ Posted January 19, 2009 Posted January 19, 2009 Did you run the Ultrasound tool that ChrisH suggested? That tool is the bomb... it even tells you how to fix the problems!
ChrisH Posted January 19, 2009 Posted January 19, 2009 Did you run the Ultrasound tool that ChrisH suggested? That tool is the bomb... it even tells you how to fix the problems! It's true. I have never had an MS tool that tells me whats wrong and then how to easily fix it!
FN-GM Posted January 20, 2009 Author Posted January 20, 2009 I haven't no, the reason is i am still messing round with AD. in the event log i am getting this now: The Active Directory Domain Services database has been restored using an unsupported restoration procedure. Active Directory Domain Services will be unable to log on users while this condition persists. As a result, the Net Logon service has paused. User Action See previous event logs for details. and i see this message on the server screen, any input is appreciated.untitled.bmp
FN-GM Posted January 21, 2009 Author Posted January 21, 2009 The problem is the server that is throwing up the error messages is the only DC with the netlogon folder. looks like there is a USN rollback, no idea how its happened, i was only adding a new DC by demoting the old one and putting the new one on. is there a way to recover with just this DC? other DC's have the AD upto date and replicate fine in active directory of sites and services. thanks
FN-GM Posted January 21, 2009 Author Posted January 21, 2009 The only thing i can think of now is some how force the sysvol to replicate then demote the bad DC. what do you think?
SYNACK Posted January 21, 2009 Posted January 21, 2009 You could try backing up a good DC and then performing an authoritive restore on it, this should make the good DCs values override anything that has come before: How to Restore Windows Server 2003 Active Directory Authoritative Restore Windows Active Directory NTDSutil Performing an Authoritative Restore of Active Directory Objects: Active Directory
FN-GM Posted January 21, 2009 Author Posted January 21, 2009 You could try backing up a good DC and then performing an authoritive restore on it, this should make the good DCs values override anything that has come before: How to Restore Windows Server 2003 Active Directory Authoritative Restore Windows Active Directory NTDSutil Performing an Authoritative Restore of Active Directory Objects: Active Directory The problem is the only DC with the sysvol folder is the bad one throwing up the errors. Thanks
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now