111,111
社区成员
发帖
与我相关
我的任务
分享SQL Server 2005 服务启动不了,怎么办？
以下是在事件查看器中的错误：
SQL Server 无法生成 FRunCM 线程。请查看 SQL Server 错误日志和 Windows 事件日志，获取有关可能发生的相关问题的信息。
由于网络库中存在内部错误，所以无法启动网络库。要确定原因，请查看错误日志中紧位于此错误之前的那些错误。
TDSSNIClient 初始化失败，出现错误 0x7e，状态代码 0x60。
...全文
请发表友善的回复…
发表回复
醉龍 2006-04-15
- 打赏
- 举报
引用
我说明吧：正式版本由于工作人员的失误，造成没有去掉Visual Studio® 2005 Beta 2 Setup的字样，但内容绝对是正式版本的东西，我这里正式版本的里面也有这个字样，咨询后，微软如是回复的。
我说VS2005那么多bug，原来是微软的工程师现在都这么粗心！
以前在别的论坛上看到的一个帖子
我说明吧：正式版本由于工作人员的失误，造成没有去掉Visual Studio® 2005 Beta 2 Setup的字样，但内容绝对是正式版本的东西，我这里正式版本的里面也有这个字样，咨询后，微软如是回复的。
我说VS2005那么多bug，原来是微软的工程师现在都这么粗心！
以前在别的论坛上看到的一个帖子
kingtsui 2006-04-15
- 打赏
- 举报
在SQL Server Configuration Manager里
SQl Server 2005网络配置， MSSQLSERVER的协议 里
把 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.
I hope this helps.
SQl Server 2005网络配置， MSSQLSERVER的协议 里
把 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.
I hope this helps.
孟子E章 2006-04-15
- 打赏
- 举报
在开始－Sql server 2005-配置工具－SQL Server Configuration Manager － sql协议－禁止VIA
孟子E章 2006-04-15
- 打赏
- 举报
Check what network protocols are enabled for SQL Server in the SQL Configuration Manager application. If the VIA protocol is enabled disable it and then try starting the SQL Server service again.
