Running SQL Server 2022 Express edition on Windows Server 2022 with TLS 1.3 only

Copper Contributor

Hello there,

I tried running SQL server 2022 express on Windows 2022 Server that had SSL and TLS 1.0-1.2 disabled. But couldn't start the SQL server. Got the following error. Can you please explain if this is supported or not?

svazdekis_0-1675129305744.png

 

2 Replies

@svazdekis , yes, SQL Server 2022 supports TLS 1.3, see TDS 8.0 and TLS 1.3 support - SQL Server | Microsoft Learn

 

Do what the error message says, review Windows EventLog & SQL Server ErrorLog for more details.

@olafhelper looks like SQL Server 2022 Express still requires TLS 1.2 or SSL. I get this error when starting the SQL server on a TLS 1.3 only 2022 server.

Error: 26011, Severity: 16, State: 1.
2023-02-01 06:36:44.22 spid38s 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.
2023-02-01 06:36:44.68 spid38s Error: 17182, Severity: 16, State: 1.
2023-02-01 06:36:44.68 spid38s 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-02-01 06:36:44.70 spid38s Error: 17182, Severity: 16, State: 1.
2023-02-01 06:36:44.70 spid38s 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-02-01 06:36:44.91 spid38s Error: 17826, Severity: 18, State: 3.
2023-02-01 06:36:44.91 spid38s 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-02-01 06:36:44.92 spid38s Error: 17120, Severity: 16, State: 1.
2023-02-01 06:36:44.92 spid38s 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.