SQL Server failed to start and throwing error – "The request failed or the service did not respond in timely fashion. Consult the event log or other applicable error logs for details."
I have tried the solution given here
I have tried multiple solutions but neither have worked\
- Tried to built-in account to Local System, Local Service and Network service.
- Reinstalled the SQL Server.
- Disabled the VIA in SQL Server network configuration.
Any solution to solve my problem?
Window 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.
- 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.
- 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.
- 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.
SQL Server error log:
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.
Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
Error: 17182, Severity: 16, State: 1.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.
Best Answer
When the server cannot start, the first thing to consult is
SQL Server error log
. There can be different reasons, for example, banally the port assigned is occupied. But in OP case it wasThe error message itself suggested what to do:
Another option in this case was to remove encryption at all if it was configured by mistake