Export (0) Print
Expand All

If database integrity check fails, perform semantic database analysis with fixup

Updated: June 8, 2005

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

When you run semantic database analysis with the Go Fixup command instead of the Go command, errors are written into Dsdit.dmp.xx log files. A progress indicator reports the status of the check.

noteNote
To perform this procedure, the domain controller must be started in Directory Services Restore Mode.

Administrative Credentials

To perform this procedure, you must provide the Directory Services Restore Mode password for the local administrator account.

To perform semantic database analysis with fixup

  1. In Directory Services Restore Mode, open a Command Prompt.

  2. Type the following command and then press ENTER:

    ntdsutil:

  3. At the ntdsutil: prompt, type semantic database analysis and then press ENTER.

  4. At the semantic checker: prompt, type verbose on and then press ENTER.

  5. At the semantic checker: prompt, type go fixup and then press ENTER.

    • If errors are reported during the semantic database analysis Go Fixup phase, perform directory database recovery.

      CautionCaution
      Do not confuse the recover command with the repair command. Never use the repair command in Ntdsutil.exe. Forest-wide data loss can occur.

    • If semantic database analysis with fixup succeeds, type quit and then type quit again to close Ntdsutil.exe, and then restart the domain controller normally. If you are performing this procedure remotely over a Terminal Services connection, be sure that you have modified the Boot.ini file for normal restarting before you restart the domain controller.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft