Results 1 to 5 of 5

Thread: Windows\NTDS\edb.log corruption.

  1. #1
    Join Date
    Aug 2006

    Windows\NTDS\edb.log corruption.

    I have 3 DCs and 2 of them experience Windows\NTDS\edb.log corruption, this week and I am afraid that my last DC will be next. The first DC is not booting in normal mode so I ended up forcing a demotion and then bringing it back intp normal mode, so I ended up forcing a demotion and then bringing it back into the domain. It looks to come back fine and everything ran ok for the past week. But today, my 2nd DC started to have same errors, that was, Directory Services events 465, etc. The first DC that failed is Windows 2003 64bit and todays DC is Windows 2003 32 bit and it runs as a virtual machine under the first failing DC. The one DC that has not failed is Windows 2003 32bit on a real machine with no virtual's under it. Can anyone tell me what should I do now? Thanks.

  2. #2
    Join Date
    Oct 2005

    Re: Windows\NTDS\edb.log corruption.

    You can try to run dcdiag and netdiaf from support tools. After that check the replication errors, disk space or errors, memory, etc. If everything is working fine, then you will need to run an offline defrag of AD Database.

  3. #3
    Join Date
    Jan 2006

    Re: Windows\NTDS\edb.log corruption.

    Did you try to run a Semantic Database analysis yet? Check the article made on, how to complete a semantic database analysis for the Active Directory database by using Ntdsutil.exe from here -

  4. #4
    Join Date
    Feb 2006
    You need to check the root cause of this issue. Are you using professional hardware with ECC memory? Is you disk controller cache use ECC memory? Have you checked the disk controller has a battery backup, or is write cachning disabled? Incase you are not using ECC memory, then try to run memtest86 on the machine to find out if your memory is faulty. The disk controller could also be at fault, so check it as well.

  5. #5
    Join Date
    Jul 2007
    I tried everything out there to fix the AD errors, but nothing had worked. Bad thing is, tape backups had failed & was just installing new tape drive when AD became corrupted.

    I ran the following commands:
    esentutl /g “c:\winnt\ntds\ntds.dit” /!10240 /8 /v /x /o
    might fail, but do next step anyway
    esentutl /p “c:\winnt\ntds\ntds.dit” /!10240 /8 /v /x /o
    Deleted log files
    Rebooted server normally

    This fixed the problem.

Similar Threads

  1. NTDS ISAM: Database Corruption
    By BoanHed in forum Small Business Server
    Replies: 3
    Last Post: 03-01-2014, 10:41 AM
  2. Replies: 3
    Last Post: 29-01-2011, 06:41 PM
  3. How To Fix WMI Corruption under windows
    By Saaarc in forum Windows Software
    Replies: 3
    Last Post: 02-07-2009, 12:56 PM
  4. NTDS ISAM 467 database corruption
    By low40p in forum Active Directory
    Replies: 8
    Last Post: 03-07-2007, 12:52 PM
  5. NTDS ISAM / NTDS Replication major issues
    By MikeY007 in forum Active Directory
    Replies: 3
    Last Post: 18-07-2005, 03:20 AM

Tags for this Thread


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
Page generated in 1,686,419,433.21460 seconds with 17 queries