MSSQLSERVER_17120
適用於：
SQL Server
詳細資料
| 屬性 | 值 |
|---|---|
| 產品名稱 | SQL Server |
| 事件識別碼 | 17120 |
| 事件來源 | MSSQLSERVER |
| 元件 | SQLEngine |
| 符號名稱 | INIT_SPAWN |
| 訊息文字 | SQL Server 無法繁衍 %s 執行緒。 如需可能相關問題的相關信息，請檢查 SQL Server 錯誤記錄檔和操作系統錯誤記錄檔。 |
說明
當執行系統或背景工作的線程無法建立時，就會引發錯誤 17120。 背景工作的範例包括檢查點、延遲寫入器、資料庫復原工作、記錄讀取器、記錄寫入器、自動壓縮工作、通訊管理員、平行重做背景工作工作等等。 %s錯誤中的 包含工作的名稱。 以下是此錯誤在錯誤記錄檔中顯示方式的範例：
Error: 17120, Severity: 16, State: 1.
SQL Server could not spawn checkpoint thread. Check the SQL Server error log and the operating system error log for information about possible related problems.
Error: 17120, Severity: 16, State: 1.
SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the operating system error log for information about possible related problems.
Error: 17120, Severity: 16, State: 1.
SQL Server could not spawn log writer thread. Check the SQL Server error log and the operating system error log for information about possible related problems.
原因
SQL Server 無法建立線程，讓背景工作開始執行。 常見的原因包括：
- 系統上或 SQL Server 內部可用的記憶體不足或無記憶體
- SQL Server 處於關機的中間
- SQL Server 是服務無法啟動，因為設定錯誤或資源問題
使用者動作
診斷其他錯誤，並在系統上重試作業。
記憶體不足問題： 開始調查的第一個步驟是檢查記憶體不足或記憶體不足的情況。 檢查系統事件記錄檔和 SQL 錯誤記錄檔。 如需如何進行疑難解答的資訊，請參閱 針對 SQL Server 中的記憶體不足或記憶體不足問題進行疑難解答
解決設定錯誤的通訊協定 回報的常見問題包括設定錯誤的 SQL Server 通訊協定。 如需詳細資訊，請參閱 SQL Server 無法在停用所有通訊協定時啟動。 您可能會在錯誤記錄檔中觀察到下列錯誤順序：
Error: 17182, Severity: 16, State: 1. TDSSNIClient initialization failed with error 0xd, status code 0x4. Reason: **All protocols are disabled. The data is invalid**. Error: 17182, Severity: 16, State: 1. TDSSNIClient initialization failed with error 0xd, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. The data is invalid. 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 operating system error log for information about possible related problems.解決 TLS 設定和更新問題 ：回報的另一個常見問題包括伺服器上的 TLS 設定，以防止 SQL Server 建立背景通訊工作。
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.請確定您已正確設定 SQL Server 的 TLS。 如需所需更新的資訊，請參閱 MICROSOFT SQL Server 的 TLS 1.2 支援
解決加密憑證問題 另一個常見問題是 TLS/SSL 憑證的設定錯誤，導致 SQL Server 無法啟動和啟動線程。
Error: 26014, Severity: 16, State: 1. Unable to load user-specified certificate [Cert Hash(sha1) "%hs"]. 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. Error: 17182, Severity: 16, State: 1. TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property. 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.如需詳細資訊，請參閱 將實例設定為使用安全套接字層憑證之後，SQL Server 服務無法啟動