TDSSNIClient Error: 17182 Error: 26011he server was unable to initialize encryption because of a pro

2025-07-02 11:59:12.94 spid16s Server name is 'ET-DBJC'. This is an informational message only. No user action is required. 2025-07-02 11:59:12.94 spid36s Error: 26011, Severity: 16, State: 1. 2025-07-02 11:59:12.94 spid36s 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. 2025-07-02 11:59:12.94 spid36s Error: 17182, Severity: 16, State: 1. 2025-07-02 11:59:12.94 spid36s 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. 2025-07-02 11:59:12.94 spid36s Error: 17182, Severity: 16, State: 1. 2025-07-02 11:59:12.94 spid36s 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. 2025-07-02 11:59:12.95 spid36s Server is listening on [ ::1 51006]. 2025-07-02 11:59:12.95 spid36s Server is listening on [ 127.0.0.1 51006]. 2025-07-02 11:59:12.96 spid36s Server local connection provider is ready to accept connection on [ \\.\pipe\sqlsatellitelaunch ]. 2025-07-02 11:59:12.96 spid36s Resource governor reconfiguration encountered an issue (HRESULT code : 0x80040002, reason: Construction of Launchpad Connection failed), while sending active external resource pool ids to launchpad. This will not fail reconfigure. 2025-07-02 11:59:12.96 spid36s Error: 17826, Severity: 18, State: 3. 2025-07-02 11:59:12.96 spid36s 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. 2025-07-02 11:59:12.96 spid36s Error: 17120, Severity: 16, State: 1. 2025-07-02 11:59:12.96 spid36s 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.