After installing SQL Server 2014 SP1 CU1 (build version 12.0.4416.1) the SQL Server service no longer fails to start when TLS 1.0 is disabled, but no matter what I have tried I can't successfully connect to the database.

When trying connect using shared memory I get this message:

A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - No process is on the other end of the pipe.) (Microsoft SQL Server, Error: 233)

And if I tryTCP/IP or Named Pipes I get this:

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)

TLS 1.1 and TLS 1.2 are enabled on the computer and working fine for IIS.

Any Ideas on what I can do to get SQL Server to work successfully with TLS 1.2 or is it still just not supported yet?

Hello,

TLS 1.2 is not supported yet and it seems it will be supported on SQL Server 2016. Please read the following Connect item:

https://connect.microsoft.com/SQLServer/feedback/details/1073492/sql-server-depends-on-old-ssl-tls-versions

Hope this helps.

Regards,

Alberto Morillo
SQLCoffee.com

• Edited by Alberto MorilloMVP, Moderator Wednesday, June 24, 2015 7:00 PM
• Proposed as answer by Raul Garcia - MSMicrosoft employee, Moderator Thursday, June 25, 2015 12:34 AM
• Marked as answer by Eric Arstein Thursday, June 25, 2015 12:43 AM

Hello,

TLS 1.2 is not supported yet and it seems it will be supported on SQL Server 2016. Please read the following Connect item:

https://connect.microsoft.com/SQLServer/feedback/details/1073492/sql-server-depends-on-old-ssl-tls-versions

Hope this helps.

Regards,

Alberto Morillo
SQLCoffee.com

• Edited by Alberto MorilloMVP, Moderator Wednesday, June 24, 2015 7:00 PM
• Proposed as answer by Raul Garcia - MSMicrosoft employee, Moderator Thursday, June 25, 2015 12:34 AM
• Marked as answer by Eric Arstein Thursday, June 25, 2015 12:43 AM

Thanks for the quick reply, I was kind of expecting that was the case but figured it wouldn't hurt to ask.

If you've installed the CU from https://support.microsoft.com/en-us/kb/3067839, make sure you install the ODBC/client side updates as well. If you're using the unmanaged clients, you need to install the ODBC installer (named SQL2014_SP1_ODBC_CU1_3067839_12_0_4416 in the hotfix download).

Wait a minute! What does it means then that KB 3052404 is fixed in CU1 for SQL Server 2014 SP1???

Do you have a solution for this problem?

I have the same problem.

Afster installing the hotfix for TLS 1.2 (https://support.microsoft.com/en-us/kb/3046038)

I got the error

 A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - No process is on the other end of the pipe.)

Do you have a solution for this problem?

I have the same problem.

Afster installing the hotfix for TLS 1.2 (https://support.microsoft.com/en-us/kb/3046038)

I got the error

 A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - No process is on the other end of the pipe.)

I have a server with the same problem. It's installed with SQL 2014 +SP1 + CU1. I installed this combo specifically because of the TLS 1.2 patch included with CU1. I went ahead and disabled TLS1.0 and SSL3. Now... SQL Server starts (thankfully), but SSMS won't start. I get the same error that BartSmash is getting. SQLServerAgent also won't start. I get a pretty non-descript error in the Application Log when I try to start the service:

SQLServerAgent could not be started (reason: Unable to connect to server '(local)'; SQLServerAgent cannot start).

I'd love to get an update with current information about this. The info from connect.microsoft.com says that an update for 2014 will probably be made available. According to the SP1/CU1 information, we should be able to connect to SQL with TLS1.2. Why isn't this working?

Thanks!

You can connect using SSMS after installing dot net 4 point 6 for sqlagent you need hotfix kb3052468 SNAC update

• Edited by Rubin Siller 11 hours 8 minutes ago added sqlagent fix
• Proposed as answer by svallarian 7 hours 52 minutes ago

I can confirm that Rubin's fix works. Installing .net 4.6 allows management studio to connect.

• Edited by svallarian 7 hours 52 minutes ago