When you try to install Microsoft SQL Server 2012 or SQL Server 2014 on a server that has Transport Layer Security (TLS) version 1.2 enabled, you may encounter the following issues:
- If the version of SQL Server that you're trying to install doesn't contain the fix to enable TLS 1.2 support (for more information about the build that adds TLS 1.2 support, see KB 3052404), you receive the following error message:
Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
- If the version of SQL Server that you're trying to install does contain the fix to enable TLS 1.2 support, you receive the following error message:A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: Named Pipes Provider, error: 0 - No process is on the other end of the pipe.)
This issue occurs because SQL Server Setup uses SqlClient for ADO.NET from the .NET Framework 2.0. By default, the .NET Framework 2.0 works with TLS 1.0.
To resolve this issue, install the hotfix rollup for the .NET Framework, and then restart the server. Use following table to find the appropriate hotfix, based on the operating system and SQL Server version that you're running:
|Operating system version||Hotfix|
|Windows 2012 R2 and Windows 8.1||Hotfix rollup 3106993 for the .NET Framework 2.0 SP2 in Windows Server 2012 R2 and Windows 8.1|
|Windows Server 2012 and Windows 8||Hotfix rollup 3106992 for the .NET Framework 2.0 SP2 on Windows Server 2012 and Windows 8|
|Windows Server 2008 R2 SP1 and Windows 7 SP1||Hotfix rollup 3106991 for the .NET Framework 2.0 SP2 in Windows Server 2008 R2 SP1 and Windows 7 SP1|
To work around this issue, follow these steps:
- Enable TLS 1.0 on the server.
- Restart the server.
- Run the SQL Server 2012 or SQL Server 2014 Setup program, and update the SQL Server version to a build that supports TLS 1.2. (For more information about the updates that add support for TLS 1.2, see KB 3052404.)
- Disable TLS 1.0.
- Restart the server.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.