SQL服務器服務無法啓動

Question

我一直在嘗試從最近12小時啓動sql服務器，但不太清楚發生了什麼。我得到了錯誤1814這是'tempdb'不足夠的空間'，但我有60GB的數據在C：驅動器。此外，它試圖從E：驅動器打開這是我的DVD驅動器，這是不應該發生的表。

這裏通過添加日誌。請讓我知道最新的錯誤。

2012-12-26 12:24:06.34 Server  Microsoft SQL Server 2008 (SP1) - 10.0.2531.0 (Intel X86) 
Mar 29 2009 10:27:29 
Copyright (c) 1988-2008 Microsoft Corporation 
Express Edition on Windows NT 6.1 <X86> (Build 7601: Service Pack 1) 

2012-12-26 12:24:06.34 Server  (c) 2005 Microsoft Corporation. 
2012-12-26 12:24:06.34 Server  All rights reserved. 
2012-12-26 12:24:06.34 Server  Server process ID is 3456. 
2012-12-26 12:24:06.34 Server  System Manufacturer: 'WIPRO', System Model: 'WNB7PBM4930R-0007'. 
2012-12-26 12:24:06.34 Server  Authentication mode is WINDOWS-ONLY. 
2012-12-26 12:24:06.34 Server  Logging SQL Server messages in file 'c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\Log\ERRORLOG'. 
2012-12-26 12:24:06.34 Server  This instance of SQL Server last reported using a process ID of 5716 at 12/26/2012 12:15:10 PM (local) 12/26/2012 6:45:10 AM (UTC). This is an informational message only; no user action is required. 
2012-12-26 12:24:06.34 Server  Registry startup parameters: 
-d c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\DATA\master.mdf 
-e c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\Log\ERRORLOG 
-l c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\DATA\mastlog.ldf 
2012-12-26 12:24:06.36 Server  SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required. 
2012-12-26 12:24:06.36 Server  Detected 2 CPUs. This is an informational message; no user action is required. 
2012-12-26 12:24:06.41 Server  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. 
2012-12-26 12:24:06.48 Server  Node configuration: node 0: CPU mask: 0x00000003 Active CPU mask: 0x00000003. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required. 
2012-12-26 12:24:06.50 spid6s  Starting up database 'master'. 
2012-12-26 12:24:06.62 spid6s  FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SQLEXPRESS'. 
2012-12-26 12:24:06.65 spid6s  SQL Trace ID 1 was started by login "sa". 
2012-12-26 12:24:06.65 spid6s  Starting up database 'mssqlsystemresource'. 
2012-12-26 12:24:06.66 spid6s  The resource database build version is 10.00.2531. This is an informational message only. No user action is required. 
2012-12-26 12:24:06.91 spid6s  Server name is 'L--COMPUTER\SQLEXPRESS'. This is an informational message only. No user action is required. 
2012-12-26 12:24:06.91 spid10s  Starting up database 'model'. 
2012-12-26 12:24:06.91 spid6s  Informational: No full-text supported languages found. 
2012-12-26 12:24:06.91 spid6s  Starting up database 'msdb'. 
2012-12-26 12:24:07.19 spid10s  Error: 17204, Severity: 16, State: 1. 
2012-12-26 12:24:07.19 spid10s  FCB::Open failed: Could not open file e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\model.mdf for file number 1. OS error: 21(The device is not ready.). 
2012-12-26 12:24:07.19 spid10s  Error: 5120, Severity: 16, State: 101. 
2012-12-26 12:24:07.19 spid10s  Unable to open the physical file "e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\model.mdf". Operating system error 21: "21(The device is not ready.)". 
2012-12-26 12:24:07.20 spid6s  Error: 17204, Severity: 16, State: 1. 
2012-12-26 12:24:07.20 spid6s  FCB::Open failed: Could not open file e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\MSDBData.mdf for file number 1. OS error: 21(The device is not ready.). 
2012-12-26 12:24:07.20 spid6s  Error: 5120, Severity: 16, State: 101. 
2012-12-26 12:24:07.20 spid6s  Unable to open the physical file "e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\MSDBData.mdf". Operating system error 21: "21(The device is not ready.)". 
2012-12-26 12:24:07.20 Server  A self-generated certificate was successfully loaded for encryption. 
2012-12-26 12:24:07.20 Server  Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQLEXPRESS ]. 
2012-12-26 12:24:07.20 Server  Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$SQLEXPRESS\sql\query ]. 
2012-12-26 12:24:07.20 Server  Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag 7806. This is an informational message only. No user action is required. 
2012-12-26 12:24:07.22 Server  The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies. 
2012-12-26 12:24:07.22 Server  SQL Server is now ready for client connections. This is an informational message; no user action is required. 
2012-12-26 12:24:07.45 spid10s  Error: 17207, Severity: 16, State: 1. 
2012-12-26 12:24:07.45 spid10s  FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\modellog.ldf'. Diagnose and correct the operating system error, and retry the operation. 
2012-12-26 12:24:07.45 spid10s  File activation failure. The physical file name "e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\modellog.ldf" may be incorrect. 
2012-12-26 12:24:07.45 spid10s  Error: 945, Severity: 14, State: 2. 
2012-12-26 12:24:07.45 spid10s  Database 'model' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details. 
2012-12-26 12:24:07.45 spid10s  Could not create tempdb. You may not have enough disk space available. Free additional disk space by deleting other files on the tempdb drive and then restart SQL Server. Check for additional errors in the event log that may indicate why the tempdb files could not be initialized. 
2012-12-26 12:24:07.45 spid10s  SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required. 
2012-12-26 12:24:07.45 spid6s  Error: 17207, Severity: 16, State: 1. 
2012-12-26 12:24:07.45 spid6s  FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\MSDBLog.ldf'. Diagnose and correct the operating system error, and retry the operation. 
2012-12-26 12:24:07.48 spid6s  File activation failure. The physical file name "e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\MSDBLog.ldf" may be incorrect. 

