Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums  SQL Server 2005 Forums  Express Edition and Compact Edition (2005)  Cannot install on Vista Home Premium

Author  Topic  rk294 Starting Member 1 Post Posted - 2009-10-24 : 17:56:34 Hi, I get the error message: "The SQL Server Service failed to start. For more information, see the SQL server books online topics, How to View SQL Server 2005 Setup Logs and Start SQL Server Manually." I have attached the error log I received after trying to install. Any help would be appreciated. Thanks! 2009-10-24 16:27:25.37 Server Microsoft SQL Server 2005 - 9.00.4035.00 (Intel X86) Nov 24 2008 13:01:59 Copyright (c) 1988-2005 Microsoft Corporation Express Edition on Windows NT 6.0 (Build 6002: Service Pack 2) 2009-10-24 16:27:25.37 Server (c) 2005 Microsoft Corporation. 2009-10-24 16:27:25.37 Server All rights reserved. 2009-10-24 16:27:25.37 Server Server process ID is 4752. 2009-10-24 16:27:25.37 Server Authentication mode is MIXED. 2009-10-24 16:27:25.37 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'. 2009-10-24 16:27:25.37 Server This instance of SQL Server last reported using a process ID of 4376 at 10/24/2009 4:27:17 PM (local) 10/24/2009 9:27:17 PM (UTC). This is an informational message only; no user action is required. 2009-10-24 16:27:25.37 Server Registry startup parameters: 2009-10-24 16:27:25.37 Server -d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf 2009-10-24 16:27:25.37 Server -e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG 2009-10-24 16:27:25.37 Server -l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf 2009-10-24 16:27:25.37 Server Command Line Startup Parameters: 2009-10-24 16:27:25.37 Server -m SqlSetup 2009-10-24 16:27:25.37 Server SqlSetup 2009-10-24 16:27:25.37 Server -Q 2009-10-24 16:27:25.37 Server -q SQL_Latin1_General_CP1_CI_AS 2009-10-24 16:27:25.37 Server -T 4022 2009-10-24 16:27:25.37 Server -T 3659 2009-10-24 16:27:25.37 Server -T 3610 2009-10-24 16:27:25.37 Server -T 4010 2009-10-24 16:27:25.39 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required. 2009-10-24 16:27:25.39 Server Detected 2 CPUs. This is an informational message; no user action is required. 2009-10-24 16:27:25.54 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-10-24 16:27:25.65 Server Database Mirroring Transport is disabled in the endpoint configuration. 2009-10-24 16:27:25.65 spid5s Warning ****************** 2009-10-24 16:27:25.65 spid5s SQL Server started in single-user mode. This an informational message only. No user action is required. 2009-10-24 16:27:25.65 spid5s Starting up database 'master'. 2009-10-24 16:27:25.85 spid5s SQL Trace ID 1 was started by login "sa". 2009-10-24 16:27:25.88 spid5s Starting up database 'mssqlsystemresource'. 2009-10-24 16:27:25.91 spid5s The resource database build version is 9.00.4035. This is an informational message only. No user action is required. 2009-10-24 16:27:26.15 Server Error: 17182, Severity: 16, State: 1. 2009-10-24 16:27:26.15 Server TDSSNIClient initialization failed with error 0x2, status code 0x80. 2009-10-24 16:27:26.15 spid7s Starting up database 'model'. 2009-10-24 16:27:26.15 Server Error: 17182, Severity: 16, State: 1. 2009-10-24 16:27:26.15 Server TDSSNIClient initialization failed with error 0x2, status code 0x1. 2009-10-24 16:27:26.15 Server Error: 17826, Severity: 18, State: 3. 2009-10-24 16:27:26.15 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. 2009-10-24 16:27:26.15 Server Error: 17120, Severity: 16, State: 1. 2009-10-24 16:27:26.15 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.