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.

8. Rename the edb.chk file and try to boot to Normal mode. If that fails, proceed with the next steps.

9. Reboot into Directory Services Restore mode again. At the command prompt, use the ESENTUTL to check the integrity of the database. NOTE: You can use NTDSUTIL to check the Integrity, however esentutl is usually more reliable. Type the following command:
ESENTUTL /g “\NTDS.dit” /!10240 /8 /v /x /o (Note: Type the path without the quotes). Note: The default path would be C:\Winnt\NTDS\ntds.dit; however it may be different in some cases. The output will tell you if the database is inconsistent and may produce
a jet_error 1206 stating that the database is corrupt. If the database is inconsistent or corrupt it will need to be recovered or repaired . To recover the database type the following at the command prompt: NTDSUTIL Files Recover If this fails with an error,
type quit until back at the command prompt and repair the database using ESENTUTL by typing the following: ESENTUTL /p “\NTDS.dit” /!10240 /8 /v /x /o (Note: Type the path without the quotes). Note: If you do not put the switches at the end of the command
you will most likely get a Jet_error 1213 “Page size mismatch” error.

10. Delete the log files in the NTDS directory, but do not delete or move the ntds.dit file.

11. The NTDSUTIL tool needs to be run again to check the Integrity of the database and to perform a Semantic Database analysis. To check the integrity, at the command prompt type: NTDSUTIL Files Integrity The output should tell you that the integrity check
completed successfully and prompt that you should perform a Semantic Database Analysis. Type quit. To perform the Semantic Database Analysis type the following at the NTDSUTIL Prompt type: Semantic Database Analysis Go The output will tell you that the Analysis
completed successfully. Type quit and closes the command prompt. NOTE: If you get errors running the Analysis then type the following at the semantic checker prompt: semantic checker: go fix This puts the checker in Fixup mode, which should fix whatever errors
there were.

12. Reboot the server to Normal Mode. If any of these steps fail to recover the database the only alternative is to perform an Authoritative System State restore from backup in Directory Services Restore mode. For more information, please refer to the following
articles: 315136 HOW TO: Complete a Semantic Database Analysis for the Active Directory http://support.microsoft.com/?id=315136 265706 DCDiag and NetDiag in Windows 2000 Facilitate Domain Join and DC Creation http://support.microsoft.com/?id=265706 258007
Error Message: Lsass.exe – System Error : Security Accounts Manager http://support.microsoft.com/?id=258007 265089 Event 1168: Windows 2000 DCs Unable to Boot into Active Directory http://support.microsoft.com/?id=265089 315131 HOW TO: Use Ntdsutil to Manage
Active Directory Files from the Command http://support.microsoft.com/?id=315131 BR – Frank

Edited bypbbergs [MSFT]ModeratorWednesday, April 24, 2013 3:56 PMI have broken the lines up to help make for readability

Frank: This procedure (with some variations required for my environment) worked
perfectly. Thank you very much.

To other readers: The procedure works, but it is a loaded gun. Be careful and methodical.

The specifics of my situation, which I offer as additional information, are:
Windows Server 2003 R2 Standard Edition SP2 with all updates.
One server, 20 clients; of course the server is the domain controller.

I suggest running the command prompt window at an elevated security level ("run as:", followed by unchecking the "restricted" box).
I also suggest changing directories to C:\WINNT\NTDS or C:\WINDOWS\NTDS, as appropriate.﻿

Variations:
The location of the NTDS folder is C:\WINDOWS\NTDS for an install that is not an upgrade from Server 2000.
Step 9 -- the parameters for ESENTUTL are different. For the integrity check I used "ESENTUTL /g NTDS.DIT /8" as the other parameters are not available.
Also in step 9 -- For the repair step that was required I used "ESENTUTL /p NTDS.DIT /8". There was a window warning of a possible data loss, which clicking OK cleared.
Step 11 -- NTDSUTIL FILES INTEGRITY works properly without change. However, the Semantic Database Analysis check cannot be run in a single command. I used "NTDSUTIL SEMANTIC DATABASE ANALYSIS" followed by "GO" at the next prompt. The database analysis does
not report a positive result, but if there is no warning the database passes the analysis. To be certain I ran the "GO FIX" step anyway, which gave identical output.

After this procedure the system started perfectly. I recommend this procedure as the answer to the problem.

-- E. R. Quinones

Edited byERQuinonesSunday, August 26, 2012 3:45 PMCorrected name of original poster.

Spending over 10 long painful days trying to help a firend out with their server build 9yrs ago (which they just enter daya and never do maintenance) the HDD corrupted with bad sectors and performing a chkdsk, scan, etc brought me to the lsass.exe Directory
Services Recovery stage.

I read several hundred links (not a server guy, mainly desktop) I came across this article and followed to the letter (although was getting an invalid switch for /v, /x, /o (so left these out) and now backup operational.

This gives more time to understand my friends system and needs to replace the hardware (server only P4 1gb RAM, wunning W2k# Small Business Server) and bring them nto the new world.

Thanks again for publishing this article and bringing others back from terranova.

I just wanted to take a minute to thank Frank for his awesome walk-through. You saved me so much time, effort and pain it's almost indescribable. You are a credit to the IT world and I am beyond thankful that I came across your article.
After 2 days of fighting the corruption problem, with no end in sight, getting late and I was ill on top of it, I came upon this write-up and had it solved in only a few minutes. I seriously cannot thank you enough for taking the time to put this up.

Microsoft should take a lesson from you in how to write How To's. I don't need a thousand options and explanations for every parameter, I need a resolution and you, sir, know how to write them.

This didn't work for me because got Jet_errBadPageLink or Jet_errReadVerifyFailure(bad checksum/page checksum mismatch) when trying to repair database. Then I noticed in integrity check logs that there is warning "Repair
is not allowed on this database due to its specific content" so it means some errors are not fixed for ntds.dit database.

What did the trick was to use older eseutil or edbtool from Exchange 2003 installation. It fixed the wrong pages and Microsoft Active Directory database problems.