Question : MSSQL Service will not start up (Logs Posted)

I have a Windows 2000 Server and the MSSQL Service will not start. Below is the most recent Error Log.

Code Snippet:

1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:
31:
32:
33:
34:
35:
36:
37:
38:
39:
40:
41:



2009-12-14 09:05:43.67 kernel   Microsoft SQL Server  7.00 - 7.00.1063 (Intel X86) 
	Apr  9 2002 14:18:16 
	Copyright (c) 1988-2002 Microsoft Corporation
	Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4) 
2009-12-14 09:05:43.67 kernel   Copyright (C) 1988-1997 Microsoft Corporation.
2009-12-14 09:05:43.67 kernel   All rights reserved.
2009-12-14 09:05:43.67 kernel   Logging SQL Server messages in file 'C:\MSSQL7\log\ERRORLOG'.
2009-12-14 09:05:43.68 kernel   initconfig: Number of user connections limited to 32767.
2009-12-14 09:05:43.68 kernel   SQL Server is starting at priority class 'normal'(1 CPU detected).
2009-12-14 09:05:43.70 kernel   User Mode Scheduler configured for thread processing
2009-12-14 09:05:44.81 server   Directory Size: 74425
2009-12-14 09:05:44.81 spid1    Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks
2009-12-14 09:05:44.81 kernel   Attempting to initialize Distributed Transaction Coordinator.
2009-12-14 09:05:44.85 spid1    Failed to obtain TransactionDispenserInterface: Result Code = 0x8004d01b
2009-12-14 09:05:44.85 spid1    Starting up database 'master'.
2009-12-14 09:05:44.85 spid1    Opening file C:\MSSQL7\data\master.mdf. 
2009-12-14 09:05:44.87 spid1    Opening file C:\MSSQL7\data\mastlog.ldf. 
2009-12-14 09:05:44.90 spid1    Loading SQL Server's  Unicode collation.
2009-12-14 09:05:44.90 spid1    Loading SQL Server's  non-Unicode sort order and character set.
2009-12-14 09:05:44.95 spid1    Starting up database 'model'.
2009-12-14 09:05:44.95 spid1    Opening file C:\MSSQL7\DATA\model.mdf. 
2009-12-14 09:05:44.96 spid1    Opening file c:\mssql7\data\modellog.ldf. 
2009-12-14 09:05:44.99 spid1    Clearing tempdb database.
2009-12-14 09:05:44.99 spid1    Creating file C:\MSSQL7\DATA\TEMPDB.MDF. 
2009-12-14 09:05:45.23 spid1    Closing file C:\MSSQL7\DATA\TEMPDB.MDF. 
2009-12-14 09:05:45.29 spid1    Creating file C:\MSSQL7\DATA\TEMPLOG.LDF. 
2009-12-14 09:05:45.42 spid1    Closing file C:\MSSQL7\DATA\TEMPLOG.LDF. 
2009-12-14 09:05:45.49 spid1    Opening file C:\MSSQL7\DATA\TEMPDB.MDF. 
2009-12-14 09:05:45.51 spid1    Opening file C:\MSSQL7\DATA\TEMPLOG.LDF. 
2009-12-14 09:05:45.70 spid1    Closing file C:\MSSQL7\DATA\TEMPDB.MDF. 
2009-12-14 09:05:45.74 spid1    Closing file C:\MSSQL7\DATA\TEMPLOG.LDF. 
2009-12-14 09:05:45.79 spid1    Starting up database 'tempdb'.
2009-12-14 09:05:45.79 spid1    Opening file C:\MSSQL7\DATA\TEMPDB.MDF. 
2009-12-14 09:05:45.81 spid1    Opening file C:\MSSQL7\DATA\TEMPLOG.LDF. 
2009-12-14 09:05:45.82 spid1    Bypassing recovery for database 'tempdb' because it is marked SUSPECT.
2009-12-14 09:05:45.84 spid1    Database 'tempdb' cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information.
2009-12-14 09:05:45.84 spid1    WARNING: problem activating all tempdb files.
2009-12-14 09:05:45.84 spid1    Trying just primary files.
2009-12-14 09:05:45.84 spid1    Database 'tempdb' cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information.
2009-12-14 09:05:45.84 spid1    Database 'tempdb' cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information.

Open in New Window

Select All

Answer : MSSQL Service will not start up (Logs Posted)

This happens when there is an issue with accessing/finding tempdb files. Here is the step by step process on how to resolve it:

1. Try to rename the files tempdb.mdf and templog.ldf files
2. Goto command prompt and navigate to the sql server files location (Ideally it will be in C:\Program Files\Microsoft SQL Server\MSSQL\Binn\) and type the command sqlservr -c -f -T3608 -T4022 and press Enter
3. Keep the command prompt window open and connect to Query Analyzer and execute the query
exec master..sp_resetstatus Tempdb
4. In the command prompt window, type Ctrl+C twice to shutdown the server
5. Restart the SQL Server service. This creates a new set of tempdb database files, and recovers the tempdb database.

Please revert in case of any clarifications.