| 2020-03-09 10:34:39.90 spid13s Error: 26011, Severity: 16, State: 1. |
| 2020-03-09 10:34:39.90 spid13s 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. |
| 2020-03-09 10:34:39.90 spid13s Error: 17182, Severity: 16, State: 1. |
| 2020-03-09 10:34:39.90 spid13s 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. |
| 2020-03-09 10:34:39.90 spid13s Error: 17182, Severity: 16, State: 1. |
| 2020-03-09 10:34:39.90 spid13s 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. |
| 2020-03-09 10:34:39.90 spid13s Error: 17826, Severity: 18, State: 3. |
| 2020-03-09 10:34:39.90 spid13s 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. |
| 2020-03-09 10:34:39.90 spid13s Error: 17120, Severity: 16, State: 1. |
| 2020-03-09 10:34:39.90 spid13s SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems. |
|
|
