SQL Server 2016 Installation Errors and Solution

In this article, I am going to talk about the common errors faced during SQL Server 2016 with Sp1 installation and configuration.

Error 1:

Setup contains lots of components, so installation running considerable amount of time was expected. But after few minutes, it was only 30% finished and the setup was still trying to install the same package. It seemed that the installation got stuck. The error is as below,

Microsoft visual studio 2015 shell isolated SQL stuck.

Root cause:

1. vs_shell.exe process has been locked by other other process.
2. Another Installation is in progress and require System restart.

Solution:

1. Cancel the setup, but even that got stuck
2. Go to Task Manager to end the installation by stopping the process
3. Restart the computer and try again

Error 2:

While installtion SQL Server 2016 with SP1, the more commong error is,

Could not find the Database Engine startup handle.

Solution:

1. 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.
2. 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.
3. Click OK to accept the new account.
4. Your screen should look similar to the screenshot below.
5. Continue on with the installation as normal.
6. You should no longer receive the error Could not find the Database Engine startup handle during installation.

Error 3:

This is related to tcp-ip and port issue.

1. The TCP/IP connection to the host localhost, port 1433 has failed.
2. The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption.

Solution:

1. 1. Go to Start – Microsoft SQL Server – Configuration Tools – SQL Server Configuration Manager.
   2. Go to SQL Server Configuration Manager – SQL Server Network Configuration – Protocols for SQLExpress
   3. Check if Protocol TCP/IP disabled. If yes, then it Click on TCP/IP and its properties.
   4. Remove All the TCP Dynamic Ports and Add value of 1433 to all TCP Port as like below screenshot
   5. Restart your SQL Server Services – SQL Server. And It’s Done…

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.