We have an issue while installing the Microsoft SQL Server 2014 and took us almost 5 hours to sort it out. So, the issue is we cannot bring up the SQL Server Agent service even though the SQL Server service is running fine.
From the error log location (C:\Program Files\Microsoft SQL Server\[SQL-VERSION]\MSSQL\Log, the trace file SQLAGENT gave us this,
Microsoft SQLServerAgent version 12.0.4419.0 (X64 unicode retail build) : Process ID 5264
The SQL Server Agent startup service account is ITSITI.
SQL Server does not accept the connection (error: 817). Waiting for Sql Server to allow connections. Operation attempted was: Verify Connection On Start.
Unable to connect to server '(local)'; SQLServerAgent cannot start
SQLServer Error: 21, Encryption not supported on the client. [SQLSTATE 08001]
SQLServer Error: 817, SSL Provider: The client and server cannot communicate, because they do not possess a common algorithm. [SQLSTATE 08001]
SQLServer Error: 21, Client unable to establish connection [SQLSTATE 08001]
SQLServer Error: 817, A network-related or instance-specific error has occurred while establishing a connection to SQL Server.
Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections.
For more information see SQL Server Books Online. [SQLSTATE 08001]
Logon to server '(local)' failed (DisableAgentXPs)
SQLServerAgent terminated (normally)
In the Windows Event Viewer,
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.
Solution
Refer to this Microsoft article, TLS 1.2 support for Microsoft SQL Server and perform the update based on current SQL server version installed.
Alternatively, you can perform the below workaround. But, updating the SQL server is always be the recommended way.
Open the Registry Editor and go to the below directory and ensure the DisabledByDefault and Enabled value as below for client and server.
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Client
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Server
Thank you for the article. Extremely useful