Le service du server SQL ne démarre pas

J'ai essayé de démarrer le server SQL depuis les 12 dernières heures, mais je ne suis pas très sûr de ce qui se passe. J'ai l'erreur 1814 qui est 'espace insuffisant pour tempdb' mais j'ai 60Go de données dans le lecteur C :. En outre, il essaye d'ouvrir des tables de E: drive qui est mon lecteur de DVD qui n'est pas censé se produire.

Ici en ajoutant les journaux. S'il vous plaît laissez-moi savoir ce qui ne va pas.

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: -dc:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\DATA\master.mdf -ec:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\Log\ERRORLOG -lc:\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 certificatee 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. 

Regardez ces liens:

1) Assurez-vous de décocher "Compresser le contenu pour économiser de l'espace disque" pour le file tempdb.mdf

2) Assurez-vous de ne pas save tempdb dans un dossier compressé

AUSSI:

Quelle est cette erreur:

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

Peut-être que vous voulez juste prendre "model" hors ligne?

J'ai eu le même problème avec SQL Express. Les installateurs MS SQL sont très buggés. Plusieurs fois, je me suis retrouvé dans des situations où je devais juste réinstaller le operating system. Pour ce problème particulier, la solution est ici: https://social.technet.microsoft.com/wiki/contents/articles/31786.sql-server-not-starting-after-fresh-installation.aspx .

Les bits essentiels sont:

Démarrez le service à partir de la command line à l'aide de la command suivante

 NET START MSSQLSERVER /f /T3608 

Exécutez le processeur de requête de command line:

 SQLCMD –S .\ 

ou

 SQLCMD –S .\INSTANCENAME 

Vérifiez les paths des bases de données:

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

Corrigez les paths de la database:

 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 

Quittez et redémarrez le service:

 exit NET STOP MSSQLSERVER NET START MSSQLSERVER