Geforce
asked on
Restore AD (Domain Controller)-VM
Hi,
Our HV HDD was crush. We manage to restore AD Domain controller (Windows server 2012R) but when i boot the VM. I received this blue screen. I tried all the available solutions.
This is only one domain controller and we have to restore it.
Boot VM via 2012r2 ISO and perform below commands but still receive the same blue screen error.
SFC/scannow
bootrec / fixmbr
bootrec / fixboot
bootrec / rebuildbcd
Please suggest me to resolve this issue.
2019-04-23_19-48-52.jpg
Our HV HDD was crush. We manage to restore AD Domain controller (Windows server 2012R) but when i boot the VM. I received this blue screen. I tried all the available solutions.
This is only one domain controller and we have to restore it.
Boot VM via 2012r2 ISO and perform below commands but still receive the same blue screen error.
SFC/scannow
bootrec / fixmbr
bootrec / fixboot
bootrec / rebuildbcd
Please suggest me to resolve this issue.
2019-04-23_19-48-52.jpg
Is this the only domain controller in the environment?
ASKER
Yes Coolie.
When it starts booting up, start pressing F8 before the OS tries to load. When you get to the black screen, go into "Directory Services Restore Mode" you'll have to use the local admin account password.
If you get to that point, you'll want to follow this article:
https://support.hostway.com/hc/en-us/articles/360001126259-How-to-fix-Error-0xc00002e2-after-rebooting-Windows-Domain-Controller
If you get to that point, you'll want to follow this article:
https://support.hostway.com/hc/en-us/articles/360001126259-How-to-fix-Error-0xc00002e2-after-rebooting-Windows-Domain-Controller
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi Coolie,
I perform the steps as given in the article but I didn't receive database error. Please review the attach image.
so it seems like that my Active Directory database is not corrupted so what will i do at this stage.
AD.jpg
I perform the steps as given in the article but I didn't receive database error. Please review the attach image.
so it seems like that my Active Directory database is not corrupted so what will i do at this stage.
AD.jpg
So you were able to get in the server?
Try F8 again, and select "Last Known Good Configuration" and see if it works.
Try F8 again, and select "Last Known Good Configuration" and see if it works.
ASKER
Hi,
I just tried but same blue screen.
I just tried but same blue screen.
Try this:
https://www.dell.com/support/article/ca/en/cabsdt1/sln290986/recovering-the-active-directory-database-in-windows-server-2012-r2?lang=en
Next step would be creating a DC
https://www.dell.com/support/article/ca/en/cabsdt1/sln290986/recovering-the-active-directory-database-in-windows-server-2012-r2?lang=en
Next step would be creating a DC
Please review the following link, take a few very summarized steps of what you should do:
https://www.tbngconsulting.com/blog/bid/385396/9-steps-to-correcting-a-Windows-Server-2012-0xc00002e2-Error
https://www.tbngconsulting.com/blog/bid/385396/9-steps-to-correcting-a-Windows-Server-2012-0xc00002e2-Error
ASKER
Hi RAFA,
i already did these steps but still no luck :(
same blue screen. also when i run the this command (Type "Compact to " and press Enter. I created C:\Windows\NTDS\Temp and used that).
i received the below error:
-------------------------- ---------- ---------- ---------- ---------- ---------- ---------- ---------- ---
Fortunately, I found a better/simpler solution that usually works, or at least did for me.
- Boot into Directory Services Repair Mode (Troubleshoot / Startup Settings / Restart / Directory Services Repair Mode). It may do some repairs and reboot, requiring you to do this a second time.
- Login with a local admin account, since AD is not available.
- Delete (or rename) C:\Windows\NTDS\*.log.
And reboot normally.
However, you may also want to 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 top of the old one in NTDS, and delete all the *.log files.
Reboot normally.
i already did these steps but still no luck :(
same blue screen. also when i run the this command (Type "Compact to " and press Enter. I created C:\Windows\NTDS\Temp and used that).
i received the below error:
--------------------------
Fortunately, I found a better/simpler solution that usually works, or at least did for me.
- Boot into Directory Services Repair Mode (Troubleshoot / Startup Settings / Restart / Directory Services Repair Mode). It may do some repairs and reboot, requiring you to do this a second time.
- Login with a local admin account, since AD is not available.
- Delete (or rename) C:\Windows\NTDS\*.log.
And reboot normally.
However, you may also want to 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 top of the old one in NTDS, and delete all the *.log files.
Reboot normally.
I'd build a new DC. It takes only a few hours and you will be sure that the system is ok.
To be honest I'd be rebuilding it, I had a similar problem last year. though mine had the stop error mentioned above.
Regards,
Pete
Regards,
Pete
Here is an article giving detailed workaround on this error.
fixing a corrupt domain controller stop code 0x00002e2
https://ithinkvirtual.com/2017/11/12/fixing-a-corrupt-domain-controller-stop-code-0x00002e2/
fixing a corrupt domain controller stop code 0x00002e2
https://ithinkvirtual.com/2017/11/12/fixing-a-corrupt-domain-controller-stop-code-0x00002e2/
ASKER
Hi Rafa,
Thanks for the link but i already try this method but i was stuck at setp "compat to c:\temp" and receive an error that i posted in my above post.
Long story short. I rebuild the domain controller again. I have to rebuild rest of the three servers (SQL, RDSH and applications).
If i was recover the domain controller so I don't have to rebuild rest of the servers.
I am closing this ticket and I appreciate and Thanks to all users who help me to resolve the issue and suggest me alternate solution.
Thanks for the link but i already try this method but i was stuck at setp "compat to c:\temp" and receive an error that i posted in my above post.
Long story short. I rebuild the domain controller again. I have to rebuild rest of the three servers (SQL, RDSH and applications).
If i was recover the domain controller so I don't have to rebuild rest of the servers.
I am closing this ticket and I appreciate and Thanks to all users who help me to resolve the issue and suggest me alternate solution.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.