NTDS cannot be found, need help

[Paul Clemmons]

Here is the situation. I have a client's server, SBS2000, the C: Drive ran
out of drive space and I got the dreaded LSASS.EXE error. Following all the
directions, I deleted some of the files to now have 1.8GB free and rebooted
and still have the same error. I have followed the NTDSUTIL Knowledge Base
article and the I am getting the error that soft recovery failed because the
database could not be found. The NTDS.DIT file is there along with all the
other files that are supposed to be there. If I try to repair, recover,
move or do an integrity check in NTDSUTIL, I get the same error,
DBInitializeJetDatabase Error system database not found. I am at wits end
right now. I can't do a recovery as the third-party backup solution (Backup
Exec) will not start in safemode. I have read that the .edb file might be
the cause of this, but I am getting a bit desparate to figure out how to fix
this problem. Please anyone help.

Paul Clemmons
PC Networks

 

[Jmnts]

Hi

Did you try to run ntdsutil for:
- file maintenance: integrity
- semantic checker: go fix

Did you check if disk has virus?
Run CheckDisk for bad clusters (AD Restore mode) - chkdsk c: /x /v
Then try to move the database - Ntdsutil: - file maintenance: move db to
.....

Good Luck

 

[Paul Clemmons]

when I do the integrity, it gives me the error -1032 that the file is locked
and in use by something else.

the chkdsk had no errors. I am sort of stuck because one of the MS
suggestions is to remove the active directory, but you can't do that in safe
mode. I can't reinstall because of the Exchange server database cannot be
moved over to a new system and I can't start it because you can't in safe
mode.

Any more suggestions?

 

[Jmnts]

You can try to use the Esentutl.exe directly to resolve the problem.

Start the Server in Ad Restore Mode



To perform an integrity check.

Type the following command (including the quotation marks), and then press
ENTER: esentutl /g "path\ntds.dit"

where path is the path to the folder that contains the Ntds.dit db file. By
default, this folder is C:\Winnt\Ntds.


To repair the database:
Type the following command (including the quotation marks), and then press
ENTER: esentutl /p "path\ntds.dit"
Import: Delete the database log files from the Winnt/Ntds folder. Do not
delete or move the Ntds.dit file.


However if you're planning to remove AD you can try to recover SBS to a
different Box (Temp):

Check this MS White paper to restore SBS2000:
http://www.microsoft.com/sbserver/techinfo/administration/2000/disasterrec.mspx



Good luck

 

[Paul Clemmons]

I am getting a size mismatch with the database with the repair and stops.
Is there anyway to setup a new domain server and import the NTDS.dit and the
Exchange databases?
Thanks for all your help so far
Paul

 

[Jmnts]

Don't you have backup?

 

[Paul Clemmons]

Not of the system state if that is what you mean.

 

[Jmnts]

Ok, if you can't repair NTDS.dit, you don't have Backups (Next time do it),
all you have left is:
A parallel installation (an installation to another partition or in the new
disk on the same computer).

Check for: Recovering Without a Tape Backup
http://www.microsoft.com/technet/prodtechnol/sbs/2000/maintain/bkuprcvr.mspx

 

[Paul Clemmons]

I appreciate everything you have done so far. On the server SBS group, I
got a MSFT engineer to help out.
Thanks.

 

[Jmnts]

How did you recover ?

 

[Paul Clemmons]

Haven't yet, but I will post the results once the guy from Microsoft and I
get it straightened out.

 

[Jmnts]

Ok we'll wait

Good Luck

 

[Paul Clemmons]

Ok, Guys if you ever have this problem, try this first. Typical problem
that looks like one thing, but is actually something completely different.
This comes directly from a wonderful engineer named Steve:

1. Reboot the server and press F8. Choose Directory Services Restore Mode
from the Menu.
2. Check the physical location of the Winnt\NTDS\ folder.
3. Check the permissions on the \Winnt\NTDS folder. The default
permissions are:

Administrators - Full Control
System - Full Control

4. Check the Winnt\Sysvol\Sysvol folder to make sure it is shared.
5. Check the permissions on the Winnt\Sysvol\Sysvol share. The default
permissions are:

Share Permissions:
Administrators - Full Control
Authenticated Users - Full Control
Everyone - Read

NTFS Permissions:
Administrators - Full Control
Authenticated Users - Read & Execute, List Folder Contents,
Read
Creator Owner - none
Server Operators - Read & Execute, List Folder Contents,
Read
System - Full Control

Note: You may not be able to change the permissions on these folders if
the Active Directory database is unavailable because it is damaged,
however it is best to know if the permissions are set correctly before you
start the recovery process, as it may not be the database that is the
problem.

6. Make sure there is a folder in the Sysvol share labeled with the
correct name for their domain.
7. Open a command prompt and run NTDSUTIL to verify the paths for the
NTDS.dit file. These should match the physical structure from
Step 2

To check the file paths type the following commands:

NTDSUTIL <enter>
Files <enter>
Info <enter>

The output should look similar to:

Drive Information:

C:\ NTFS (Fixed Drive) free (2.9 Gb) total (3.9 Gb)
D:\ NTFS (Fixed Drive) free (3.6 Gb) total (3.9 Gb)

DS Path Information:

Database : C:\WINNT\NTDS\ntds.dit - 10.1 Mb
Backup dir: C:\WINNT\NTDS\dsadata.bak
Working dir: C:\WINNT\NTDS
Log dir : C:\WINNT\NTDS - 30.0 Mb total
res2.log - 10.0 Mb
res1.log - 10.0 Mb
edb.log - 10.0 Mb

This information is pulled directly from the registry and mismatched paths
will cause Active Directory not to start. Type Quit to end the NTDSUTIL
session.

8. Rename the edb.chk file and try to boot to Normal mode.

 

[Jmnts]

I'm glad you made it.