TDSSNIClient 初始化失败，出现错误 0x7e，状态代码 0x60。

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.