Solution for SQL Server failure to generate FRunCM thread

SQL Server cannot generate FRunCM threads. The Database Error Log is as follows:

Copy codeThe Code is as follows:
21:21:50. 31 Server Microsoft SQL Server 2005-9.00.1399.06 (Intel X86)
Oct 14 2005 00:33:37
Copyright (c) 1988-2005 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 2)

21:21:50. 31 Server (c) 2005 Microsoft Corporation.
2013-09-26 21:21:50. 31 Server All rights reserved.
2013-09-26 21:21:50. 31 Server process ID is 2680.
21:21:50. 31 Server Logging SQL Server messages in file 'C: \ Program Files \ Microsoft SQL Server \ MSSQL.1 \ MSSQL \ LOG \ errorlog '.
21:21:50. 31 Server This instance of SQL Server last reported using a process ID of 2884 at 21:20:51 (local) 13:20:51 (UTC ). this is an informational message only; no user action is required.
2013-09-26 21:21:50. 31 Server Registry startup parameters:
2013-09-26 21:21:50. 31 Server-d C: \ Program Files \ Microsoft SQL Server \ MSSQL.1 \ MSSQL \ DATA \ master. mdf
2013-09-26 21:21:50. 31 Server-e C: \ Program Files \ Microsoft SQL Server \ MSSQL.1 \ MSSQL \ LOG \ ERRORLOG
2013-09-26 21:21:50. 31 Server-l C: \ Program Files \ Microsoft SQL Server \ MSSQL.1 \ MSSQL \ DATA \ mastlog. ldf
21:21:50. 32 Server SQL Server is starting at normal priority base (= 7). This is an informational message only. No user action is required.
2013-09-26 21:21:50. 32 server Detected 2 CPUs. This is an informational message; no user action is required.
21:21:50. 37 server Set AWE Enabled to 1 in the configuration parameters to allow use of more memory.
21:21:50. 49 server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
21:21:50. 53 server Attempting to initialize Microsoft Distributed Transaction Coordinator (ms dtc). This is an informational message only. No user action is required.
21:21:52. 54 server Attempting to recover in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (ms dtc). This is an informational message only. No user action is required.
21:21:52. 54 Server Database Authentication ing Transport is disabled in the endpoint configuration.
2013-09-26 21:21:52. 54 spid5s Starting up database 'master '.
2013-09-26 21:21:52. 68 spid5s Starting up database 'mssqlsystemresource '.
21:21:52. 81 spid5s Server name is 'gs1653'. This is an informational message only. No user action is required.
2013-09-26 21:21:52. 82 spid8s Starting up database 'model '.
2013-09-26 21:21:52. 93 spid8s Clearing tempdb database.
21:21:53. 10 server A self-generated certificate was successfully loaded for encryption.
21:21:53. 10 server error: 17182, severity: 16, status: 1.
2013-09-26 21:21:53. 10 server TDSSNIClient initialization failed with error 0x7e, status code 0x60.
21:21:53. 10 server error: 17182, severity: 16, status: 1.
2013-09-26 21:21:53. 10 server TDSSNIClient initialization failed with error 0x7e, status code 0x1.
21:21:53. 10 server error: 17826, severity: 18, status: 3.
21:21:53. 10 server cocould 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.
21:21:53. 10 server error: 17120, severity: 16, status: 1.
21:21:53. 10 Server SQL Server cocould not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

Solution:

Some special changes have led to the enabling of the VIA protocol in the SQL SERVER2005 database network protocol.
SQL Server Configuration Manager ------- SQL Server 2005 network Configuration ------ MSSQLSERVER protocol. Disable the VIA protocol.