Crashed DC/FSMO ROLL HOLDER!!!

[Guest]

I have a Dell 2550 whose RAID5 drive array came off line. Dell replaced SCSII
card, MB, SCSII RAM, SCSII Key, etc.
When booting system did a chkdsk before I could stop it, so I let it run. I
was then unable to get server to boot, received stop error [ Security
Accounts Manager failed. Directrory Service cannot start Error Status
0xc00002e1] . I decided to copy system, software, sam, security, and default
from repair folder. This process rolled server back to pre-AD. I copied back
up I made of these files back and system is in a constant reboot loop. Just
before logon screen appears...system reboots. I tried to do a Directory
service Repair from F8 menu but cannot find a DC...although two others exist.
{I did have to add a new Global catalog to Domain after crash BTW}
I have a system state B/U I made prior to crash and a B/U of registery from
a few weeks ago.
I have tried many utilities to restore B/U of registry [*.reg file]
unsuccessfully.
I am thinking of installing 2000 server on D: partition, installing BackUp
Exec, and trying to do a system restore from B/U tape to C:\.
Does anyone have any other suggestions? Is there any steps I'm missing when
I go to restore system state B/U to C: from OS loaded to D:?
If I do need to re-install...Is my ONLY option then to seize FSMO rolls
[shudder]?
Thanks for y'all's input in advance!
JJ

 

[Frank Szita [MSFT]]

The LSASS error you described is usually caused by a corrupted active
directory database. Given that you have other working domain controllers
you can use a force removal process of active directory which will maintain
the software on your server without having to perform a reinstall. Follow
the section "If the domain controller cannot start in normal mode" in
Microsoft Knowledge Base article 332199 "Using the DCPROMO /FORCEREMOVAL
Command to Force the Demotion of Active Directory"
(http://support.microsoft.com/?id=332199)

Before you repromote the server as a domain controller you will have to
seize all of the FSMO roles to another domain controller and removed the
problem server from active directory.

To seize FSMO Roles:
255504 "Using Ntdsutil.exe to seize or transfer FSMO roles to a domain
controller" (http://support.microsoft.com/?id=255504)

To perform metadata cleanup:
216498 "How to remove data in Active Directory after an unsuccessful
domain" (http://support.microsoft.com/?id=216498)

Best regards,

Frank Szita [MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights.