Re: NTDS ISAM DataBase Corruption

Hi

Some possible solutions:

*Solution1:

Perform restore operation to resolve the issue with your lastest Systate
BACKUPS.



*Solution 2:
In case this is not the only DC in the domain, you can simply rebuild it.
At the same time, you will need to perform the steps below before
re-promoting the server:

1. Seize FSMO roles to the existing DC in the domain. For the detailed
steps, you can refer to the following Microsoft Knowledge Base article:

Using Ntdsutil.exe to transfer or seize FSMO roles to a domain controller
http://support.microsoft.com/?id=255504

2. Remove remnant entries of the corrupted DC from AD database.

How to remove data in Active Directory after an unsuccessful domain
controller demotion
http://support.microsoft.com/?id=216498

3. Then, you can re-promote the server

*Solution 3:

If this is the only DC, you can use ntdsutil.exe to repair AD database
ntds.dit. However it might not completely resolve the issue. In some
situation, certain configurations will be lost.

"Directory Services cannot start" error message when you start your
Windows-based or SBS-based domain controller
http://support.microsoft.com/?id=258062

How to complete a semantic database analysis for the Active Directory
database by using Ntdsutil.exe
http://support.microsoft.com/default.aspx?scid=kb;en-us;315136

Additional Information
Exchange Server 2003 Disaster Recovery Operations Guide

http://www.microsoft.com/technet/prodtechnol/exchange/2003/library/disrecopgde.mspx

Disaster Recovery Tips and Tricks

http://www.petri.co.il/disaster_recovery.htm


--
I hope that the information above helps you

Good Luck
Jorge Silva
MCSA
Systems Administrator

"Alfred" <Alfred@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F6D77881-7CE8-4732-83F8-81D9AED7ECE0@xxxxxxxxxxxxxxxx
Source : NTDS ISAM
Category : DataBase Corruption
Event ID : 447

Description : NTDS (872) NTDSA: A bad page link (error-327) has been
detected in a B-Tree (ObjectID: 29 PgnoRoot: 47) of Database
C:\windows\ntds\ntds.dit (761 => 762,293)

This message from event log that I try to reset an user password -
internal
error.


.

Relevant Pages

  • Re: NTDS ISAM DataBase Corruption
    ... Did you tried the recover the corrupted Active Directory process that a gave ... This is brand new IBM Server. ... using symantec livestate recovery. ... Active Directory database is unavailable because it is damaged, ...
    (microsoft.public.windows.server.active_directory)
  • RE: AD Repair Possible? Event ID 474s
    ... You receive the Active Directory database ntds.dit checksum mismatch error ... Exchange server) seems to work correctly without any problem. ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • Re: NTDS ISAM DataBase Corruption
    ... using symantec livestate recovery. ... You may try the following steps to recover the corrupted Active Directory, ... Active Directory database is unavailable because it is damaged, ... Open a command prompt and run NTDSUTIL to verify the paths for the ...
    (microsoft.public.windows.server.active_directory)
  • Re: NTDS ISAM DataBase Corruption
    ... This is brand new IBM Server. ... using symantec livestate recovery. ... You may try the following steps to recover the corrupted Active Directory, ... Active Directory database is unavailable because it is damaged, ...
    (microsoft.public.windows.server.active_directory)
  • Re: DCPromo and NTDS.DIT
    ... - You may try the following steps to recover the corrupted Active Directory, ... Active Directory database is unavailable because it is damaged, ... Open a command prompt and run NTDSUTIL to verify the paths for the ...
    (microsoft.public.windows.server.active_directory)
Loading