Re: NTDS ISAM DataBase Corruption

Hi Jorge,

I don't have any error messages when I restart the server.

Solution 1 : I don't have a systate backup. However, I did a full backup
using symantec livestate recovery. Can I restore the files from
c:\windows\ntds\*.* ? I have no success to use esentult /r and restart the
server using a backup ntds.dit.

Solution 2 : Only DC in domain.

Solution 3 : I can ndtsutil -> files -> recovery : no problem - 0x00 exit
code.
However, I get an error message database corruption using "esentutl /r
ntds.dit".

Question: Can I delete it and re-install or rebuilt a new DC (same name) and
add back all the users and computers?

Thanks,
Alfred


"Jorge Silva" wrote:

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: How do I restore from mdf and ldf files?
    ... Tasks -> Backup Database ... Tasks -> Restore Database ... Windows 2003 Server with Latest Service Pack ... Pre-requisites for Sharepoint Backup and Restore: ...
    (microsoft.public.sharepoint.portalserver)
  • RE: ESENT Logging
    ... SBS server 2003 has a backup job that will ... 145881 How to Use Jetpack.exe to Compact a WINS or DHCP Database ... newsgroups so that they can be resolved in an efficient and timely manner. ...
    (microsoft.public.windows.server.sbs)
  • RE: ESENT Logging
    ... SBS server 2003 has a backup job that will ... 145881 How to Use Jetpack.exe to Compact a WINS or DHCP Database ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • RE: Backups have Shadow Copy Problems
    ... and restarted the server. ... suggested and changed the recovery model to simple on the one database called ... I understand the issue to be: the backup task failed ... You back up data from a volume that contains a Microsoft SQL Server ...
    (microsoft.public.windows.server.sbs)
  • Re: Copying a database between servers
    ... In 2000 you can backup to an UNC path ... or a local drive and the same goes for the restore. ... backup the database and then restore it on the new server. ... >>> one SQL Server 7.0 database with 'select' access to another SQL ...
    (microsoft.public.sqlserver.tools)