Forum Discussion
Not able to start SQL Services using SQL Server 2022 and when only TLS 1.3 protocol is enabled
Not able to start SQL Services (SQL Server and SQL Server Agent ) using SQL Server 2022 and when only TLS 1.3 protocol is enabled.
There are no other protocol enabled like TLS 1.0, TLS 1.1 or TLS 1.2. I have installed SQL Server 2022 + CU3.
ODBC Driver for SQL Server version 18.1.2.1 OLE DB Driver for SQL Server version 19.2.0
I have also installed ODBC and OLE Db driver with SQL server 2022 CU3 (16.x) + CU3 version.
Also, tried to install one SQL certificate and enabled strict encryption but stil unable to start SQL services.
Used following link to generate SQL certificate : https://learn.microsoft.com/en-us/sql/database-engine/configure-windows/configure-sql-server-encryption?view=sql-server-ver16#powershell-script-to-create-self-signed-certificate-for-sql-server Attached error log and error message.
Note : If I enable TLS 1.2 along with TLS 1.3 then SQL services are starting but we need only TLS 1.3 enabled and run services using only TLS 1.3
Error log :
2023-07-06 01:47:25.79 spid17s Error: 17182, Severity: 16, State: 1.2023-07-06 01:47:25.79 spid17s TDSSNIClient initialization failed with error 0x139f, status code 0x80. Reason: Unable to initialize SSL support. The group or resource is not in the correct state to perform the requested operation.2023-07-06 01:47:25.79 spid17s Error: 17182, Severity: 16, State: 1.2023-07-06 01:47:25.79 spid17s TDSSNIClient initialization failed with error 0x139f, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. The group or resource is not in the correct state to perform the requested operation.2023-07-06 01:47:25.79 spid17s Server is listening on [ ::1 <ipv6> 60742] accept sockets 1.2023-07-06 01:47:25.79 spid17s Server is listening on [ 127.0.0.1 <ipv4> 60742] accept sockets 1.2023-07-06 01:47:25.79 spid17s Server local connection provider is ready to accept connection on [ \\.\pipe\sqlsatellitelaunchHELIOSSQL3 ].2023-07-06 01:47:25.79 spid17s Resource governor reconfiguration encountered an issue (HRESULT code : 0x80070002, reason: Construction of Launchpad Connection failed), while sending active external resource pool ids to launchpad. This will not fail reconfigure.2023-07-06 01:47:25.79 spid17s Error: 17826, Severity: 18, State: 3.2023-07-06 01:47:25.79 spid17s Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.2023-07-06 01:47:25.79 spid17s Error: 17120, Severity: 16, State: 1.2023-07-06 01:47:25.79 spid17s SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the operating system error log for information about possible related problems.
Hi,
I am also facing the same issue, not able to start SQL Services (SQL Server and SQL Server Agent ) using SQL Server 2022 and when only TLS 1.3 protocol is enabled.
Used the following links for setup installation.
https://learn.microsoft.com/en-us/sql/relational-databases/security/networking/tls-1-3?view=sql-server-ver16
https://learn.microsoft.com/en-us/sql/relational-databases/security/networking/connect-with-strict-encryption?view=sql-server-ver16
ODBC Driver for SQL Server version 18.2.2.1 OLE DB Driver for SQL Server version 19.3.1.0
I have installed ODBC and OLE Db driver with SQL server 2022 CU6 (16.x)
Cumulative update 6 for SQL Server 2022 (KB5027505) - SQL Server | Microsoft Learn
Followed the below link to configure SQL Server Database Engine for encrypting connections:
https://learn.microsoft.com/en-us/sql/database-engine/configure-windows/configure-sql-server-encryption?view=sql-server-ver16
Error log:
Error: 26011, Severity: 16, State: 1.
The server was unable to initialize encryption because of a problem with a security library. The security library may be missing. Verify that security.dll exists on the system.
Error: 17182, Severity: 16, State: 1.
TDSSNIClient initialization failed with error 0x139f, status code 0x80. Reason: Unable to initialize SSL support. The group or resource is not in the correct state to perform the requested operation.
Error: 17182, Severity: 16, State: 1.
TDSSNIClient initialization failed with error 0x139f, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. The group or resource is not in the correct state to perform the requested operation.
Error: 17826, Severity: 18, State: 3.
Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
Error: 17120, Severity: 16, State: 1.
SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
