f SQL 2012 RTM安裝於WINDOWS 2012 所碰到的問題 ~ 迪貝之家

SQL 2012 RTM安裝於WINDOWS 2012 所碰到的問題

上個禮拜安裝碰到這個問題
原本以為是權限問題
local admin及目錄權限沒給cluster帳號
調整了之後
移除軟體後,重新安裝,還是沒解決
就只好去看了一下sql server的記錄
結果.......
2020-03-09 10:34:39.90 spid13s Error: 26011, Severity: 16, State: 1.
2020-03-09 10:34:39.90 spid13s 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.
2020-03-09 10:34:39.90 spid13s Error: 17182, Severity: 16, State: 1.
2020-03-09 10:34:39.90 spid13s 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.
2020-03-09 10:34:39.90 spid13s Error: 17182, Severity: 16, State: 1.
2020-03-09 10:34:39.90 spid13s 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.
2020-03-09 10:34:39.90 spid13s Error: 17826, Severity: 18, State: 3.
2020-03-09 10:34:39.90 spid13s 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.
2020-03-09 10:34:39.90 spid13s Error: 17120, Severity: 16, State: 1.
2020-03-09 10:34:39.90 spid13s SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
跟HP的外包溝通後
他說可能是TLS 1.0沒啟動的問題
這個時候, 其實我已經把問題丟到微軟去了
微軟的回覆:
TLS 1.0
接到這個回覆的時候
HP的外包已經調整完正在重開OS
調完當然就解了
微軟建議閱讀的有關TLS KM