SQL Server 無法生成 FRunCM 線程。請查看 SQL Server 錯誤日誌和 Windows 事件日誌，獲取有關可能發生的相關問題的信息
服務services.msc中啓動SQLSERVER服務，提示啓動了又自動停止的現象，查了半天結果是被人修改了網絡協議，VIA本身要禁用的哦……
SQL Server Startup Issue related to TDSSNIClient error 0x7e status 0x60
Just thought I would jot down some interesting information I ran across while trying troubleshoot securing down SQL Server 2005.
Symptoms:
TDSSNIClient initialization failed with error 0x7e, status code 0x60.
TDSSNIClient initialization failed with error 0x7e, status code 0x1.
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.
SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
Problem:
If you inadvertantly enable the VIA protocol (even though it is last in the order) without the proper configuration SQL Server will not load at all. In my situation I did not need the VIA protocol so disabling it fixed the problem above, or should I say stopped the errors from occuring since no need to load the protocol. By default (at least in my installation) it is not enabled by default.