| 
	SQL Server服務無法啟動時,時常會遇到以下提示:  
	本地計算機上的MSSQLSERVER服務啟動后又停止了。一些服務自動停止,如果它們沒有什么可做的,例如“性能日志和警報”服務。  
	您可以打開“計算機管理”下的“事件查看器”,您會發(fā)現如下圖中所示錯誤:  
	這時您可以檢查日志文件C:/Program Files/Microsoft SQL 
Server/MSSQL.1/MSSQL/LOG/ERRORLOG文件,用文本工具打開后,您會發(fā)現類似如下的內容:2009-06-14 
09:14:55.56 Server      Microsoft SQL Server 2005 - 9.00.1399.06 (Intel 
X86)  
	Oct 14 2005 00:33:37  
	Copyright (c) 1988-2005 Microsoft Corporation  
	Developer Edition on Windows NT 5.2 (Build 3790: Service Pack 2)  
	2009-06-14 09:14:55.56 Server      (c) 2005 Microsoft Corporation.  
	2009-06-14 09:14:55.56 Server      All rights reserved.  
	2009-06-14 09:14:55.56 Server      Server process ID is 4360.  
	2009-06-14 09:14:55.56 Server      Logging SQL Server messages in file 
'D:/Program Files/Microsoft SQL Server/MSSQL.1/MSSQL/LOG/ERRORLOG'.  
	2009-06-14 09:14:55.56 Server      This instance of SQL Server last 
reported using a process ID of 804 at 2009-6-14 9:13:30 (local) 
2009-6-14 1:13:30 (UTC). This is an informational message only; no user 
action is required.  
	2009-06-14 09:14:55.56 Server      Registry startup parameters:  
	2009-06-14 09:14:55.56 Server      -d D:/Program Files/Microsoft SQL Server/MSSQL.1/MSSQL/DATA/master.mdf  
	2009-06-14 09:14:55.56 Server      -e D:/Program Files/Microsoft SQL Server/MSSQL.1/MSSQL/LOG/ERRORLOG  
	2009-06-14 09:14:55.56 Server      -l D:/Program Files/Microsoft SQL Server/MSSQL.1/MSSQL/DATA/mastlog.ldf  
	2009-06-14 09:14:55.59 服務器         SQL Server is starting at normal 
priority base (=7). This is an informational message only. No user 
action is required.  
	2009-06-14 09:14:55.59 服務器         Detected 2 CPUs. This is an informational message; no user action is required.  
	2009-06-14 09:14:55.64 服務器         Set AWE Enabled to 1 in the configuration parameters to allow use of more memory.  
	2009-06-14 09:14:55.90 服務器         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.  
	2009-06-14 09:14:55.95 服務器         Attempting to initialize Microsoft 
Distributed Transaction Coordinator (MS DTC). This is an informational 
message only. No user action is required.  
	2009-06-14 09:14:56.01 服務器         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.  
	2009-06-14 09:14:56.01 服務器         Database Mirroring Transport is disabled in the endpoint configuration.  
	2009-06-14 09:14:56.03 spid5s      Starting up database 'master'.  
	2009-06-14 09:14:56.20 spid5s      SQL Trace ID 1 was started by login "sa".  
	2009-06-14 09:14:56.20 spid5s      Starting up database 'mssqlsystemresource'.  
	2009-06-14 09:14:56.42 spid5s      Server name is 'HMSNJZGDY0APZRZ'. 
This is an informational message only. No user action is required.  
	2009-06-14 09:14:56.42 spid9s      Starting up database 'model'.  
	2009-06-14 09:14:56.42 服務器         錯誤: 17182,嚴重性: 16,狀態(tài): 1。  
	2009-06-14 09:14:56.42 服務器         TDSSNIClient initialization failed with error 0xd, status code 0x10.  
	2009-06-14 09:14:56.42 服務器         錯誤: 17182,嚴重性: 16,狀態(tài): 1。  
	2009-06-14 09:14:56.42 服務器         TDSSNIClient initialization failed with error 0xd, status code 0x1.  
	2009-06-14 09:14:56.42 服務器         錯誤: 17826,嚴重性: 18,狀態(tài): 3。  
	2009-06-14 09:14:56.42 服務器         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.  
	2009-06-14 09:14:56.42 服務器         錯誤: 17120,嚴重性: 16,狀態(tài): 1。  
	2009-06-14 09:14:56.42 服務器         SQL Server could not spawn FRunCM 
thread. Check the SQL Server error log and the Windows event logs for 
information about possible related problems.  
	這時,不難看出:  
	TDSSNIClient initialization failed :TDSSNIClient 初始化失敗。  
	SQL Server could not spawn FRunCM thread :無法生成FRunCM 線程。  
	我們可以判定,可能會是以下問題,分別處理如下:  
	1、可能是IP地址配置不對。解決方法如下:  
	打開 /Microsoft SQL Server 2005/配置工具/下的SQL Server Configuration Manager,選擇mssqlserver協(xié)議, 然后雙擊右邊窗口的TCP/IP,在彈出窗口中檢查IP配置。  
	
一般來講,默認的IP2是:127.0.0.1,如果第一個IP地址的端口1433端口ping不通的話,服務無法啟動。您可以將127.0.0.1放在
IP1上,那么不管IP2的端口是否能ping通,服務都能夠正常啟動。您也可以將IP1設置為當前機器的IP地址,并保證該IP地址的端口能夠ping
通。  
	2、可能是因為VIA協(xié)議啟用造成的。解決方法如下:  
	打開 /Microsoft SQL Server 2005/配置工具/下的SQL Server Configuration 
Manager,選擇mssqlserver協(xié)議, 
然后右邊窗口有個VIA,點擊右鍵禁用它,點擊“確定”即可。這時候再啟動sqlserver服務即可!  
	另外,管理員密碼修改也會造成sqlserver服務無法啟動。解決方法如下:  
	打開 /Microsoft SQL Server 2005/配置工具/下的SQL Server Configuration Manager,打開SQL Server屬性,如下圖所示:  
	將本帳戶的密碼修改為您更改之后的管理員密碼,“確定”即可。這時SQL Server服務應該就能正常啟動了。  
	最后需要補充說明的是:我的機器在安裝時沒有使用默認實例,而是用的“EHR”這個實例名,因此,截圖可能會與您看到的不太一樣。沒有關系,道理都是一樣的。 | 
|  |