Delete the user profile if it existing twice.

Use other service accounts for the services.

Extract the ISO file instead to mount them.

Ok my first approach was to googling around. Check the SQL Server error log and the Windows event logs for information about possible related problems. 14:00:34.44 spid15s SQL Server could not spawn FRunCommunicationsManager thread. To determine the cause, review the errors immediately preceding this one in the error log. 14:00:34.44 spid15s Could not start the network library because of an internal error in the network library. Reason: Initialization failed with an infrastructure error. 14:00:34.44 spid15s TDSSNIClient initialization failed with error 0x80092004, status code 0x1. Reason: Unable to initialize SSL support. 14:00:34.43 spid15s TDSSNIClient initialization failed with error 0x80092004, status code 0x80. 14:00:34.43 spid15s Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate. 14:00:34.43 spid15s Initializing the FallBack certificate failed with error code: 1, state: 20, error number: 0. I looked into the service Dump Directory for the error log. The database engine wasn’t even able to start and the SQL service sqlservr.exe timed out. Reason for failure: An error occurred during the setup process of the feature.įeature: Full-Text and Semantic Extractions for Search

Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.Ĭomponent name: SQL Server Database Engine Services Instance FeaturesĮrror description: Could not find the Database Engine startup handle. Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail. Full-Text and Semantic Extractions for Search.The consequence, couple of services with the status failed, wasn’t installed: The SQL Server 2014 installer finished with the error message “Could not find the Database Engine startup handle”. I’m not sure if this have something to do with the Windows 8.1 Update but the reality is that I wasn’t able to install SQL Server 2014 on my machine after the Windows 8.1 Update.

Sql server 2014 express download stuck