I'm new to SQL EXPRESS. I had it set up a month or 2 ago working fine, but now it won't work. I'm guessing it's a permissions thing b/c I get a lot of those errors in general. I also recently upgraded to XP SP3. But I cannot figure out how to get the sql express server to start. My error log is below. Googling for an answer either doesn't answer it or blows my mind with stuff I don't understand.
Since I'm just getting started (although I do have one db set up), I'm open to all kinds of suggestions of how to set this up CORRECTLY and EASILY.
2008-06-11 10:34:16.01 Server Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86)
Feb 9 2007 22:47:07
Copyright (c) 1988-2005 Microsoft Corporation
Express Edition on Windows NT 5.1 (Build 2600: Service Pack 3)
2008-06-11 10:34:16.01 Server (c) 2005 Microsoft Corporation.
2008-06-11 10:34:16.01 Server All rights reserved.
2008-06-11 10:34:16.01 Server Server process ID is 4144.
2008-06-11 10:34:16.01 Server Authentication mode is WINDOWS-ONLY.
2008-06-11 10:34:16.01 Server Logging SQL Server messages in file 'c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2008-06-11 10:34:16.01 Server This instance of SQL Server last reported using a process ID of 4336 at 6/11/2008 10:27:53 AM (local) 6/11/2008 2:27:53 PM (UTC). This is an informational message only; no user action is required.
2008-06-11 10:34:16.01 Server Error: 17053, Severity: 16, State: 1.
2008-06-11 10:34:16.01 Server UpdateUptimeRegKey: Operating system error 5(Access is denied.) encountered.
2008-06-11 10:34:16.01 Server Registry startup parameters:
2008-06-11 10:34:16.01 Server -d c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2008-06-11 10:34:16.01 Server -e c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2008-06-11 10:34:16.01 Server -l c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2008-06-11 10:34:16.04 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2008-06-11 10:34:16.04 Server Detected 2 CPUs. This is an informational message; no user action is required.
2008-06-11 10:34:16.68 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.
2008-06-11 10:34:16.70 Server The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-06-11 10:34:16.71 Server Database mirroring has been enabled on this instance of SQL Server.
2008-06-11 10:34:16.71 spid5s Starting up database 'master'.
2008-06-11 10:34:16.89 spid5s SQL Trace ID 1 was started by login "sa".
2008-06-11 10:34:16.92 spid5s Starting up database 'mssqlsystemresource'.
2008-06-11 10:34:16.96 spid5s The resource database build version is 9.00.3042. This is an informational message only. No user action is required.
2008-06-11 10:34:17.17 spid5s Failed to check for new installation or a renamed server at startup. The logic for this check has failed unexpectedly. Run setup again, or fix the problematic registry key.
2008-06-11 10:34:17.17 spid8s Starting up database 'model'.
2008-06-11 10:34:17.17 Server Error: 17182, Severity: 16, State: 1.
2008-06-11 10:34:17.17 Server TDSSNIClient initialization failed with error 0x5, status code 0x90.
2008-06-11 10:34:17.20 Server Error: 17182, Severity: 16, State: 1.
2008-06-11 10:34:17.20 Server TDSSNIClient initialization failed with error 0x5, status code 0x1.
2008-06-11 10:34:17.20 Server Error: 17826, Severity: 18, State: 3.
2008-06-11 10:34:17.20 Server 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.
2008-06-11 10:34:17.20 spid5s Server name is 'HARLEM\SQLEXPRESS'. This is an informational message only. No user action is required.
2008-06-11 10:34:17.20 Server Error: 17120, Severity: 16, State: 1.
2008-06-11 10:34:17.20 Server SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.