Tag Archives: Microsoft

Wait on the Database Engine recovery handle failed. Check the SQL server error log for potential causes

When installing Microsoft SQL Server 2014, you might come across a situation where the setup fails towards the end of the installation with the following error,

“Wait on the Database Engine recovery handle failed. Check the SQL server error log for potential causes.”

Error when installing SQL

If you ignore the error and continue with the installation the following will be displayed.complete with failures

After scouring the web for a fix I was able to resolve the problem with the below steps. Some answers asked me to both uninstall SQL Server and delete a specific set of SQL registry entries, I did not delete any registry entries. I fixed the error by only uninstalling SQL 2014 using add/remove programs.

After SQL 2014 was uninstalled, I restarted the server then started the installation by right clicking on “setup.exe” and selecting “start as administrator”. Proceed with the installation normally until you get to the Server Configuration section,

Before change

On the SQL Server Database Engine service, click the drop down option to select a new user.

click advance

Click “Advanced”

click find now and select network service

Click “Find Now” then browse to “Network Service”, select this user and click OK.

After change

It should now look like the above, now continue with the installation.
You should no longer have the issue.

Finished Succesfully

Recover your virtual domain controller inside a CSV if Hyper-V failover cluster fails

Workaround to take back DC VM from CSV.

1. At this moment, your cluster is offline and failed due to its inability to connect to a Domain Controller.

2. Go to Cluster Shared Volume, select the Cluster volume which contained the VHD.

3.Offline the resources, right click and select Remove from Cluster Shared Volumes.

4. Once remove, go to Storage and you will see the disk located in Available Storage. Assign a Drive Letter and copy the VHD out.


This is the simple trick to recover the DC VM which is inside the CSV. Hopefully, you can now create the a new VM and point towards the copied VHD then start the Domain Controller. Once the DC is up, then you will be able to start the Hyper-V Failover Cluster.

Just to remind again, you should have at least 1 DC not in CSV or run in the physical server.

Source: http://www.ms4u.info/2011/08/recover-domain-controller-virtual.html