Hi,@Oskar Nowak
Found this in ERRORLOG.txt
2024-03-27 21:10:10.57 spid32s Error: 17190, Severity: 16, State: 1. 2024-03-27 21:10:10.57 spid32s Initializing the FallBack certificate failed with error code: 15, state: 29, error number: 2. 2024-03-27 21:10:10.57 spid32s Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
The above issue may be caused by two types of reasons:
- An invalid certificate.
- SQL Server is unable to access the specified certificate. To fix this issue ASAP .You may try to change the service account to an LocalService.
Refer tohttps://learn.microsoft.com/en-us/archive/msdn-technet-forums/56f14665-3f00-41ff-b002-bb5e86b3f219
Steps:
If the above is unable to resolve the issue, you can try the following method:
Configure SQL Server to use a self-signed certificate:
1.Open the Registry Editor and navigate to the following registry key (the registry path may vary slightly depending on the instance number):
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\MSSQLServer\SuperSocketNetLib\Certificate
2.Clear the value of the Certificate.
3.Open the Microsoft Management Console (MMC) and add the Certificate Management console. Delete all certificates in both the Local Computer certificate store and the Current User certificate store that have a subject field that matches the server hostname (before deleting, you may want to export the certificates as a backup for future use).
This should allow SQL Server to use a self-generated certificate in most cases.
Use the self-signed certificate automatically created by SQL Server
To check the certificate, you can refer to Microsoft's documentation on certificate requirements for SQL Server. Certificate requirements for SQL Server - SQL Server | Microsoft Learn
Best regards,
Mikey Qiao
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".