Windows Server 2012 CRASH – ERROR 0XC00002E2

If you are using windows server as a virtualized domain controller and you facing 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)

Since AD contains very sensitive and valuable data, especially if you implemented a certificate Authority or deploying Lync server, corruption in DC Database creates a dangerous problem which exactly what happened to me and cost me a lot of time to fix the issue without losing a data.

When a power disconnection happened, I checked my base server (Hyper-V server) and it started smoothly with no issue and all it`s contained VMs. except the Domain Controller which stuck in a rebooting 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)

I knew that the power failure will cause an issue to the DC, because the DC has a specific cache memory handled by the OS not RAID controller, the result will be a losing cache data which cause a data corruption .. If you face the same scenario you will be in very bad mode, but I'm here to help you;

Before doing anything backup your instance into safe location, you may lost or corrupt some data.

Now try the following
  • Restart the instance and press F8 until the boot menu appear
  • Boot into Directory Services Repair Mode (DSRM), this mode appear only if you have the DC to interact with NTDS database while it in offline, while booting It may do some repairs and reboot, requiring you to do this a second time.
  •  Login with a local administrator account, since AD service will not be running so the domain user will not be available.
  • Open a Command Prompt (Win-R, CMD, Enter)
  • Navigate to C:\Windows\NTDS
  • Backup 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 (this will shows you the logs location in case if you have more than one partition).
  •  Navigate to logs Location and delete (or rename) the *.log.
  • And reboot normally.
  • Boot into Directory Services Repair Mode for second time
  • Now you should defrag the database, while in DSRM;
  • 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.
Check this article it will help you as well http://support2.microsoft.com/?id=258062

For future protection use UPS and follow this article to protect your virtualized domain controller against AD database corruption



Share on Google Plus

About Mohamad A Sallal

A Highly Experienced and Accomplished Senior SharePoint Specialist, Architect, Designer and Developer, with Significant Experience Providing Full Life-Cycle Solutions and Project Management. Web Application Professional Experienced with Diverse Web Technologies. Knowledge of Current Microsoft Technologies, Leveraging the .NET Platform. Broad knowledge Technical Combined with Project Leadership Ability and Creative Problem Solving Skills in both Strategic and Tactical Areas. Specialties: Developing on the Microsoft .NET platform
    Blogger Comment
    Facebook Comment

28 comments:

  1. Wow.
    Thank you. Your a real life saver. This guide was perfect.

    ReplyDelete
    Replies
    1. Thanks PoTski anytime, i hope it helps you :)

      Delete
  2. Thanks! This is the only article I found that got me back up and running!

    ReplyDelete
  3. THX, I can go to sleep now

    ReplyDelete
  4. Thank you!!! Almost lost my main lab server

    ReplyDelete
  5. I am not able to login to server. how i should fix this issue

    ReplyDelete
  6. Is this specific to a single DC environment? I have a secondary DC with this error; are the steps the same or should I DC demote and then promote instead?

    ReplyDelete
  7. help I got to the compact step and I'm getting a "database inconsistent" error

    ReplyDelete
    Replies
    1. I have the same issue. any results?

      Delete
    2. found the answer
      http://blog.shiraj.com/2014/10/how-to-fix-c00002e2-directory-services-could-not-start-blue-screen/

      Delete
  8. This fixed my problem in a single-server environment. Windows storage server 2012 R2 Essentials. Exactly the same problem after updating the BIOS, but the fix worked great - Thank you!

    ReplyDelete
  9. Hey thanks for posting such an informative blog!!! i have solved http://blog.shiraj.com/2014/10/how-to-fix-c00002e2-directory-services-could-not-start-blue-screen/

    ReplyDelete
  10. wow it worked, thanks alot!

    ReplyDelete
  11. Thank you for your guide. Has helped me to recover my lab today.

    With Kind regards,

    John

    ReplyDelete
  12. Thank you,

    had this today on a Windows Server 2012R2 Essentials.
    The bad thing was that it needed 3 restarts even to enter Active Directory Recovery Servides as the last thing the DC did was installing updates.
    3 restarts in were necessary to even get to the logon prompt for the Recovery Mode.

    Keep patient in such a scenario!

    regards,

    Christian

    ReplyDelete
  13. Excellent post !. I learned lot of information. Thanks!

    php training in chennai

    ReplyDelete
  14. Hi...when i tried this.. i came with the following error , please help ...

    While i run the compact to c:\windows\ntds\ntds.dtl command, got following error

    Operation Terminated with error -327 Jet_errBadPageLink, Database corrupted

    ReplyDelete
  15. Thank you so much for this you save my beans, it worked like magic. :)

    ReplyDelete
  16. Lengend, thanks for making a nightmare a breeze to resolve :)

    ReplyDelete
  17. hank you so much for this you save my beans, it worked like magic.
    oracle apps training in chennai

    ReplyDelete
  18. Still smae issue pls help me out.....

    ReplyDelete
  19. Another homelab AD saved, Thanks!

    ReplyDelete