Even though the database server is not under our support, we were pulled to support

the database services during outage.

We assisted and resolved the issue by working with Wintel, SSCM and other teams.

During the problem identification and resolution we noticed service restart errors
and we noticed the same errors earlier also. Below given are the errors and
resolution.

Errors:

TDSSNIClient initialization failed with error 0x80090331, status code 0x80. Reason:
Unable to initialize SSL support. The client and server cannot communicate, because
they do not possess a common algorithm.

TDSSNIClient initialization failed with error 0x80090331, status code 0x1. Reason:
Initialization failed with an infrastructure error. Check for previous errors. The
client and server cannot communicate, because they do not possess a common
algorithm.

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.

SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the
Windows event logs for information about possible related problems.

Resolution:

HKLM => SYSTEM => CurrentControlSet => Control => SecurityProviders => SCHANNEL =>
Protocols => TLS 1.0 => Server => Change Enabled to 1