Answer 1

看看這些鏈接：

• http://social.msdn.microsoft.com/Forums/en-US/sqldatabaseengine/thread/922fe202-a2a8-47e4-8f77-402ef14944f8/

• http://blogs.msdn.com/b/sanchan/archive/2006/06/04/617585.aspx

1）確保您取消選中 「壓縮內容以便節省磁盤空間」文件tempdb.mdf

2）確保你是不節省tempdb中的壓縮文件夾

ALSO：

這是什麼錯誤：

e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\model.mdf

也許你想只取「模式「 離線？

Answer 2

我與SQL Express有同樣的問題。 MS SQL安裝程序非常麻煩。有幾次我進入了需要重新安裝操作系統的情況。對於這個特定的問題，解決方案在這裏：https://social.technet.microsoft.com/wiki/contents/articles/31786.sql-server-not-starting-after-fresh-installation.aspx。

基本位是：

SQLCMD –S .\ 

或

：

使用下面的命令

NET START MSSQLSERVER /f /T3608 

執行命令行查詢處理器啓動命令行的服務

SQLCMD –S .\INSTANCENAME 

檢查路徑的數據庫：

SELECT name, physical_name, state_desc FROM sys.master_files ORDER BY database_id; 
go 

修復數據庫路徑：

ALTER DATABASE model MODIFY FILE (NAME = modeldev, FILENAME = 'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\model.mdf'); 
ALTER DATABASE model MODIFY FILE (NAME = modellog, FILENAME = 'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\modellog.ldf'); 
ALTER DATABASE msdb MODIFY FILE (NAME = MSDBData, FILENAME = 'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\MSDBData.mdf'); 
ALTER DATABASE msdb MODIFY FILE (NAME = MSDBLog, FILENAME = 'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\MSDBLog.ldf'); 
ALTER DATABASE tempdb MODIFY FILE (NAME = tempdev, FILENAME = 'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\temp.mdf'); 
ALTER DATABASE tempdb MODIFY FILE (NAME = templog, FILENAME = 'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\temp.ldf'); 
go 

退出並重新啓動服務：

exit 
NET STOP MSSQLSERVER 
NET START MSSQLSERVER