December 19, 2013 at 11:59 am
It turns out there is a big problem about the sqlserver engine service, It just don't start any more, with the error code 0x80092004. It's may related to some kind of SSL cetificate issues, but after searching for days , it just don't work. Can anyone help? Thank you in advance!
December 19, 2013 at 2:17 pm
Can you change the service account?
December 19, 2013 at 2:20 pm
Have a read through this, see if it helps or at least points you to more specific and useful error messages:
https://www.simple-talk.com/sql/backup-and-recovery/the-sql-server-instance-that-will-not-start/
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
December 20, 2013 at 6:00 am
Locate SQL's ERRORLOG text file, you'll be able to get the location from the service.
Have a look through it, there should be a more descriptive message in the log.
December 20, 2013 at 7:03 am
use this account: NT Service\MSSQLSERVER can not start sql server engine service, but the account: local system can. Its log:TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property.
and this: Initializing the FallBack certificate failed with error code: 1, state: 20, error number: 0.
and this: 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.
can anybody help, please, It's really dreadful!
December 20, 2013 at 7:06 am
Can you post the entire of one of the error logs that shows the errors?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
December 20, 2013 at 7:39 am
These are the logs:
2013-12-19 17:00:03.51 spid13s Error: 17190, Severity: 16, State: 1.
2013-12-19 17:00:03.51 spid13s Initializing the FallBack certificate failed with error code: 1, state: 20, error number: 0.
2013-12-19 17:00:03.62 spid13s Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
2013-12-19 17:00:03.68 spid13s Error: 17182, Severity: 16, State: 1.
2013-12-19 17:00:03.68 spid13s TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property.
2013-12-19 17:00:03.68 spid13s Error: 17182, Severity: 16, State: 1.
2013-12-19 17:00:03.68 spid13s 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.
2013-12-19 17:00:03.68 spid13s Error: 17826, Severity: 18, State: 3.
2013-12-19 17:00:03.68 spid13s 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.
2013-12-19 17:00:03.70 spid13s Error: 17120, Severity: 16, State: 1.
2013-12-19 17:00:03.70 spid13s SQL Server could not spawn
I can provide more if you want
December 20, 2013 at 10:11 am
Can you post the entire of one of the error logs please
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply