[SQL] Event ID 17120 17826 17182 26014에 대한 조치법 ~ Learning, Sharing, and Being Updated.

Sunday, July 16, 2017

[SQL] Event ID 17120 17826 17182 26014에 대한 조치법

onehundredpanda No comments

DB서버1의 Hostname을 A-->B로 rename하고 DB서버2를 신규로 구축해서 A라는 이름으로 하여 DB를 이관하였는데, 아래와 같은 메시지가 발생하였다. 한개도 아니고;;;

발생한 이벤트 메시지를 확인해보면, 함께 발생한 이벤트 메시지간의 연관성이 크게 보이지 않지만 원인은 하나 때문에 발생한다고 한다.

Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17182
Description: TDSSNIClient initialization failed with error 0x34, status code 0x1e.

Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17826
Description: Could not start the network library because of an internal error in the network library.

Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17120
Description: SQL Server could not spawn FRunCM thread.

Event ID 26014: Unable to load user-specified certificate [Cert Hash(sha1) “D3D88810B87C9533AA30CE9B2C3BDCEE3C674B97”]. 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.

Event ID 17182: TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property.

Event ID 17182: 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.

Event ID 17826: 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.

Event ID 17120: SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.