The Active Directory database is corrupt

[Hema S]

NTDS (264) Synchronous read page checksum error -1018
((1:244411 1:244411) (0-51227717) (0-69402268)) occurred.
Please restore the databases from a previous backup.

Am getting this error in one of the domain controllers ?
any resolution ?

 

[ptwilliams]

Drop the DC into Directory Services Restore mode and restore last week's
backup of the system state. Bring the DC back on-line and allow for it to
replicate with the other DCs.


--

Paul Williams
_________________________________________
http://www.msresource.net

Join us in our new forums!
http://forums.msresource.net
_________________________________________
NTDS (264) Synchronous read page checksum error -1018
((1:244411 1:244411) (0-51227717) (0-69402268)) occurred.
Please restore the databases from a previous backup.

Am getting this error in one of the domain controllers ?
any resolution ?

 

[Hema]

Non authoritative restore right ? Could you please give
any other information regarding this -1018 database
errors? What is the impact of restoring the database in
the domain containing 48 DCs. And if the error is
occuring for longtime.. the backup is happening daily.
But If I restore the system state also, what is the
guarantee that the backed up database is error free ?
simply, i'm not sure that the backup is good to be
restored. any alternate solution ?

Will it affect the other Domain controllers in the domain
also ?

TIA..
Hema.S

 

[ptwilliams]

Non authoritative restore right ?
- Correct.

Will it affect other DCs?
- Quite possibly; if the corruption is in a record then the corrupt
record will be replicated out to all DCs. If it's a file system issue, then
probably not.

If you are unsure of your backups, you have a couple of choices:

1. use an old backup, e.g. five-six weeks old (just don't go over the 60
day tombstone period)
2. demote the DC and repromote later
3. delete the DC, perform a metadata cleanup and rebuild the DC.


I've not come across this exact error, so I can't be anything other than
general...perhaps somebody else has?

--

Paul Williams
_________________________________________
http://www.msresource.net

Join us in our new forums!
http://forums.msresource.net
_________________________________________
Non authoritative restore right ? Could you please give
any other information regarding this -1018 database
errors? What is the impact of restoring the database in
the domain containing 48 DCs. And if the error is
occuring for longtime.. the backup is happening daily.
But If I restore the system state also, what is the
guarantee that the backed up database is error free ?
simply, i'm not sure that the backup is good to be
restored. any alternate solution ?

Will it affect the other Domain controllers in the domain
also ?

TIA..
Hema.S

 

[Guido Grillenmeier [MVP]]

yep, I ran into this error before - if this DC isn't on a really slow link
in a Branch Office, I'd definitely recommend to forcefully demote the DC
(won't even try to replicate out), do a meta-data cleanup in AD and then
re-promote to a DC.

the error can occur for multiple reasons - could be HW related, could also
just be a problem in the database file that AD can't fix itself. Good news
is, that AD is smart enough not to continue any replication with partner DCs
when a DC is recognized to have a currupt DB (which this error indicates).
Has only happened on two DCs I know of in various installations in the last
4 years, so that's not too bad.

you didn't mention the OS - but you can forcefully demote DCs by default in
2003 - for 2000 DCs you'll require SP4. Then just run "dcpromo
/forceremoval".

/Guido

 

[Hema S]

It is one of the branch office and the link is 1 MB.

There is also a dependent Exchange server. thats y am
thinking about the demotion and promotion. Anyways,
thanks for the suggestions given and if you come to know
any other points regarding this, pls let me know..

Thankx..
hema.