Windows 2000 Repair NTDS.dit - Single DC no system backups available.

Hello,

My one and only Windows 2000 DC RAID controller crashed this morning and it seemed to corrupt my AD database since I am not able to log in. Upon windows services loading up I received an Issas error stating to reboot into Directory services mode..

So I did. I looked up all the NTDUTIL.EXE and ESENTUTL.EXE commands in order to repair/recover the ntds.dit db but no luck.

Command outputs generated error such as:

Operation terminated with error -1811 (JET_errFileNotFound, File not found)

Is there any special software or utility that maybe able to successfully repair this?

or am I stuck having to rebuild the server? :\

thx
tobe1424Asked:
Who is Participating?
 
tobe1424Connect With a Mentor Author Commented:
The syntax below did the trick for me. my DC is now back online.


esentutl /p "c:\winnt\ntds\ntds.dit" /!10240 /8 /v /x /o


t
0
 
Seth SimmonsConnect With a Mentor Sr. Systems AdministratorCommented:
you got a file not found error - did you specify the path/file name correctly?
if you rebuild it you will have to add your systems to the domain and create all user accounts again since you have no backup and starting from scratch
0
 
Will SzymkowskiConnect With a Mentor Senior Solution ArchitectCommented:
If you have attempted to use ESENTDSUtil and this did not fix your ntds.dit database then you are probably out of luck. You could possibly call Microsoft as they have some tools that are not released to the public which might be able to help you.

Microsoft only charges you if they correct the issue. So if you DC is worth fixing at most you would be spending approx $300.00 is Microsoft corrects the issue. If not, then you don't pay.

Out side of that if you do not have any system state backups for your AD environment or a second domain controller then you are out of luck.

Will.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
MaheshArchitectCommented:
I don't think even MS will attempt to fix the issue as 2000 is out of support OS

Not sure if premium ticket (A grade) can allow to do this but they will charge $$$ hourly basis most probably

instead I suggest you to rebuild the server from scratch may be with latest OS (Windows 2008 at minimum)

Mahesh
0
 
Will SzymkowskiSenior Solution ArchitectCommented:
Even though 2000 is out of support they should be able to do a "best efforts" attempt. MS ticekts are not hourly they are per incident.

Will.
0
 
tobe1424Author Commented:
thx for the pointers. I ended up correcting the path to c:\winnt\ntds\ntds.dit and used some other options and the repair process finished..

I opted for a chkdsk upon boot up. Now it's starting back up. let see how it goes..

I will advise shortly. Thanks again
0
 
Will SzymkowskiSenior Solution ArchitectCommented:
Great to hear!

Will.
0
 
tobe1424Author Commented:
I've requested that this question be closed as follows:

Accepted answer: 250 points for seth2740's comment #a39777483
Assisted answer: 250 points for Spec01's comment #a39777597
Assisted answer: 0 points for tobe1424's comment #a39777748

for the following reason:

the syntax entered worked correctly
0
 
tobe1424Author Commented:
i ended up discovering the correct syntax with the help of seth and spec01
0
 
tobe1424Author Commented:
seth's pointer helped me discover the correct syntax i needed in order to rebuild my AD db.
0
 
tobe1424Author Commented:
sounds good to me
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.