RE: [ActiveDir] AD restore mode

[Fugleberg, David A]

We had one DC that exhibited similar problems a few months ago...every 15 minutes it would reboot.  The event log indicated it was a problem with not being able to apply a change in one of the naming contexts to the local NTDS database (NTDS Replication Event 1084) each time.  Repadmin /showreps showed that the other naming contexts were replicating fine, but that one was not.  We finally did a non-authoritative restore from the backup on that one DC, and let it replicate everything that had changed since the backup.  The problem has not come back.  Further research I did later indicated that it was a corruption of the AD on that DC, and that we may have been able to repair it with NTDSUtil, but the restore worked.  The explanation of the above event on eventid.net has a comment that explains the repair procedure.  Good luck ! Dave -----Original Message----- From: Rinehart, Ken [mailto:[EMAIL PROTECTED]] Sent: Friday, March 15, 2002 1:03 PM To: '[EMAIL PROTECTED]' Subject: RE: [ActiveDir] AD restore mode The machine has been rebooting itself in an edless loop for at least a month.  I just stumbled upon it because it's located in an area that isn't visited much.  I haven't seen anything weird in AD other than a mention of not being able to replicate to all DCs in the site which may explain why I was getting that error.  Looks like it's back to doing the same thing again.  What is the best way to rebuild this guy?  Wipe it clean, reinstall W2K server then DCPROMO using the same name it had? Ken -----Original Message----- From: SALANDRA, JUSTIN [mailto:[EMAIL PROTECTED]] Sent: Friday, March 15, 2002 10:46 AM To: '[EMAIL PROTECTED]' Subject: RE: [ActiveDir] AD restore mode You may have to cease the roll of that operation master to a different role for the time being.  It sounds like the machine is just not liking you right now.  What were you doing before this happened on the machine?   Justin A. Salandra, MCSE Senior Network Engineer Catholic Healthcare System 914.681.8117 office 646.483.3325 cell [EMAIL PROTECTED]     -----Original Message----- From: Rinehart, Ken [mailto:[EMAIL PROTECTED]] Sent: Friday, March 15, 2002 1:38 PM To: '[EMAIL PROTECTED]' Subject: RE: [ActiveDir] AD restore mode   Interesting.  Well after playing around I figured out a way to "fix" the database on that machine using eseututl   This infact cleared up the inconsistancies in the DB and now the machine will boot up but I can't login!  Administrator passwords don't work. It doesn't help that we don't know much about this machine. I believe it is the forest and infrastructure controller for our root domain.   Ken -----Original Message----- From: SALANDRA, JUSTIN [mailto:[EMAIL PROTECTED]] Sent: Friday, March 15, 2002 10:17 AM To: '[EMAIL PROTECTED]' Subject: RE: [ActiveDir] AD restore mode Your restore won’t mean anything if you do not go into ntdsutil and make that servers copy of AD the authoritative copy that will be replicated to all other servers.   Do all the other servers have the same issue?  If they don’t then I don’t think it is an issue with AD, it may just be an issue with the OS of the server or something else to that affect.  Remember that if you end up having to rebuild the machine, you need to clean up the metadatabase before re dcpromoing the DC with the same name.  You only need to do this if you can’t run dcpromo on the machine prior to rebuilding it.   Justin A. Salandra, MCSE Senior Network Engineer Catholic Healthcare System 914.681.8117 office 646.483.3325 cell [EMAIL PROTECTED]     -----Original Message----- From: Rinehart, Ken [mailto:[EMAIL PROTECTED]] Sent: Friday, March 15, 2002 12:23 PM To: [EMAIL PROTECTED] Subject: [ActiveDir] AD restore mode     Anyone familiar with using the AD restore mode?  I have an issue with a domain controller that boots up to an error stating that SAM initilization failed because AD couldn't start.  Get a hex error 0xc00002e1.  I've got a few tech articles on the MS site but don't really address the issue.  I'm guessing that I'll need to restore the AD from a backup off of another machine?  Is this correct?  And is authoratative the right way to go in this case since this isn't the 1st DC in my domain I've got 3 or 4 others.   Thanks Ken