Question : Microsoft SQL server 2005 wont start after updates.

I have a XP machine running SQL 2005  for Microsoft Small business financials 9.0/dynamics and a service software called servicom.

everything was fine yesterday and when I came in the morning the computer had installed updates at restarted automatically (thanks microsoft.)
When I tried to open SBF or servicom they both hang because SQL isn't running.
I opened SQL server configuration manager and saw that the sql service was not running (full text search, agent and browser were all running.)
When i try to start SQL server it says the request failed because the service didn't respond in a timely fashion.
i found the errorlog file and attached it below.
it is saying it cant find the files but they are there if i check, are they corrupt?
I dont know enough about SQL to know what to do here.
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:
42:
43:
44:
45:
46:
47:
48:
49:
50:
51:
52:
2009-11-11 16:06:31.17 Server      Microsoft SQL Server 2005 - 9.00.2047.00 (Intel X86) 
	Apr 14 2006 01:12:25 
	Copyright (c) 1988-2005 Microsoft Corporation
	Standard Edition on Windows NT 5.1 (Build 2600: Service Pack 3) 
2009-11-11 16:06:31.17 Server      (c) 2005 Microsoft Corporation.
2009-11-11 16:06:31.17 Server      All rights reserved.
2009-11-11 16:06:31.17 Server      Server process ID is 2548.
2009-11-11 16:06:31.17 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2009-11-11 16:06:31.18 Server      This instance of SQL Server last reported using a process ID of 1932 at 11/11/2009 4:00:42 PM (local) 11/11/2009 9:00:42 PM (UTC). This is an informational message only; no user action is required.
2009-11-11 16:06:31.18 Server      Registry startup parameters:
2009-11-11 16:06:31.18 Server      	 -d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2009-11-11 16:06:31.18 Server      	 -e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2009-11-11 16:06:31.18 Server      	 -l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2009-11-11 16:06:31.18 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2009-11-11 16:06:31.18 Server      Detected 1 CPUs. This is an informational message; no user action is required.
2009-11-11 16:06:31.98 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.
2009-11-11 16:06:31.99 Server      Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2009-11-11 16:06:33.01 Server      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-11-11 16:06:33.01 Server      Database mirroring has been enabled on this instance of SQL Server.
2009-11-11 16:06:33.01 spid5s      Starting up database 'master'.
2009-11-11 16:06:33.10 spid5s      SQL Trace ID 1 was started by login "sa".
2009-11-11 16:06:33.15 spid5s      Starting up database 'mssqlsystemresource'.
2009-11-11 16:06:33.17 spid5s      The resource database build version is 9.00.2047. This is an informational message only. No user action is required.
2009-11-11 16:06:33.57 Server      A self-generated certificate was successfully loaded for encryption.
2009-11-11 16:06:33.57 spid5s      Server name is 'WS-1\SERVICOM'. This is an informational message only. No user action is required.
2009-11-11 16:06:33.59 spid9s      Starting up database 'model'.
2009-11-11 16:06:33.59 Server      Server is listening on [ 'any'  1041].
2009-11-11 16:06:33.59 Server      Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SERVICOM ].
2009-11-11 16:06:33.59 Server      Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$SERVICOM\sql\query ].
2009-11-11 16:06:33.59 Server      Server is listening on [ 127.0.0.1  1042].
2009-11-11 16:06:33.59 Server      Dedicated admin connection support was established for listening locally on port 1042.
2009-11-11 16:06:33.59 Server      The SQL Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b. 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.
2009-11-11 16:06:33.59 Server      SQL Server is now ready for client connections. This is an informational message; no user action is required.
2009-11-11 16:06:33.60 spid12s     Starting up database 'msdb'.
2009-11-11 16:06:33.60 spid13s     Starting up database 'DYNAMICS'.
2009-11-11 16:06:33.60 spid14s     Starting up database 'SBM01'.
2009-11-11 16:06:33.60 spid15s     Starting up database 'SWData'.
2009-11-11 16:06:33.60 spid15s     Error: 17207, Severity: 16, State: 1.
2009-11-11 16:06:33.60 spid15s     FCB::Open: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\SWData.mdf'. Diagnose and correct the operating system error, and retry the operation.
2009-11-11 16:06:33.60 spid15s     Error: 17204, Severity: 16, State: 1.
2009-11-11 16:06:33.60 spid15s     FCB::Open failed: Could not open file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\SWData.mdf for file number 1.  OS error: 2(The system cannot find the file specified.).
2009-11-11 16:06:33.62 spid15s     Error: 5120, Severity: 16, State: 101.
2009-11-11 16:06:33.62 spid15s     Unable to open the physical file "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\SWData.mdf". Operating system error 2: "2(The system cannot find the file specified.)".
2009-11-11 16:06:33.73 spid9s      Error: 5172, Severity: 16, State: 15.
2009-11-11 16:06:33.73 spid9s      The header for file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\modellog.ldf' is not a valid database file header. The PageAudit property is incorrect.
2009-11-11 16:06:33.73 spid9s      File activation failure. The physical file name "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\modellog.ldf" may be incorrect.
2009-11-11 16:06:33.73 spid9s      The log cannot be rebuilt because the database was not cleanly shut down.
2009-11-11 16:06:33.73 spid9s      Error: 945, Severity: 14, State: 2.
2009-11-11 16:06:33.73 spid9s      Database 'model' cannot be opened due to inaccessible files or insufficient memory or disk space.  See the SQL Server errorlog for details.
2009-11-11 16:06:33.73 spid9s      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.
2009-11-11 16:06:33.73 spid9s      SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.

Answer : Microsoft SQL server 2005 wont start after updates.

I got it working here are the rest of the steps i tried.
I tried system restore, no change.
What worked was stopping all SQL process and restoring the entire "C:\Program files\Microsoft SQL Server\" folder from a hard drive image backup i had.
I restarted and low and behold SQL was running again.
From there i had to restore the individual databases for SBF and Servicom now that they would open again.

After that I disabled automatic updates so I don't have any more unexpected restarts.
Random Solutions  
 
programming4us programming4us