My name is Harsh Deep Singh, and I am a SQL Server Premier Field Engineer with Microsoft. I've been working on SQL Server for quite some time, and the intention behind starting this blog is to try and share my knowledge with the SQL Server community. Any feedback or suggestions on the blog are both welcome and solicited. Please feel free to drop me a line on email@example.com anytime.
Disclaimer: The information in this weblog is provided “AS IS” with no warranties, and confers no rights. This weblog does not represent the thoughts, intentions, plans or strategies of my employer. It is solely my opinion. Feel free to challenge me, disagree with me, or tell me I’m completely nuts in the comments section of each blog entry, but I reserve the right to delete any comment for any reason whatsoever (abusive, profane, rude, or anonymous comments) – so keep it polite, please.
You might run into this situation where SQL Server fails to come online (either with a new install or an existing one). Looking at the application event logs, you see these messages:
Event Type: Error
Event Source: MSSQLSERVER
Event Category: Server
Event ID: 17182
Time: 5:03:40 AM
TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property.
Event ID: 17190
FallBack certificate initialization failed with error code: 1.
As always, it’s a good idea to take a look at the SQL Errorlog. Looking in the errorlog, you might see these messages:
2012-05-08 05:10:13.14 Server Error: 17190, Severity: 16, State: 1.
2012-05-08 05:10:13.14 Server FallBack certificate initialization failed with error code: 1.
2012-05-08 05:10:13.14 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-05-08 05:10:13.16 Server Error: 17182, Severity: 16, State: 1.
2012-05-08 05:10:13.16 Server TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property.
2012-05-08 05:10:13.16 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.
This is another error that does not exactly point towards the actual cause of the problem. One might think, why is it not possible to create a self-signed certificate? The answer is that the certificate cannot be created because the user profile is corrupted. Here’s what you can do:
Workaround : Change the service account. If the new account’s profile on the server is not corrupted, the services will come online.
Solution: Delete the profile and recreate it. For details, please refer to the KB here
Hope this helps.