SQL Server could not generate a solution for FRUNCM threads _mssql

SQL Server could not generate a FRUNCM thread. The database error log is as follows:

Copy Code code as follows:

2013-09-26 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)

2013-09-26 21:21:50.31 Server (c) is Microsoft Corporation.
2013-09-26 21:21:50.31 Server All rights reserved.
2013-09-26 21:21:50.31 Server server process ID is 2680.
2013-09-26 21:21:50.31 Server Logging SQL Server messages in file ' C:\Program Files\Microsoft SQL Server\mssql.1\mssq L\log\errorlog '.
2013-09-26 21:21:50.31 Server This instance the SQL Server last reported using a process ID of 2884 at 2013-9-26 21:20 : Wuyi (local) 2013-9-26 13:20:51 (UTC). This is a 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
2013-09-26 21:21:50.32 Server SQL server is starting at normal priority base (=7). This is a informational message only. No user action is required.
2013-09-26 21:21:50.32 Server detected 2 CPUs. This is a informational message; No user action is required.
2013-09-26 21:21:50.37 Server Set AWE Enabled to 1 in the configuration parameters to allow use of the more memory.
2013-09-26 21:21:50.49 Server Using dynamic lock allocation.  Initial allocation of 2500 lock blocks and 5000 lock Owner blocks per node.  This is a informational message only. No user action is required.
2013-09-26 21:21:50.53 Server attempting to initialize Microsoft distributed Transaction Coordinator (MS DTC). This is a informational message only. No user action is required.
2013-09-26 21:21:52.54 Server attempting to recover In-doubt distributed transactions involving Microsoft distributed Transaction Coordinator (MS DTC). This is a informational message only. No user action is required.
2013-09-26 21:21:52.54 Server Database Mirroring transport is disabled 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 '.
2013-09-26 21:21:52.81 spid5s Server name is ' SHGS1653 '. This is a 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.
2013-09-26 21:21:53.10 Server A self-generated certificate is successfully loaded for encryption.
2013-09-26 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.
2013-09-26 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.
2013-09-26 21:21:53.10 Server error: 17826, severity: 18, Status: 3.
2013-09-26 21:21:53.10 Server could not start the network library because of a internal error in the network library . To determine the cause, review the errors immediately preceding this one in the error log.
2013-09-26 21:21:53.10 Server error: 17120, severity: 16, Status: 1.
2013-09-26 21:21:53.10 Server SQL server could not spawn FRUNCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

Solution:

The analysis is due to the fact that some special changes have led to the activation of the VIA protocol in the SQL SERVER2005 Database network protocol, and that the protocol is closed.
SQL Server Configuration Manager-------The SQL Server 2005 Network configuration------MSSQLSERVER protocol, which is said to be disabled by the VIA protocol.