One of my client was trying to deploy his product on their test servers. They found that the SQL Server installation was failing with below error. Let us learn about error Wait on the Database Engine recovery handle failed.
Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
As per my internet search this happens when SQL Setup is not able to start SQL Service during installation. I have looked into SQL Server ERRORLOG and found below the messages.
2016-12-23 16:15:04.84 spid14s Error: 17120, Severity: 16, State: 1.
2016-12-23 16:15:04.84 spid14s SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
This was interesting because my client was trying to install this on a Domain Controller. I checked setup logs again and found below in Summary.txt file.
SQLSVCACCOUNT: NT Service\MSSQLSERVER
Above parameter shows the account name which was selected during installation. Â Since this is a domain controller, I thought that there might be issues due to this.
WORKAROUND / SOLUTION
As the error says, first we need to uninstall the feature and then during setup, when we come to Server Configuration Screen, we need to change the account name of the Database Engine Service to
- NT AUTHORITY\NETWORK SERVICE.
- NT AUTHORITY\LOCAL SERVICE.
Both worked for my client and they could install SQL Express.
Reference: Pinal Dave (https://blog.sqlauthority.com)
39 Comments. Leave new
This error is popping up a lot in the various forums…I used the fix above on Windows 10 Home machine to install SQL 2014 and 16 Dev edition
There are various reasons and I just have found few and blogged them.
it’s ok thank you
Thanks Tomasz.
Thanks so much!
Thanks so much! Now server installed ;)
Thanks Sergey.
I ran into this same issue installing SQLexpress on a DC (Lab Environment). The recommended workaround resolved my issue. Thanks!
Your welcome!
Ok. I feel I might be a bit dense here, also I’m Swedish; You say this:”This was interesting because my client was trying to install this on a Domain Controller.”, then you say “Since this is a domain controller, I thought that there might be issues due to this.” and then you speak of uninstalling “the feature” – To which feature are you referring to? It can’t be Domain Controller, can it?
SQL Server on Domain Controller.
Thanks Pinal, nice solution. It works for me.
Thanks Pinal, It works for me :)
Thanks for your help!
Thanks Pinal – quick solution to a surprising problem – also installing SQL 2014 on a DC (dev environment)
Thanks man!! It solved my problem!
Perfect Solution! Worked fine for me and in our Environment. Many thanks to the Author of the Article.
Dave, thanks for this. Saved me a lot of work!!
I ran into this issue installing SQL Server 2017 on a clean Windows 2012 R2 VM system. I was surprised to see this.
Thanks. It was a great help.
Just got same error on a test machine with SQL 2016 install on a win 2012R2 running AD service.
Just get to the services after the install was done (failed), update login info then start it
Install SQL Server 2014 on Domain Controller
Microsoft does not recommend installing Microsoft SQL Server on a Windows Server that has the role of Domain Controller because of account security issues
http://www.microsoft.com/en-us/download/details.aspx?id=15289
How to work around this problem and get install SQL SERVER in a Domain Control?
SQL AGENT is not activated.
It works! Thanks a lot, Pinal! And about crossfit? Are you still doing it?
Hi, I’m receiving this error when trying to install sql server on my cluster lab, how can I solve it?
Thank you very much – this post resolved my error!
Resolveu meu problema. Excelente!