Server 2012 CRASH – ERROR 0XC00002E2
нормально грузится в режиме восстановления . файл базы сначало вообще не давал ничего с собой делать через ntdsutil. ругался что не может запустить JET .
журналы переименовывал (как одно из средств восстановления, создаются по новой.)
после Esentutl с разными ключами , база начала хоть как то дефрагментироваться и проверяться. но есть ошибка:
ntdsutil: Activate Instance NTDS
Активный экземпляр — «NTDS».
ntdsutil: files
file maintenance: Compact to c:\temp\tempNTDS
Запуск режима ДЕФРАГМЕНТАЦИИ.
Исходная база данных: C:\Windows\NTDS\ntds.dit
Конечная база данных: c:\temp\tempNTDS\ntds.dit
Defragmentation Status (% complete)
0 10 20 30 40 50 60 70 80 90 100
|—-|—-|—-|—-|—-|—-|—-|—-|—-|—-|
. Операция прекращена с
ошибкой -1605( JET_errKeyDuplicate, Illegal duplicate key ).
______________________________
проверял все доступы к папкам журнала и базы . все нормально.
recover проходит без ошибок. а вот
file maintenance: integrity
Выполнение проверки целостности для базы данных: C:\Windows\NTDS\ntds.dit.
Checking database integrity.
Scanning Status (% complete)
Integrity check completed. Database is CORRUPTED!
Операция прекращена с ошибкой -1206( JET_errDatabaseCorrupted, Non database file
or corrupted db ).
— в домене трудится второй контроллер — с него как то можно взять файл базы или синхронизировать ?
— можно сломанный сервер освободить от роли AD загрузиться в нормальном режиме и опять развернуть службу AD — домен его как » страый «второй КД подхватит?
Ответы
ВОПРОС — МОЖНО ЕГО СЕЙЧАС В СЕТЬ ВОЗВРАЩАТЬ чтоб он реплицировался и встал в строй полноценно??
проверки есть какие нибудь ??
Лучше не возвращать, а принудительно понизить (Uninstall-ADDSDomainController -ForceRemoval в Powershell), вычистить на другом КД информацию о нём из Active Directory (к примеру — удалить подобъект NTDS Settings объекта этого сервера в AD Sites and services) и, если он ещё нужен как КД — повысить заново.
Дело в том, что после выполнения esentutl /p потеря данных при таком исправлении может привести к рассогласованию БД Active Directory с копией на другом КД, которое практически невозможно выявить. А также — к другим трудновыявляемым ошибкам.
Поэтому Microsoft советует (есть статья 258062 в MS KB) прибегать к esentutl /p только как крайней мере — для восстановления единственного КД в домене при отсутствии резервной копии — и даже рекомендует после этого по возможности быстрее произвести миграцию учётных записей пользователей и компьютеров в неповреждённый домен.
Fixing A Corrupt Domain Controller – Stop Code 0x00002e2
Yesterday morning I discovered that my Synology NAS had an unexpected shutdown in the middle of the night while my homelab VMs/workloads were still running. This caused both of my Domain Controllers databases to become corrupt resulting in being unable to boot those machines. When attempting to boot them, they would get stuck in a BSOD boot-loop and would display a Stop Error Code of 0x00002e2.
After some research I was able to figure out how to recover my VMs and get them to boot up again. This had happened to me once before sometime earlier this year and luckily I remembered that I had taken some notes on how to fix it so I figured this time I would put together a formal “How To:” guide to have it documented for myself and hopefully to help others facing this issue as well. So without further adieu…let’s get to it!
To start, you will need to power-on the machine and then keep pressing the F8 key to bring up the “Advanced Boot Options” boot menu. Navigate down to Directory Services Repair Mode enter press Enter to boot you into Safe Mode.
When you reach the login screen, log in with the Local Administrator account since Active Directory Domain Services are obviously unavailable.
Once at the Desktop, open an elevated Command Prompt window.
As a best practice, I feel it is always wise and important to make a backup of the files before doing any modifications. Since we will be backing up the NTDS directory, create a directory at your preferred location to store the backup files. I chose to make a backup folder on the root of “C:\” and a sub-directory with the name/date of the directory I am backing up.
Then copy everything from the “C:\Windows\NTDS” directory to this new location using xcopy.
Once done, let’s rename any .log file extensions in the NTDS directory to .log.old
Now, this is where we get to the good stuff!
First, run the following command to repair the database.
This will display the following warning message, click “OK“
Let it do its thing and you will see the following once complete.
Now we need to use the NTDS Utility (ntdsutil.exe) to activate the NTDS instance and compact the DB to a new file which will then be used to overwrite the original. I will be compacting it to a new TEMP directory within the NTDS directory. The command will automatically create the new directory if it’s not already present. Enter the following commands.
If successful, you will be presented with instructions to copy the newly compacted file to the NTDS directory, overwriting the original, and also to delete any .log files in the NTDS directory. Before we can do that we need to exit out of the ntdsutil. Type quit twice to exit.
Let’s follow those instructions and also delete the *.log.old files we renamed earlier.
Ensure you are still in the NTDS directory before entering the following delete commands.
The hard part is now over! Let’s go ahead and reboot the machine normally.
If all goes well and as expected, your machine will boot successfully and you can log in again with an Active Directory Domain Admin account.
Awesome! Well, I hope you’ve found this guide useful. Please feel free to share this and provide me some feedback/comments below. Thanks for reading!
How to fix Error 0xc00002e2 after rebooting Windows Domain Controller
This error is an indication that the Active Directory database (NTDS.DIT) is corrupt.
Error code 0xc00002e2 is only seen on a system with Active Directory.
Remediation:
Reboot the server into Directory Services Restore Mode by pressing F8 before the OS begins loading. You will be required to use the local Administrator account password.
In Directory Services Restore Mode, you can check if there is a problem with the database by running the following commands:
ntdsutil.exe
activate instance ntds
files
If there is a problem with the Active Directory database NTDS.DIT, you will see an error like the following:
Could not initialize the Jet engine: Jet Error -501. Failed to open DIT for AD DS/LDS instance NTDS. Error -2147418113
To resolve this issue, rename all of the .log files located in C:\Windows\NTDS\ to .log.old, so the logs can be recreated after reboot.
This should fixed the database after the server is rebooted once more. If you continue to get the error, you can access again Directory Services Restore Mode and run the following command:
esentutl /p «c:\windows\ntds\ntds.dit»
Reboot the server and the issue should be solved.
Created: October 02, 2018 22:30
Last Updated: October 08, 2020 05:41
Related articles
Have More Questions?
Contact our support instantly via Live Chat