Symptom
• SQL Server Service failed to start
• SQL Server ERRORLOG shows error message like:
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.
Error: 17182, Severity: 16, State: 1.
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.
Error: 17182, Severity: 16, State: 1.
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.
Error: 17826, Severity: 18, State: 3.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.
Error: 17120, Severity: 16, State: 1.SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
Read more...
Environment
• SAP Systems based on SAP NetWeaver
• Microsoft SQL Server 2005 to SQL Server 2014
Product
Keywords
initialize encryption,17182,17826,17120,0x139f,0x80,SSl,FRunCommunicationsManager , KBA , BC-DB-MSS , SQL Server in SAP NetWeaver Products , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.