Yesterday on my local instance, SQL Server service failed to start. The SQL Server error log had the following entries in it.
2012-12-31 12:31:26.58 Server Error: 17190, Severity: 16, State: 1. 2012-12-31 12:31:26.58 Server Initializing the FallBack certificate failed with error code: 1, state: 1, error number: -2146893788. 2012-12-31 12:31:26.58 Server Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate. 2012-12-31 12:31:26.58 spid7s Informational: No full-text supported languages found. 2012-12-31 12:31:26.58 Server Error: 17182, Severity: 16, State: 1. 2012-12-31 12:31:26.58 Server TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property. 2012-12-31 12:31:26.58 Server Error: 17182, Severity: 16, State: 1. 2012-12-31 12:31:26.58 Server TDSSNIClient initialization failed with error 0x80092004, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Cannot find object or property. 2012-12-31 12:31:26.58 Server Error: 17826, Severity: 18, State: 3. 2012-12-31 12:31:26.58 Server 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. 2012-12-31 12:31:26.58 Server Error: 17120, Severity: 16, State: 1. 2012-12-31 12:31:26.58 Server SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
Before getting too much into the error details, I started to analyse what had changed since the last service/server restart. Here is what I had done the day before, to troubleshoot some other issue.
- Removed the Server from the domain and made it part of a workgroup
- After completing the desired tasks, I had made the server part of the domain again.
That’s all. The SQL Server service was configured to start using a domain account.
When I changed the SQL Server service account from the domain account to a local (built-in) account, the service started normally.
However, if I changed the service to start using a domain account the same error message would re-appear.
The following portion of the error message caught my attention.
TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property
SQL Server service is trying to intialize SSL support but it cannot find the requisite information. Like I mentioned earlier, the only thing that had changed on this instance was that the server was re-added to the domain. Did the permissions of the SQL Server service account have changed? No. I verified that the permissions were intact. Did something go wrong with the local profile of the Service account? Here is what I saw under the User Profiles (Computer Properties –> Advanced –> User Profiles)
The SQL Server service account had *two* profiles on this computer. One had the status of “Backup” whereas the other one had the status of “Temporary”. This was unusual because for any user who logs on to a computer, one local profile is created. The profile related files are created under C:\Users directory (on Windows 2003 server and below it is C:\Documents and Settings). In this case there was only one folder created but under User Profiles it was showing two. Since this seems to be an issue, I deleted the profile which had the status of “Backup”. After this In logged onto the system using the SQL Server service account to ensure that the there are no visible errors during the profile creation.
After this the SQL Server service started normally! Perfect way to end the year 2012 and I am welcoming the year 2013 with this blog post!