SQL SERVER – Installation Failed With Error – Wait on the Database Engine Recovery Handle Failed

SQL
7 Comments

You might have seen on Facebook that I have completed the new setup of my machines. Since I use VMs to do my tests. To have a domain, I made a VM as domain controller and another as a member server. Next step was to install SQL Server and by mistake, I have run the setup of SQL on a domain controller. As per Microsoft documentation they don’t recommend installing SQL on the domain controller and there is a warning in SQL Setup. Let us learn about how to fix Installation Failed With Error.

SQL SERVER - Installation Failed With Error - Wait on the Database Engine Recovery Handle Failed setup-dc-01

—————————
Rule Check Result
—————————
Rule “Computer domain controller” generated a warning.
Installing SQL Server 2016 CTP2.4 on a domain controller is not recommended.
—————————
OK
—————————
I proceeded further and it failed at the end with below error
Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Here is the complete message in summary.txt file.
Feature:                       SQL Server Replication
Status:                        Failed: see logs for details
Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name:                SQL Server Database Engine Services Instance Features
Component error code:          0x851A001A
Error description:             Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
I followed the error message as it asked to check ERRORLOG. Here is message in ERRORLOG
Error: 17190, Severity: 16, State: 1.
Initializing the FallBack certificate failed with error code: 1, state: 20, error number: 0.
Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
Error: 17182, Severity: 16, State: 1.
TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property.
Error: 17182, Severity: 16, State: 1.
TDSSNIClient initialization failed with error 0x80092004, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Cannot find object or property.
Error: 17826, Severity: 18, State: 3.
Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
Error: 17120, Severity: 16, State: 1.
SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

Solarwinds

I searched on the internet and found that this could be issued with a SQL Service account. I selected all default configuration and it was NT Service\MSSQLServer

I uninstalled SQL Server and this time I selected Local System account for SQL Service in setup wizard and voilà it went fine.

Have you ever faced any such error on a regular machine? What was the solution?

Reference : Pinal Dave (https://blog.sqlauthority.com)

Solarwinds
, ,
Previous Post
SQL SERVER – Backup to Azure Blob error – The remote server returned an error: (409) Conflict
Next Post
Interview Question of the Week #045 – How to Do Case Sensitive Search?

Related Posts

7 Comments. Leave new

  • Once again, stellar advice. Thanks.

    Reply
  • I’m currently running into this same problem. However, I’ve got a Windows 2012 Essentials server, and because of this, my server is also my DC. It won’t allow me to use Local or Network System accounts. Not sure what my options are.

    Reply
    • Jeff – did you manage to get round your problem. I have the same issue.

      Reply
      • I used the NT AUTHORITY\NETWORK SERVICE account for the Database Engine configuration

      • OK. I created an account in AD just for the SQL account. It worked fine then. SQL on a DC isn’t supported but I think for Dev work it’s fine.

  • I ran into the same issue today and resolved the issue using the NT AUTHORITY\NETWORK SERVICE account for the Database Engine entry in the configuration dialog. The installation succeeded. I did not completely uninstall but ony removed the database engine and then added it back using the modified user account. I will check it out and get back if there any issues with this fix

    Reply
  • Ramkumar Kandappan
    February 14, 2016 8:44 pm

    Thank you, It helped me… I exactly got the same error and your solution is the fix for me

    Reply

Leave a Reply

Menu