Службы компонентов database engine ошибка

---

 

---

Introduction

This article is about how to proceed when you get error message ‘Could not find database engine startup handle ‘ while installing SQL Server 2008 R2/2012 or 2014.

↑ Back to top

---

Problem Definition

 If you are an active member of
SQL Server Setup and Upgrade forum you must have noticed some users creating a thread with error messages of  ‘Could not find database engine startup handle ‘
while installing SQL Server . This article tries to provide a simple solution to this problem, that many users face during installation of SQL Server 2008 R2, SQL Server 2012 and SQL Server 2014 as well.

Let’s get started. For resources on installing SQL Server 2008/R2/2012/2014; there are lot of good articles which you find in Suggested Readings section .

Its common belief that installation of SQL Server is very easy,  just do *Next, Next * and installation would be complete.

It is correct, it’s simple but internally what all operations go a general user is not aware about it and when he faces issue he feels that SQL Server product is not good ( this is my forum experience where many of Original Poster (OP) get frustrated with
SQL Server installation error). It’s recommend to read below Microsoft articles before proceeding with installation of SQL Server

1.  Hardware and Software requirement for installing SQL Server
2.  Install SQL Server from installation wizard
3.  How to use SQL Server in win 8 and Windows Server environment

Problem is when a user tries to install SQL Server 2012 or 2014 or 2008 R2 during installation error is flashed which says

Could not find database engine startup handle and some Hex error like ‘0x851a0019’ error could also be ‘Wait on the Database Engine recovery handle failed’.

↑ Back to top

---

Cause

Following can be the reason behind the error message.

1. The account which user selected on Server Configuration page window ( during installation)  is somehow not able to bring SQL Server database engine services online. Either is lacks privilege or it is corrupted. During installation of database engine services
   SQL Server tries to bring online database services as a internal process but due to startup account either corrupt or not having appropriate privileges it fails to do so and ultimately installation fails.
2. Other reason is when installation fails first time due to some reason and user uninstall failed installation from add remove program, the un-installation leaves account in broken state so any further attempt to install flashes this error message.
3. The reason can be also that SQL Server installation was successful in installing SQL Server and its services but due to some other limitation in system or other system related errors SQL Server is not able to come online. The same has been discussed in
   section ‘Looking at SQL Server errorlog’ 

↑ Back to top

---

Solution

A simple solution to above problem is below.

Uninstall

If you are unable to uninstall SQL Server completely because you deleted SQL Server files and un-installation is giving error please follow below method. This method is tested and suggested on

this thread and 
Forum.

Below Solution (about removing reg keys) will work correctly for SQL Server having Just one instance.
If you have multiple instances and you have messed up SQL Server installation please contact Microsoft Support personal to get better guidance on removal of SQL Server. Please DONT use this method if you are new to SQL Server take help of experienced
DBA to locate proper registry keys and remove them if you are not confident at all it would be better calling Microsoft Support.

Note: Removing necessary registry entries might cause SQL Server instance to crash so backup registry before doing changes.

• 1. Uninstall the existing SQL Server  and all the components from the add remove program.
• 2.
  Backup the registry.
• 3. Delete the following keys using regedit:
  • —HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server
  • —HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer
• 4. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall and delete all the sub-keys referencing SQL Server.
• 5. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services and delete all the keys referencing SQL Server.
• 6. Rename all the SQL Server folders in the computer.
• 7. Reboot the machine.

Fresh install

2. Start a fresh installation. Locate Setup.exe file in SQL Server installable. It would be something like below

Always Right click on Setup file and select Run As Administrator to launch the setup.

Next you need to proceed as normally you do for installation.You will see this will solve the issue.

After installation completes please change Service Account from NT AUTHORITY\SYSTEM to a low privileged domain account. Please refer to below Microsoft link about how to configure various accounts for SQL Server and what minimum rights to provide

• Configure Windows Service Account and Permissions

To get information about Local System account please refer to below link

• Local System Account

Looking at SQL Server Errorlog

Cannot
use file ‘C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DB_NAME\master.mdf’ because it was originally formatted
with sector size 4096
and is now on a volume
with sector size

Now above error is not related to SQL Server but related to disk drive formatting on which SQL Server master data file resides. Error is beyond the scope of this article hence would not be discussed.

↑ Back to top

---

Forum threads related to this issue

This article is an outcome of my answer provided to below forum threads which faced issue ‘Could not find Database engine startup handle’. Please have a look

• Could not find database engine startup handle Thread 1
• Could Not find database engine startup handle thread 2
• Database engine startup handle issue
• Similar Thread  

If you still cannot find solution to your problem please post your question on

SQL Server Setup and Upgrade forum for more assistance. 

↑ Back to top

---

Suggested Readings

• How to Identify SQL Server Setup issue using setup log files
• How to install SQL Server 2014 
• How To Install SQL Server On Windows 8
• How to Install SQL
  Server 2012
• How to find location of setup log files generated after SQL Server Installation
• Installing SQL Server 2012 with SP1 and Product update in One Go  

