I tried installing SQL2012 and
encountered a failure with the below messages in the Summary file in folder
C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\
Detailed results:
Feature:
Database Engine Services
Status:
Failed: see logs for details
Reason for failure:
An error occurred during the setup process of the feature.
Next Step:
Use the following information to resolve the error,
uninstall this feature, and then run the setup process again.
Component name:
SQL Server Database Engine Services Instance Features
Component error code:
0x851A001A
Error description:
Wait on the Database Engine recovery handle failed. Check the SQL Server error
log for potential causes.
I looked at the Event Viewer to see what caused it and noticed the
below messages logged in there:
The server was unable to initialize encryption because of a problem
with a security library. The security library may be missing. Verify that
security.dll exists on the system.
TDSSNIClient initialization failed with error 0x139f, status code
0x80. Reason: Unable to initialize SSL support. The group or resource is not in
the correct state to perform the requested operation.
TDSSNIClient initialization failed with error 0x139f, status code
0x1. Reason: Initialization failed with an infrastructure error. Check for
previous errors. The group or resource is not in the correct state to perform
the requested operation.
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.
SQL Server could not spawn FRunCommunicationsManager thread. Check
the SQL Server error log and the Windows event logs for information about
possible related problems.
I installed SQL 2012 with the same setup file before successfully,
but this time it failed. I tried to figure out what changed recently in the
company and remembered that TLS 1.0 and SSL 3.0 protocols were disabled (because of known security vulnerabilities) on
all the servers and newer version of TLS & SSL was enabled which is TLS 1.1/1.2 . Disabling those protocols will cause problems in SQL Install process. This issue is addressed in CU1 (after SP3) of SQL 2012.
To resolve this, I had go enable the registry keys of the older SSL 3.0 (which is TLS 1.0, Microsoft renamed SSL 3.0 as TLS 1.0) as indicated below
HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Client:
After I modified the registrly keys, the SQL Install completed successfully. After the install is complete, make sure you patch it with SP3+CU1. At that point you can modify the registry keys back to normal.
HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL.3.0\Client:
Right–click on DisabledByDefault, click on
Modify and enter the value 0 (hexadecimal)
Right click on 'Enabled', click on Modify and
enter the value 1 (hexadecimal).
HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL.3.0\Server:
Right–click on DisabledByDefault, click on
Modify and enter the value 0 (hexadecimal)
Right click on 'Enabled', click on Modify and
enter the value ffffffff (hexadecimal).
HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Client:
Right–click on DisabledByDefault, click on
Modify and enter the value 0 (hexadecimal)
Right click on 'Enabled', click on Modify and
enter the value 1 (hexadecimal).
HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS
1.0\Server:
Right–click on DisabledByDefault, click on
Modify and enter the value 0 (hexadecimal)
Right click on 'Enabled', click on Modify and
enter the value ffffffff (hexadecimal).
After I modified the registrly keys, the SQL Install completed successfully. After the install is complete, make sure you patch it with SP3+CU1. At that point you can modify the registry keys back to normal.
