Please complete the form below with your resume attached.

Your Name (required)                                             Email Address (required):                                        Phone Number (required):

                      

Why should we consider you for the position? How would you be an asset to our company?

 
 
 
 


Your Picture  


Note: Only .doc .docx and .pdf files smaller than 5MB

Upload CV / Resume  

Upload Cover Letter  

How to fix ERROR 0XC00002E2 on Windows Server 2012

Windows Server running on a virtualized domain controller might face an issue like this. It just would not boot up properly and display an error message that would say “Your PC ran into a problem and needs to restart. We’re just collecting some error info, and then we’ll restart for you. (0% complete). If you’d like to know more, you can search online later for this error: 0xc00002e2).”

Active directory contains very sensitive and valuable data that can can get damaged. This sometimes occurs if you are implemented a Certificate Authority, deploying a Lync server, or data corruption in DC (Domain Controller) Databases, or just plain old power interruption.

The host/base server running the Hyper-V server would boot up smoothly and you can still see all the virtual machines. However, the Domain Controller server or virtual machine would show it is rebooting in a loop with this error:

Your PC ran into a problem and needs to restart. We’re just collecting some error info, and then we’ll restart for you. (0% complete). If you’d like to know more, you can search online later for this error: 0xc00002e2)

In cases of power failure, it will really cause an issue because the DC has a specific cache memory handled by the OS not RAID controller. The said cache will get corrupted and thus would result to the 0xc00002e2 error.

Before you do anything else, make sure to do a backup to avoid further data loss.

Here is how you could recover from this issue.

Restart the machine/virtual machine/instance and press F8 until you reach the boot menu.

Boot into Directory Services Repair Mode (DSRM).

Login with a local administrator account. This is important since Active Directory service is not running during this time.

Open a Command Prompt (Win-R, CMD, Enter)
Navigate to C:\Windows\NTDS folder
Create a backup copy of everything in this location.
Type NTDSUTIL and press Enter.
Type “activate instance ntds” and press Enter.
Type “Files” and press Enter.
Type “Info” and press Enter.
Navigate to logs Location and delete (or rename) the *.log.
reboot normally.

Boot into Directory Services Repair Mode for second time
A defrag/compact is necessary.
Open a Command Prompt (Win-R, CMD, Enter).
Type NTDSUTIL and press Enter.
Type “activate instance ntds” and press Enter.
Type “Files” and press Enter.
Type “Info” and press Enter.
Verify the folder is actually C:\Windows\NTDS.
Type “Compact to ” and press Enter. I created C:\Windows\NTDS\Temp and used that.
Copy the new file Ntds.dit in the temp folder over the old one in NTDS, and delete all the *.log files.
Reboot normally.

Written by

No Comments Yet.

Leave a Reply

Message

Facebook

YouTube

LinkedId

LiveZilla Live Chat Software
LiveZilla Live Chat Software