Encountered "Could not find the Database Engine startup handle" while installing MS SQL 2019 standalone

Question

Encountered "Could not find the Database Engine startup handle" while installing MS SQL 2019 standalone

Murphy 0

Hello everyone,

I am struck at installing MS SQL 2019 database engine with my machine running MS server 2019.

The error "Could not find the Database Engine startup handle" came at the almost finishing installation part.

Any good suggestion? I tried uninstalling completely all SQL components and reinstalled with administrator rights.

Below is the log:

Machine Properties:
  Machine name:                  WIN-5IEAF9UCUGJ
  Machine processor count:       32
  OS version:                    Microsoft Windows Server 2019 Standard (10.0.17763)
  OS service pack:               
  OS region:                     United States
  OS language:                   English (United States)
  OS architecture:               x64
  Process architecture:          64 Bit
  OS clustered:                  No

Package properties:
  Description:                   Microsoft SQL Server 2019 
  ProductName:                   SQL Server 2019
  Type:                          RTM
  Version:                       15
  SPLevel:                       0
  Installation location:         C:\POC Solarwind\SQL\x64\setup\
  Installation edition:          Standard

Product Update Status:
  User selected not to include product updates.

Notice: A paid SQL Server edition product key has been provided for the current action - Standard. Please ensure you are entitled to this SQL Server edition with proper licensing in place for the product key (edition) supplied.

