NTDS ISAM 474 in event log - The database page read from the file "d:\directory\NTDS\ntds.dit at offset XYZ failed verification

paulfoel
paulfoel used Ask the Experts™
on
Multiple 2003 servers with multiple DCs. This is occuring on one of them.

At the moment, server is up and running fine.

Best way to fix? Force AD replication to this server?

If I could fix with server reboot that would be best solution.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
MaheshArchitect
Distinguished Expert 2018
Commented:
Since issue exists with single DC, demotion and promotion will resolve your issue

Author

Commented:
Any issues with having to clean up metadata?
Architect
Distinguished Expert 2018
Commented:
If affected DC holding FSMO, then 1st transfer it to another DC

Then just point it to some else working DC in tcp/ip properties as preferred DNS and reboot once

After reboot just try with dcpromo, if its failed, then run dcpromo /forceremoval switch

After that you must do metadata cleanup for failed DC as forceremoval switch will remove AD from affected DC only and it will not clear its entry from other domain controllers
Check below article
http://support.microsoft.com/kb/216498

Mahesh

Author

Commented:
Thanks, so only need to do metadata cleanup you have to do /forceremoval? i.e. no need if dcpromo works without this option?
MaheshArchitect
Distinguished Expert 2018

Commented:
Yes, if dcpromo works smoothly, it will cleanup AD for removed server automatically and no need to run Metadata Cleanup

However if that fails, then you must use dcprpmo /forceremoval switch and then metadata cleanup is also mandatory

Mahesh

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial