The server could not load the certificate Error 0x80090331
TDSSNIClient Initialization Failed with error
Dieser Fehler kann darauf hindeuten, das es ein Problem mit den TCP Einstellungen (SQL Server Network Configuration) geben könnte, oder der Fingerabdruck eines Zertifikats in der Registry enthält ein unsichtbares Zeichen.
HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\<instance>\MSSQLServer\SuperSocketNetLib
The server could not load the certificate Error 0x80090331
TDSSNIClient Initialization Failed with error
2021-11-15 15:18:42.80 spid31s The server could not load the certificate it needs to initiate an SSL connection. It returned the following error: 0x80090331. Check certificates to make sure they are valid.
2021-11-15 15:18:42.81 spid31s Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
2021-11-15 15:18:42.81 spid31s Error: 17182, Severity: 16, State: 1.
2021-11-15 15:18:42.81 spid31s 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.
2021-11-15 15:18:42.81 spid31s Error: 17182, Severity: 16, State: 1.
2021-11-15 15:18:42.81 spid31s 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.
2021-11-15 15:18:42.81 spid31s Error: 17826, Severity: 18, State: 3.
2021-11-15 15:18:42.81 spid31s 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.
2021-11-15 15:18:42.81 spid31s Error: 17120, Severity: 16, State: 1.
2021-11-15 15:18:42.81 spid31s 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.
Die Ausgangssituation ist ein installierter SQL Server 2019 unter Windows 10.
In diesem Fall lag es tatsächlich mal wieder an den TLS 1.2 Einstellungen innerhalb der Registry. und zwar war der Wert des Protocols auf = 0 gesetzt also disabled.
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Server]
„DisabledByDefault“=dword:00000000
„Enabled“=dword:00000001
Nach der Anpassung bzw. nach der Aktivierung von TLS 1.2 war der Fehler behoben und die SQL Server Dienste starteten wieder.
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Server]
„DisabledByDefault“=dword:00000000
„Enabled“=dword:00000001
Download TLS 1.2 Sammlung