User Input Settings:
  ACTION:                        Install
  ADDCURRENTUSERASSQLADMIN:      false
  AGTSVCACCOUNT:                 NT Service\SQLSERVERAGENT
  AGTSVCPASSWORD:                *****
  AGTSVCSTARTUPTYPE:             Manual
  ASBACKUPDIR:                   Backup
  ASCOLLATION:                   Latin1_General_CI_AS
  ASCONFIGDIR:                   Config
  ASDATADIR:                     Data
  ASLOGDIR:                      Log
  ASPROVIDERMSOLAP:              1
  ASSERVERMODE:                  TABULAR
  ASSVCACCOUNT:                  <empty>
  ASSVCPASSWORD:                 <empty>
  ASSVCSTARTUPTYPE:              Automatic
  ASSYSADMINACCOUNTS:            <empty>
  ASTELSVCACCT:                  <empty>
  ASTELSVCPASSWORD:              <empty>
  ASTELSVCSTARTUPTYPE:           0
  ASTEMPDIR:                     Temp
  BROWSERSVCSTARTUPTYPE:         Disabled
  CLTCTLRNAME:                   <empty>
  CLTRESULTDIR:                  <empty>
  CLTSTARTUPTYPE:                0
  CLTSVCACCOUNT:                 <empty>
  CLTSVCPASSWORD:                <empty>
  CLTWORKINGDIR:                 <empty>
  COMMFABRICENCRYPTION:          0
  COMMFABRICNETWORKLEVEL:        0
  COMMFABRICPORT:                0
  CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\150\Setup Bootstrap\Log\20231106_111942\ConfigurationFile.ini
  CTLRSTARTUPTYPE:               0
  CTLRSVCACCOUNT:                <empty>
  CTLRSVCPASSWORD:               <empty>
  CTLRUSERS:                     <empty>
  ENABLERANU:                    false
  ENU:                           true
  EXTSVCACCOUNT:                 <empty>
  EXTSVCPASSWORD:                <empty>
  FEATURES:                      SQLENGINE
  FILESTREAMLEVEL:               0
  FILESTREAMSHARENAME:           <empty>
  FTSVCACCOUNT:                  <empty>
  FTSVCPASSWORD:                 <empty>
  HELP:                          false
  IACCEPTPYTHONLICENSETERMS:     false
  IACCEPTROPENLICENSETERMS:      false
  IACCEPTSQLSERVERLICENSETERMS:  true
  IACKNOWLEDGEENTCALLIMITS:      false
  INDICATEPROGRESS:              false
  INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
  INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
  INSTALLSQLDATADIR:             <empty>
  INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
  INSTANCEID:                    MSSQLSERVER
  INSTANCENAME:                  MSSQLSERVER
  ISMASTERSVCACCOUNT:            NT AUTHORITY\Network Service
  ISMASTERSVCPASSWORD:           <empty>
  ISMASTERSVCPORT:               8391
  ISMASTERSVCSSLCERTCN:          <empty>
  ISMASTERSVCSTARTUPTYPE:        Automatic
  ISMASTERSVCTHUMBPRINT:         <empty>
  ISSVCACCOUNT:                  NT AUTHORITY\Network Service
  ISSVCPASSWORD:                 <empty>
  ISSVCSTARTUPTYPE:              Automatic
  ISTELSVCACCT:                  <empty>
  ISTELSVCPASSWORD:              <empty>
  ISTELSVCSTARTUPTYPE:           0
  ISWORKERSVCACCOUNT:            NT AUTHORITY\Network Service
  ISWORKERSVCCERT:               <empty>
  ISWORKERSVCMASTER:             <empty>
  ISWORKERSVCPASSWORD:           <empty>
  ISWORKERSVCSTARTUPTYPE:        Automatic
  MATRIXCMBRICKCOMMPORT:         0
  MATRIXCMSERVERNAME:            <empty>
  MATRIXNAME:                    <empty>
  MRCACHEDIRECTORY:              
  NPENABLED:                     0
  PBDMSSVCACCOUNT:               <empty>
  PBDMSSVCPASSWORD:              <empty>
  PBDMSSVCSTARTUPTYPE:           0
  PBENGSVCACCOUNT:               <empty>
  PBENGSVCPASSWORD:              <empty>
  PBENGSVCSTARTUPTYPE:           0
  PBPORTRANGE:                   <empty>
  PBSCALEOUT:                    false
  PID:                           *****
  QUIET:                         false
  QUIETSIMPLE:                   false
  ROLE:                          
  RSINSTALLMODE:                 DefaultNativeMode
  RSSVCACCOUNT:                  <empty>
  RSSVCPASSWORD:                 <empty>
  RSSVCSTARTUPTYPE:              Automatic
  SAPWD:                         <empty>
  SECURITYMODE:                  <empty>
  SQLBACKUPDIR:                  <empty>
  SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
  SQLJAVADIR:                    <empty>
  SQLMAXDOP:                     8
  SQLMAXMEMORY:                  2147483647
  SQLMINMEMORY:                  0
  SQLSVCACCOUNT:                 NT Service\MSSQLSERVER
  SQLSVCINSTANTFILEINIT:         false
  SQLSVCPASSWORD:                *****
  SQLSVCSTARTUPTYPE:             Automatic
  SQLSYSADMINACCOUNTS:           WIN-5IEAF9UCUGJ\Administrator
  SQLTELSVCACCT:                 NT Service\SQLTELEMETRY
  SQLTELSVCPASSWORD:             <empty>
  SQLTELSVCSTARTUPTYPE:          Automatic
  SQLTEMPDBDIR:                  <empty>
  SQLTEMPDBFILECOUNT:            8
  SQLTEMPDBFILEGROWTH:           64
  SQLTEMPDBFILESIZE:             8
  SQLTEMPDBLOGDIR:               <empty>
  SQLTEMPDBLOGFILEGROWTH:        64
  SQLTEMPDBLOGFILESIZE:          8
  SQLUSERDBDIR:                  <empty>
  SQLUSERDBLOGDIR:               <empty>
  SUPPRESSPAIDEDITIONNOTICE:     false
  SUPPRESSPRIVACYSTATEMENTNOTICE: false
  TCPENABLED:                    1
  UIMODE:                        Normal
  UpdateEnabled:                 false
  UpdateSource:                  MU
  USEMICROSOFTUPDATE:            false
  USESQLRECOMMENDEDMEMORYLIMITS: false
  X86:                           false

  Configuration file:            C:\Program Files\Microsoft SQL Server\150\Setup Bootstrap\Log\20231106_111942\ConfigurationFile.ini

