Share via

Fail to start MSSQLSERVER 2016 service after windows server 2016 patch

TracyLiang 41 Reputation points
2022-04-16T04:13:17.89+00:00

Last night there is windows server 2016 patch installed, and then we found the mssqlserver 2016 service failed with error.

Now we have rollbacked the windows patch KB5012596, but the mssqlserver 2016 service still failed to start with bellow error:
Unable to load user-specified certificate [Cert Hash(sha1) "19A4C4FD63C459C802DC7FEBA8A0854CDF04EC2E"]. The server will not accept a connection. You should verify that the certificate is correctly installed. See "Configuring Certificate for Use by SSL" in Books Online.

Please kindly guide how to recover the service quickly. Many thanks!

Attachments:

  1. windows server 2016 patch:

2) MSSQLSERVER 2016 service failure error.
193581-event-log-error-2022-04-16-133341.jpg
3) Sql configuration management;
193469-sql-server-configuation-manager-2022-04-16-132120.jpg

SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
13,363 questions
0 comments
Accepted answer
  1. Erland Sommarskog 107.2K Reputation points
    2022-04-16T10:42:05.307+00:00

    I googled on "TDSSNIClient initialization failed with error 0x80092004, status code 0x80" and "Cannot find object or property." and found these links that may help you:

    https://learn.microsoft.com/en-us/troubleshoot/sql/security/service-cannot-start
    https://social.msdn.microsoft.com/Forums/sqlserver/en-US/63c15cb5-0d12-4ea8-bf84-e3ea8a42a866/regarding-the-sql-server-service-starting-problem?forum=sqldatabaseengine

5 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Erland Sommarskog 107.2K Reputation points
    2022-04-16T08:32:32.82+00:00

    My gut feeling is that this is a matter of registry corruption. The Windows patch is unlikely to have anything do with it - except that you had to restart the machine, whereupon the corruption started to hurt.

    I should immediately repeat that this is just gut feeling - or a guess, if you like. So don't run away to take actions based on this.

    One thing that would help would be to see the SQL Server errorlog. There can be errors there leading up to the final errors that can give more information.

    1 person found this answer helpful.
    0 comments
  2. TracyLiang 41 Reputation points
    2022-04-16T09:01:38.39+00:00

    @Erland: Thank you so much for your reply.
    I tried to start the MSSQLSERVER service and see the all error event logs as bellow, please kindly give your guide how to fix it. Many appreciations!
    193545-systemlogerror-20220416043834.png193566-systemlogerror-20220416043837.png193567-applicationlogerror-2022041604383601.png193546-applicationlogerror-2022041604383701.png193547-applicationlogerror-2022041604383702.png193548-applicationlogerror-2022041604383703.png193549-applicationlogerror-2022041604383704.png

  3. TracyLiang 41 Reputation points
    2022-04-16T09:46:39.027+00:00

    @Erland: Thank you. I have viewed SQL Server error log, and there are bellow error log files after patching of windows server 2016 ; obviously the problem still exists after rollbacking the patch.
    Please kindly guide how to fix it. Many appreciations!
    193592-sqlagent.txt193593-errorlog6.txt

    0 comments
  4. TracyLiang 41 Reputation points
    2022-04-16T12:44:58.3+00:00

    @Erland: Thank you so much. I checked the property in SQL Server Configuration Manager, the certificate is empty.
    193553-sqlserverconfigurationmanager-missingcertificate.png

    And I have chosen the server self-signed certificate to apply it and then restart still with error, the SQL Server error log is as bellows:
    193490-errorlog4.txt

    It seems that the certificate still has problem, please kindly guide it. Many appreciations!

    0 comments