Checksum Error On A Database Page Ntds.dit
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Repair NTDS.DIT that have bad checksum Want to Advertise Here? Solved Repair NTDS.DIT that have bad checksum Posted on 2013-02-26 SBS Windows Server 2008 Active Directory 1 Verified Solution 10 Comments 2,846 Views Last Modified: 2013-09-25 Hi, yes i know, i should have done backup of AD to, but i didnt :-( My ntds.dit file is corrupted and i dont have backup. Its a SBS 2011 premium server I can start in directory recover mode I can't start in safe mode or normal mode :-( First time i tried to run ntdsutil and the file command it failed, i couldnt run it. I had to run the go fix command and after that i can run the file command. But i cant fix the bad checksum so i cant start it in normal mode. Is there any way to repair the ntds.dit file in any way, some program or other way to do it? Is it possible to see what the checksum should be and correct it manualy? If its not possible to fix the ntds.dit file, is it possible to start AD on scratch and connect it to the exchange server? 0 Question by:per-w Facebook Twitter LinkedIn Google LVL 5 Best Solution byvin_shooter I think then its not possible to revert the situation. Have to demote the DC and have to start right from scratch.., I doubt. Go to Solution 10 Comments LVL 9 Overall: Level 9 Active Directory 9 Windows Server 2008 6 SBS 1 Message Expert Comment by:Zenvenky2013-02-26 Yes, you can repair NTDS.dit. As this is SBS server, I'm sure you do not have any other DC in the domain. Now that you are in DSRM mode, check the NTDS paths in registry and default folder where it is suppose to be. Use the following link though it doesn't mention SBS, you can use this KB. AD Repair Note: Before you start using NTDSUTIL, take backup of NTDS folder, place it some other location and rename that folder and keep it as backup. 0 LVL 23 Overall: Level 23 Windows Server 2008 12 Active Directory 8 SBS 2 Message Expert Comment by:Nagendra Pratap Singh2013-02-26 BTW additional DCs are suppor
360 games PC games Windows games Windows phone games Entertainment All Entertainment Movies & TV Music Business & Education Business Students & educators Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet https://www.experts-exchange.com/questions/28045541/Repair-NTDS-DIT-that-have-bad-checksum.html Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Lumia All https://support.microsoft.com/en-us/kb/2645996 Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States) Terms of use Privacy & cookies Trademarks © 2016 Microsoft
may have a replication issue so I started looking into it and to give a brief background of the environment.. we have almost 48 Windows 2008 R2 domain controllers globally, so we needed to find out where and http://asknicks.blogspot.com/2013/05/active-directory-database-corruption.html how the replication is broken.. Now, i needed a tool that can go and check all domain controllers to summarize the replication inbound and outbound replication status.. so Ipulled up "REPADMIN"to find out the inbound and outbound replication https://www.vmadmin.co.uk/microsoft/43-winserver2008/156-svr08addsntdscompact status of my domain.. I ran "repadmin /replsummary" and i started counting dots on the command screen which represent the progress. So after few minutes of processing, I had a summary report of the servers and unfortunately checksum error i found one of our DCs hasn't replicated in last 16 hrs (quite worrying, huh!! ). But just next to it had a reason of the failure which said "The replication operation encountered a database error" Oopps, this is getting interesting now.. So, i logged in to the Domain Controller reporting database issue to investigate further and fix it. The directory service Event log showed me Database index corruption errors.. hmm interesting.. Log Name: Directory checksum error on Service Source: NTDS ISAM Date: 10.5.2013 10:03:21 Event ID: 467 Task Category: Database Corruption Level: Error Keywords: Classic User: N/A Computer: Test.domain.local Description: NTDS (492) NTDSA: Database C:\Windows\NTDS\ntds.dit: Index DRA_USN_index of table datatable is corrupted (0). Corrupt database? This willdefinitelyskip a heartbeat of most of the AD administrators.. :( so we ran little PowerShell script to quickly check all domain controllers for Event ID 467 and make sure we are not spreading the corruption over to other servers. Thankfully no other DC isexperiencingthe corruption.. Generally, the corruption can be caused by numerous reasons but i had few in my mind that requires a check there and then... Hardware Outdated Drivers/firmware especially disk controller & controller cache. Sudden power loss Lingering objects Time to fix it then.. most of the time the Domain Administrators prefer to go ahead and rebuild the domain controller and sync everything back, but the real concern is how many changes does this box hold and what would be the impact if we go ahead with demote andre promoteof the server.. hmm, so in our case we decided to go a bitfurtherand look for clues to fix the issue instead of going for a demotion.... So, the question was how can we find more details about the error.. and like always the answer was e
depending on amount of changes to the database. Stop "Active Directory Domain Services" (also stops the services below) -File Replication Service -Kerberos Key Distribution Center -Intersite Messaging -DNS Server ntdsutilntdsutil: activate instance ntdsActive instance set to "ntds".ntdsutil: filesService "NTDS" is running. Stop the service before binding to this Active Directory database.ntdsutil: filesfile maintenance: compact to c:\tempInitiating DEFRAGMENTATION mode...Source Database: C:\Windows\NTDS\ntds.ditTarget Database: c:\temp\ntds.ditDefragmentation Status (% complete)0 10 20 30 40 50 60 70 80 90 100|----|----|----|----|----|----|----|----|----|----|...................................................It is recommended that you immediately perform a full backupof this database. If you restore a backup made before thedefragmentation, the database will be rolled back to the stateit was in at the time of that backup.Compaction is successful. You need to:copy "c:\temp\ntds.dit" "C:\Windows\NTDS\ntds.dit"and delete the old log files:del C:\Windows\NTDS\*.logquitquit copy "c:\temp\ntds.dit" "C:\Windows\NTDS\ntds.dit"del C:\Windows\NTDS\*.log ntdsutilntdsutil: activate instance ntdsActive instance set to "ntds".ntdsutil: filesService "NTDS" is running. Stop the service before binding to this Active Directory database.ntdsutil: filesfile maintenance: help? - Show this help informationCheckpoint - Dump Jet checkpoint fileChecksum - Perform Jet physical integrity checkCompact to %s - Compact DB to specified directoryDump page %d - Dump Jet db %d page numberHeader - Dump the Jet database headerHelp - Show this help informationInfo - Return information about DS filesIntegrity - Perform Jet logical integrity checkLogfile %s - Dump Jet log file %s. %s could be absolutepath or just the log file name in log dir.Metadata - Dump Jet db metadataMove DB to %s - Move DB to specified directoryMove logs to %s - Move log files to specified directoryQuit - Return to the prior menuRecover - Perform soft database recoverySet backup exclusion key - Set backup exclusion key for the AD DS/LDS.Set default folder security - Reset security on NTDS folders to defaultvaluesSet path backup %s - Set online backup directory pathSet path DB %s - Set DB file pathSet path logs %s - Set logging directory pathSet path working dir %s - Set AD DS/LDS working directory pat