---

See Also

• SQL Server General & Database Engine Resources on the TechNet Wiki
• List of articles by Shanky
• SQL Server 2014 Portal

---

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”.

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;
3. Change this account to 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;
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).

When I decided to install SharePoint 2016 IT Preview I figured I should install it on a Windows Server 2016 Technical Preview, along with SQL Server 2016 Community Technology Preview (CTP). I bet you didn’t realize there are so many different names today for what used to be simply referred to as “BETA” back in the good ol’ days. Actually, we used to  have Alpha, Beta, Release Candidate, and the Final product. But that was then, this is now. If you are really curious as to why Microsoft decided to use terminology like Community Technology Preview, visit this MSDN blog post.

Windows Server 2016 Technical Preview installation was simple but when I started to install SQL Server 2012 on Windows Server 2016 Technical Preview in Hyper-V I ran into some issues. No problem, I decided to install SQL Server 2014 but it too had some issues so I decided it makes sense to install SQL Server 2016 so let’s try that. I have installed SQL Server tons of times on different versions of SQL Server over the years and didn’t really had any major issues that I wasn’t able to resolve. When I started to run into some errors during SQL Server 2016 CTP2.3 install, I decided it better fix these issues because the 2016 version will be the most compatible version with Windows Server 2016 and SharePoint Server 2016. All these products are still in beta so I had to be patient and fix these errors before I start to install these products for my business clients down the road. Here’s the first problem and a solution. I will document the second problem and a solution in my next post.

---

---

PROBLEM

During SQL Server installation, you may run into the following error:

Could not find the Database Engine startup handle

The word handle is misspelled in the above screenshot. Microsoft should be excused because at the time I wrote this article, SQL Server 2016 was still in beta. The screenshots in this article are from SQL Server 2016 CTP2.3 running on Windows Server 2016 Technical Preview. I have experienced this error only in SQL Server 2016 CTP2.3 but you may also experience this error in SQL Server 2014 or 2008.

Here’s a solution that I found on Microsoft TechNet Wiki. There’s a lot more information in the wiki post. Here I am just documenting the steps in detail that I used to make the recommended change in the post.

SOLUTION

1. If you have installed SQL Server then you should remove it completely through the Control Panel and restart the server. If you need help, visit this wiki post for more information.
2. When you get to the Server Configuration page as shown below, you will notice that the SQL Server Database Engine service is using the account NT Service\MSSQLSERVER.
   
3. Change the account from NT Service\MSSQLSERVER to NT AUTHORITY\SYSTEM by clicking on the drop-down box, selecting browse and then typing SYSTEM in Select User, Computer, Service Account, or Group window in Active Directory. Click OK to accept the new account.
   
4. Your screen should look similar to the screenshot below.
   
5. Continue on with the installation as you normally would.
6. You should no longer receive the error Could not find the Database Engine startup handle during installation.

Best Practice: You should restart the Windows server after SQL Server installation is complete. Yes, even if you are not prompted by the system to restart the server you must restart the server after installation of SQL Server, SharePoint Server, etc. or else you may run into problems.

The wiki post recommends that after the installation is complete you should change this account back to a low-privileged domain account that will run the SQL Database Engine service. If you are still experiencing the error, please visit the wiki post because it has a lot more detail, references, links to forums, etc.

UPDATE: January 17, 2017

To change the account back to a low-privileged domain account, as mentioned above, follow the steps in this section. The domain account can be just a regular domain user account, not an administrator but it may need special permissions in SQL Server (not Windows Server, or Active Directory Domain). For example, the NT Service\MSSQLSERVICE and NT Service\SQLSERVERAGENT both have sysadmin permissions on the SQL Server by default, which means your domain account used as a service account will require these permissions on the SQL Server.

WARNING! You should only change the SQL Server service account if you are comfortable working with the SQL Server and understand how SQL Server account permissions work. If you are not sure what type of permissions are required for your SQL Server service account in your environment, I would recommend you don’t change the service account and contact a qualified SQL Server consultant or expert. Also, keep in mind that restarting the SQL Server means you are making the SQL Server unavailable until the service is started again. Although this is usually a short period, it is best that you perform this step outside of normal business hours.

1. Backup the SQL Server, including all databases.
2. Go to the SQL Server Configuration Manager.
3. Click SQL Server Services.
4. In the right-hand pane double-click SQL Server (MSSQLSERVER).
5. Click Browse and make sure the location is set to your domain, rather than your local SQL Server. If not, click Locations, select Entire Directory, and then click OK.
6. Type the name of the domain account that you want to use, click Check Names and then click OK.
7. Enter the password and then click OK.
8. You will be prompted to restart the SQL Server service. Click Yes to restart the service.
9. Your SQL Service account is now changed to a domain account.

---

Copyright © 2015 SeattlePro Enterprises, LLC. All rights reserved.

This div height required for enabling the sticky sidebar

We use cookies on our website to give you the most relevant experience by remembering your preferences and repeat visits. By clicking “Accept”, you consent to the use of ALL the cookies.