MSSQLSERVER_17120
适用范围：
SQL Server
详细信息
| Attribute | 值 |
|---|---|
| 产品名称 | SQL Server |
| 事件 ID | 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 配置和更新问题 ：报告的另一个常见问题包括服务器上阻止 SQL Server 创建后台通信任务的 TLS 配置。
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。 有关所需的更新的信息，请参阅 TLS 1.2 对 Microsoft SQL Server 的支持
解决加密证书问题 的另一个常见问题是 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 服务在配置实例以使用安全套接字层证书后无法启动