Re: AD crash

If there are no other services than AD on this box and you have other dc's
from the same domain then I would demote this server and repromote and let
DS replication fix your problems.

--
Paul Bergson
MVP - Directory Services
MCTS, MCT, MCSE, MCSA, Security+, BS CSci
2008, 2003, 2000 (Early Achiever), NT4

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.

"sean" <azsean@xxxxxxxxxxx> wrote in message
news:OOLle$ZwIHA.3968@xxxxxxxxxxxxxxxxxxxxxxx
Hello
Thank you for your replies.
I already have a second dc within my domain. I have 3 DC which 2 are
running Win2000 and 1 is running Win2003.

After the error about DS could not be started, I clicked OK and server
started to reboot. I unplugged the NIC and plugged
it to a seperate switch which is isolated from my network. My network
still up and running since the other 2 DC are still running..
After the server was rebooted, I didn't get the error about DS could not
be started anymore. Instead I got an error about WINS database
is corrupted, etc. We had WINS server running because of old NT4 and
Exchange 5.5. We no longer have NT4 and Exchange 5 since
we are in AD w/ DNS now and Exchange 2003.

I also checked WINNT\NTDS folder and NTDS.DIT does exist.

I stopped the WINS services. After looking at the event viewer, I am some
error messages like:

in application viewer:
event id 427 source: esent
ntfrs (1052) c:\winnt\ntfrs\jet\temp\tmp.edbThe database engine could not
access the file called %4.
event id: 439
ntfrs (1052) c:\winnt\ntfrs\jet\temp\tmp.edbUnable to write a shadowed
header for file %4. Error %5.
event id: 454
ntfrs (1052) -1032Database recovery/restore failed with unexpected error
%4.

in system viewer:
event id: 7023
The File Replication Service service terminated with the following error:
Insufficient system resources exist to complete the requested service.

and in Directory Service event viewer
I have some red event id of 1311 and warning of 1566.

My question is this. Should I just plug the NIC of this server back to
the same network and do a full replication
and wait till everything syncs up again.
Or should I reboot the server into directory service restore mode and use
backupexec to restore the AD?

Thanks in advance








"Paul Bergson [MVP-DS]" <pbergson@xxxxxxxxxxxxxxxxx> wrote in message
news:ulrr2zYwIHA.420@xxxxxxxxxxxxxxxxxxxxxxx
No you can't copy ntds.dit from machine to machine, it doesn't work that
way. Even if it did you have a separate domain so the dit is not even
have the same domain objects. Either do a restore -or- if you have a
second dc from within the domain (Which it doesn't sound like you have)
clean up metadata, seize and roles and promote a new dc. Otherwise you
are stuck having to restore the old machine from the errors you are
receiving.

--
Paul Bergson
MVP - Directory Services
MCTS, MCT, MCSE, MCSA, Security+, BS CSci
2008, 2003, 2000 (Early Achiever), NT4

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no
rights.

"sean" <azsean@xxxxxxxxxxx> wrote in message
news:%23zJ1wCSwIHA.1936@xxxxxxxxxxxxxxxxxxxxxxx
Hi

I have 3 domains controllers running Windows 2000 and 2000 servers.

DomainA server running Windows 2000 Server w/ Sp4.
DomainB server running Windows 2003 server w/ sp2
DomainC server running Windows 2000 Server w/ Sp4

Few days ago, DomainA crashed and bluescreen. Nothing was changed on
this server. Just out of blue, got a blue screen with
inaccessible_boot_device
0x0000007b (0x88fe0850, 0xc0000032, and 0x0000000, 0x0000000)

I did a fdisk /mbr and problem still was the same. I placed the original
win2000 server cd, boot, went into recover mode. Server rebooted
itself and did a chkdsk. Then rebooted itself and gave me an error.

lsass.exe
Directory Services could not start because of the following error: The
system cannot find the file specified. Error Status: 0xc000000f. Please
click OK to shutdown the system and reboot into the Directory Services
Restore Mode, check the event log for more detailed information.

I do have a backup of this server using veritas backup exec. I usually
backup active directory, boot files, com+ class, registery, and sysvol.

After doing some reading, it seems like NTDS.DIT might be missing or
corrupt. Can I copy the NTDS.DIT from the Windows 2003 Server domainB
server into it if I do directory restore mode? If not, can I copy the
NTDS.DIT from Windows 2000 Server domainC?

The FSMO roles on my network is.

DomainB is Schema Owner
DomainB is Domain Role owner
DomainA is PDC role
DomainA is RID pool manager
DomainA is Infrastructure owner

Domain C is just a domain controller with no roles.
Thanks in advance







.

Relevant Pages