Detailed results:
  Feature:                       Database Engine Services
  Status:                        Failed
  Reason for failure:            An error occurred during the setup process of the feature.
  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:          0x851A0019
  Error description:             Could not find the Database Engine startup handle.
  Error help link:               https://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=15.0.2000.5&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025

  Feature:                       SQL Browser
  Status:                        Passed

  Feature:                       SQL Writer
  Status:                        Passed

  Feature:                       SQL Client Connectivity SDK
  Status:                        Passed

  Feature:                       SQL Client Connectivity
  Status:                        Passed

  Feature:                       Setup Support Files
  Status:                        Passed

Rules with failures or warnings:

Rules report file:               C:\Program Files\Microsoft SQL Server\150\Setup Bootstrap\Log\20231106_111942\SystemConfigurationCheck_Report.htm

Answer 1

Hi @Murphy

Could you please post the error logs in txt?

There is a summary.txt file and many subfolders created every time the Installation wizard is started. In those subfolders, we can find a Detail.txt file.

View and Read SQL Server Setup Log Files - SQL Server | Microsoft Learn

You can look at the prerequisites for SQL Server 2019.

https://learn.microsoft.com/en-us/sql/sql-server/install/hardware-and-software-requirements-for-installing-sql-server-2019?view=sql-server-ver16
Have you tried this:

Uninstall all the SQL instances one by one. Goto--control panel - uninstall a program - Microsoft SQL server (64 bit) - select remove option, select the particular instance, and uninstall
Repeat the same process till you uninstall all instances. Goto C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER (MSSQLSERVER indicates instances). Should not have any instances like this ex: MSSQL15.MSSQLSERVER.
Restart the computer and run as administrator choose basic installation process.

Best regards,

Percy Tang

Answer 2

Erland Sommarskog 92,801

The message Wait on the Database Engine recovery handle failed is a generic error that means that SQL Server did not start when Setup wanted to run configuration steps. To understand why it did not start, you need to look in the SQL Server errorlog, which you find in C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\LOG\ERRORLOG.

Feel free to upload that file error. You will need to rename it to ERRORLOG.txt for the forum software to accept it.

Also, please ignore Percy's post until we have looked at the file and know what is wrong.

Murphy 0 Reputation points

2023-11-08T08:10:43.1833333+00:00

ERRORLOG.txt ERRORLOG.1.Txt ERRORLOG.3.txt ERRORLOG.2.txt

Hello Erland and Percy,

Thanks for pointing out the error log location.

I have uploaded the 4 error log files generated though they seemed similar.
Erland Sommarskog 92,801 Reputation points

2023-11-08T22:24:26.5533333+00:00

The error logs have these errors:

2023-11-07 10:11:03.15 spid16s Error: 26011, Severity: 16, State: 1. 2023-11-07 10:11:03.15 spid16s The server was unable to initialize encryption because of a problem with a security library. The security library may be missing. Verify that security.dll exists on the system. 2023-11-07 10:11:03.15 spid16s Error: 17182, Severity: 16, State: 1. 2023-11-07 10:11:03.15 spid16s TDSSNIClient initialization failed with error 0x139f, status code 0x80. Reason: Unable to initialize SSL support. The group or resource is not in the correct state to perform the requested operation. 2023-11-07 10:11:03.15 spid16s Error: 17182, Severity: 16, State: 1. 2023-11-07 10:11:03.15 spid16s TDSSNIClient initialization failed with error 0x139f, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. The group or resource is not in the correct state to perform the requested operation. 2023-11-07 10:11:03.15 spid16s Error: 17826, Severity: 18, State: 3. 2023-11-07 10:11:03.15 spid16s 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. 2023-11-07 10:11:03.15 spid16s Error: 17120, Severity: 16, State: 1. 2023-11-07 10:11:03.15 spid16s SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the operating system error log for information about possible related problems.

This usually indicates that the default profile in Windows is corrupted.

I've run into this at some occasion and googled around. I think a common suggestion was to copy the profile from another computer. I think in my case, I eventually opted to restore it from a backup. I should add that in my case it was my desktop at home, not a server as in your case.

Encountered "Could not find the Database Engine startup handle" while installing MS SQL 2019 standalone

2 answers

Activity