SQL Server 2016,2014 cannot find the database engine startup handle

when I decided to install the SharePoint it preview, I thought I should install it on Windows Server 2016 Technical preview and the SQL Server 2016 Community Technology Preview (CTP). I bet you may not realize that today there are many different names, and the Times that were formerly known as "beta" are long gone.

The installation of Windows Server Technical Preview is simple, but when I start installing SQL Server 2012 on Hyper-V Windows Server Technical Preview, Have encountered some problems. When I started encountering some errors during SQL Server CTP2.3 Setup, I decided to better address these issues because version 2016 will be the most compatible version of Windows Server 2016 and SharePoint Server 2016. All of these products are still in beta, so before I start installing these products for my commercial customers, I have to be patient with these errors.

# 1 Error

During SQL Server installation, you may experience the following error warning:

"Database engine startup handle not found"

In the upper screen, the handle is spelled incorrectly. The screen in this article is from SQL Server CTP2.3 that is running on Windows Server Technical Preview. I have encountered this error only in SQL Server CTP2.3, and may also encounter this error in SQL Server 2014 or 2008.

#2 Reference Steps

1. If you already have SQL Server installed, you should completely remove it from the Control Panel and restart the server.

2. When you enter 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 the drop-down box, selecting Browse, and then typing SYSTEM in the Select Users, Computers, service accounts, or Groups window in Active Directory. Click OK to accept the new account.

4. Looks similar to the following screen.

5. Follow the configuration Wizard to proceed with the installation.

6. Reinstall should not prompt " database engine startup handle not found " error

Hope to help you!

#3

After the SQL Server installation is complete, you should restart the Windows Server. Yes, even if you are not prompted to restart the server, you must restart the server after you install SQL Server,sharepoint Server, or you may experience problems.

Official recommendation after the installation is complete, you should change this account back to the low-privileged domain account that will run the SQL Database engine service.

http://social.technet.microsoft.com/wiki/contents/articles/24364. Sql-server-troubleshooting-could-not-find-database-engine-startup-handle-error-during-installation.aspx

As described above, to change the account back to a low-privileged domain account, follow the steps in this section. A domain account can be just a regular domain user account, not an administrator, but it may require special permissions in SQL Server (not Windows Server or Active Directory domains). For example, by default, NT service \ Mssqlservice and NT service \ SQLServerAgent have sysadmin permissions on SQL Server, which means that the domain account used as the service account will require the SQL These permissions on the server.

Also, it is important to note that restarting SQL Server means that you are making SQL Server unavailable until the service starts again. Although this is usually short, it is best to perform this step outside of normal business hours.

SQL Server 2016,2014 cannot find the database engine startup handle