Tdssniclient initialization failed with error 0x139f status code 0x80



Tdssniclient initialization failed with error 0x139f status code 0x80

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Asked by:

Question

Error: 26011, Severity: 16, State: 1.
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.

This node is patched identical to other Node. No issues (so far with other node). No issues after Spectre-Meltdown fix applied.

Currently SSL3.0, TLS 1.0, TLS 1.1 and TLS 1.2 all enabled. No certificates used so the links to cert thumb prints does not apply. Not a password or SQL Server Service account issue. Same domain account and password on working Node. Have rebooted server multiple times, yet no success when trying to fail the cluster over to this node.

Any directions or previously found solutions would be helpful.

Источник

Tdssniclient initialization failed with error 0x139f status code 0x80

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Asked by:

Question

Installed all patches below:

SQL 2012 Service Pack 1 SQL 2012 Service Pack 2 SQL 2012 Service Pack 3 SQL 2012 Service Pack 3 — Hotfix for TLS1.2 Still the SQL SERVER 2012 cannot start as per error below.

Читайте также:  Ansys error interpolating results onto the new mesh

A fatal error occurred while creating an SSL client credential. The internal error state is 10013. 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.

2018-07-12 11:16:25.10 spid10s The server could not load the certificate it needs to initiate an SSL connection. It returned the following error: 0x80090331. Check certificates to make sure they are valid. 2018-07-12 11:16:25.11 spid10s Error: 26014, Severity: 16, State: 1. 2018-07-12 11:16:25.11 spid10s Unable to load user-specified certificate [Cert Hash(sha1) «1E40ACCA7AB499E2967FE691A9FBCCAA39A122CC»]. The server will not accept a connection. You should verify that the certificate is correctly installed. See «Configuring Certificate for Use by SSL» in Books Online. 2018-07-12 11:16:25.11 spid10s Error: 17182, Severity: 16, State: 1. 2018-07-12 11:16:25.11 spid10s TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property. 2018-07-12 11:16:25.11 spid10s Error: 17182, Severity: 16, State: 1. 2018-07-12 11:16:25.11 spid10s 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. 2018-07-12 11:16:25.11 spid10s Error: 17826, Severity: 18, State: 3. 2018-07-12 11:16:25.11 spid10s 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. 2018-07-12 11:16:25.11 spid10s Error: 17120, Severity: 16, State: 1. 2018-07-12 11:16:25.11 spid10s SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems. Is there really a solution for this?

Читайте также:  Что означает error code 267

The SSL certificate is not the issue because when i enabled the TLS1.0. The server can start again.

Источник

Tdssniclient initialization failed with error 0x139f status code 0x80

Вопрос

we are getting below error while installing SQL server 2012 Enterprise edition on new windows 2012 server.

1) 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.

2) 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.

3) 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.

4) 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.

5) SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

Источник

Tdssniclient initialization failed with error 0x139f status code 0x80

Вопрос

we are getting below error while installing SQL server 2012 Enterprise edition on new windows 2012 server.

1) 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.

Читайте также:  Soring mbc 601 error

2) 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.

3) 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.

4) 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.

5) SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

Источник

Tdssniclient initialization failed with error 0x139f status code 0x80

Вопрос

we are getting below error while installing SQL server 2012 Enterprise edition on new windows 2012 server.

1) 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.

2) 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.

3) 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.

4) 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.

5) SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

Источник

Оцените статью
toolgir.ru
Adblock
detector