Skip to main content
Database Administrators

Return to Question

Post Closed as "Needs details or clarity" by John K. N., mustaccio, ypercubeᵀᴹ, LowlyDBA - John M, McNets
Tweeted twitter.com/#!/StackDBAs/status/490015151865987072
code format, tags
Source Link
edit approved Jul 18, 2014 at 2:24
jynus
edit approved Jul 18, 2014 at 2:24
jynus
  • 15k
  • 1
  • 37
  • 46

2014-07-17 16:31:16.00 spid14s Error: 17190, Severity: 16, State: 1. 2014-07-17 16:31:16.00 spid14s Initializing the FallBack certificate failed with error code: 1, state: 20, error number: 0. 2014-07-17 16:31:16.00 spid14s Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate. 2014-07-17 16:31:16.00 spid7s Starting up database 'msdb'. 2014-07-17 16:31:16.01 spid12s Starting up database 'mssqlsystemresource'. 2014-07-17 16:31:16.01 spid14s Error: 17182, Severity: 16, State: 1. 2014-07-17 16:31:16.01 spid14s TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property. 2014-07-17 16:31:16.01 spid14s Error: 17182, Severity: 16, State: 1. 2014-07-17 16:31:16.01 spid14s 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. 2014-07-17 16:31:16.01 spid14s Error: 17826, Severity: 18, State: 3. 2014-07-17 16:31:16.01 spid14s 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. 2014-07-17 16:31:16.01 spid14s Error: 17120, Severity: 16, State: 1. 2014-07-17 16:31:16.01 spid14s SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

2014-07-17 16:31:16.00 spid14s     Error: 17190, Severity: 16, State: 1.
2014-07-17 16:31:16.00 spid14s     Initializing the FallBack certificate failed with error code: 1, state: 20, error number: 0.
2014-07-17 16:31:16.00 spid14s     Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
2014-07-17 16:31:16.00 spid7s      Starting up database 'msdb'.
2014-07-17 16:31:16.01 spid12s     Starting up database 'mssqlsystemresource'.
2014-07-17 16:31:16.01 spid14s     Error: 17182, Severity: 16, State: 1.
2014-07-17 16:31:16.01 spid14s     TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property. 
2014-07-17 16:31:16.01 spid14s     Error: 17182, Severity: 16, State: 1.
2014-07-17 16:31:16.01 spid14s     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. 
2014-07-17 16:31:16.01 spid14s     Error: 17826, Severity: 18, State: 3.
2014-07-17 16:31:16.01 spid14s     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.
2014-07-17 16:31:16.01 spid14s     Error: 17120, Severity: 16, State: 1.
2014-07-17 16:31:16.01 spid14s     SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

2014-07-17 16:31:16.00 spid14s Error: 17190, Severity: 16, State: 1. 2014-07-17 16:31:16.00 spid14s Initializing the FallBack certificate failed with error code: 1, state: 20, error number: 0. 2014-07-17 16:31:16.00 spid14s Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate. 2014-07-17 16:31:16.00 spid7s Starting up database 'msdb'. 2014-07-17 16:31:16.01 spid12s Starting up database 'mssqlsystemresource'. 2014-07-17 16:31:16.01 spid14s Error: 17182, Severity: 16, State: 1. 2014-07-17 16:31:16.01 spid14s TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property. 2014-07-17 16:31:16.01 spid14s Error: 17182, Severity: 16, State: 1. 2014-07-17 16:31:16.01 spid14s 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. 2014-07-17 16:31:16.01 spid14s Error: 17826, Severity: 18, State: 3. 2014-07-17 16:31:16.01 spid14s 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. 2014-07-17 16:31:16.01 spid14s Error: 17120, Severity: 16, State: 1. 2014-07-17 16:31:16.01 spid14s SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

2014-07-17 16:31:16.00 spid14s     Error: 17190, Severity: 16, State: 1.
2014-07-17 16:31:16.00 spid14s     Initializing the FallBack certificate failed with error code: 1, state: 20, error number: 0.
2014-07-17 16:31:16.00 spid14s     Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
2014-07-17 16:31:16.00 spid7s      Starting up database 'msdb'.
2014-07-17 16:31:16.01 spid12s     Starting up database 'mssqlsystemresource'.
2014-07-17 16:31:16.01 spid14s     Error: 17182, Severity: 16, State: 1.
2014-07-17 16:31:16.01 spid14s     TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property. 
2014-07-17 16:31:16.01 spid14s     Error: 17182, Severity: 16, State: 1.
2014-07-17 16:31:16.01 spid14s     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. 
2014-07-17 16:31:16.01 spid14s     Error: 17826, Severity: 18, State: 3.
2014-07-17 16:31:16.01 spid14s     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.
2014-07-17 16:31:16.01 spid14s     Error: 17120, Severity: 16, State: 1.
2014-07-17 16:31:16.01 spid14s     SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
Source Link
user43965
user43965
  • 169
  • 1
  • 1
  • 3

Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes

I try installing SQL2008R2 - SQL2012 - sql2014

2014-07-17 16:31:16.00 spid14s Error: 17190, Severity: 16, State: 1. 2014-07-17 16:31:16.00 spid14s Initializing the FallBack certificate failed with error code: 1, state: 20, error number: 0. 2014-07-17 16:31:16.00 spid14s Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate. 2014-07-17 16:31:16.00 spid7s Starting up database 'msdb'. 2014-07-17 16:31:16.01 spid12s Starting up database 'mssqlsystemresource'. 2014-07-17 16:31:16.01 spid14s Error: 17182, Severity: 16, State: 1. 2014-07-17 16:31:16.01 spid14s TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property. 2014-07-17 16:31:16.01 spid14s Error: 17182, Severity: 16, State: 1. 2014-07-17 16:31:16.01 spid14s 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. 2014-07-17 16:31:16.01 spid14s Error: 17826, Severity: 18, State: 3. 2014-07-17 16:31:16.01 spid14s 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. 2014-07-17 16:31:16.01 spid14s Error: 17120, Severity: 16, State: 1. 2014-07-17 16:31:16.01 spid14s SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.