Windows OS Hub
  • Windows Server
    • Windows Server 2016
    • Windows Server 2012 R2
    • Windows Server 2012
    • Windows Server 2008 R2
    • SCCM
  • Active Directory
    • Group Policies
  • Windows Clients
    • Windows 10
    • Windows 8
    • Windows 7
    • MS Office
    • Outlook
  • Virtualization
    • VMWare
    • Hyper-V
  • PowerShell
  • Exchange
  • Home
  • About

Windows OS Hub

  • Windows Server
    • Windows Server 2016
    • Windows Server 2012 R2
    • Windows Server 2012
    • Windows Server 2008 R2
    • SCCM
  • Active Directory
    • Group Policies
  • Windows Clients
    • Windows 10
    • Windows 8
    • Windows 7
    • MS Office
    • Outlook
  • Virtualization
    • VMWare
    • Hyper-V
  • PowerShell
  • Exchange

 Windows OS Hub / SQL Server / SQL Server Install Error: Could Not Find the Database Engine Startup handle

September 30, 2019 SQL Server

SQL Server Install Error: Could Not Find the Database Engine Startup handle

I came across an interesting error when installing MS SQL Server 2014 on a new VM running Windows Server 2012 R2. SQL Server setup was interrupted almost at the end with the error “Could not find the Database Engine startup handle”.

Could not find the Database Engine startup handle - SQL Server 2014 Install error

There was the following error in the SQL installation log (summary.txt file):

Feature: Database Engine Services
Status: Failed: see logs for details
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.

This MS SQL Server installation error is related to standard installation settings when SQL Server is run under an unprivileged account NT Service\MSSQL$V2014. This account may not have the privilege to run SQL Server service, so the service cannot be run and the installer returns the “Could not find the Database Engine startup handle” error. Also, this error may indicate that somebody has already tried to install SQL Server on this computer and files or services left after the installation have not been removed.

To fix the SQL Server install error:

  1. Correctly uninstall all programs related to SQL Server from the Control Panel and restart your server (make sure there are no files or folders in the folder C:\Program Files\Microsoft SQL Server\MSSQL12.xxx).;
  2. Run the installation from the SQL Server distribution from scratch. On the Server Configuration tab, make sure that the SQL Server Database Engine service is run under NT Service\MSSQLSERVER account; SQL Server Database Engine - service account name NT Service\MSSQLSERVER
  3. Change this account to NT AUTHORITY\SYSTEM; install Sql Server under NT AUTHORITY\SYSTEM
  4. Continue the SQL Server installation. The error shouldn’t appear again.

After the installation is complete, we strongly recommend to change the account, under which SQL Server Database Engine is run, to an unprivileged account. You don’t need to grant this account local administrator permissions ( it’s enough to provide necessary privileges inside SQL Server security settings). You can use accounts with sysadmin privileges: NT Service\MSSQLSERVICE or NT Service\SQLSERVERAGENT. To change the account, under which SQL Server runs:

  1. Run the SQL Server Configuration Manager and go to SQL Server Services;
  2. Click SQL Server (MSSQLSERVER), then click Browse and in the “This account” field specify the account, under which the service must be run, or use a gMSA  (Group Managed Service Account). Enter the user password and save the changes; Changing The SQL Server Service Account In SQL
  3. Restart SQL Server services.

This method will help you to fix the “Could not find the Database Engine startup handle” error during the installation of any SQL Server versions (2016, 2014, 2012 or 2008 r2).

0 comment
0
Facebook Twitter Google + Pinterest
previous post
How to Disable UAC Prompt for Specific Applications in Windows 10?
next post
Installing SFTP (SSH FTP) Server on Windows with OpenSSH

Related Reading

Change the Default Port Number (TCP/1433) for a...

February 24, 2021

MS SQL Server 2019 Installation Guide: Basic Settings...

January 19, 2021

Querying Microsoft SQL Server (MSSQL) Database with PowerShell

November 18, 2020

FAQ on Microsoft SQL Server Licensing

October 7, 2020

How to Obtain SeDebugPrivilege when Debug Program Policy...

December 28, 2017

Leave a Comment Cancel Reply

Categories

  • Active Directory
  • Group Policies
  • Exchange
  • Windows 10
  • Windows 8
  • Windows 7
  • Windows Server 2016
  • Windows Server 2012 R2
  • Windows Server 2008 R2
  • PowerShell
  • VMWare
  • MS Office

Recent Posts

  • How to Disable NetBIOS and LLMNR Protocols in Windows Using GPO?

    April 9, 2021
  • Enable Windows Lock Screen after Inactivity via GPO

    April 8, 2021
  • How to Create and Manage Scheduled Tasks with PowerShell?

    April 7, 2021
  • Updating Windows VM Templates on VMWare with PowerShell

    April 5, 2021
  • Running Multiple IIS Websites on the Same Port or IP Address

    April 1, 2021
  • Can’t Copy and Paste via Remote Desktop (RDP) Clipboard

    March 31, 2021
  • UAC: This App Has Been Blocked for Your Protection on Windows 10

    March 30, 2021
  • How to Unlock a File Locked by Any Process or SYSTEM?

    March 29, 2021
  • Configuring a Domain Password Policy in the Active Directory

    March 26, 2021
  • Using Native Package Manager (WinGet) on Windows 10

    March 24, 2021

Follow us

woshub.com
  • Facebook
  • Twitter
  • RSS
Popular Posts
  • FAQ on Microsoft SQL Server Licensing
  • Querying Microsoft SQL Server (MSSQL) Database with PowerShell
Footer Logo

@2014 - 2018 - Windows OS Hub. All about operating systems for sysadmins


Back To Top