Hello. I am experiencing the issue with SQL Server 2005 service not able to start when TCP/IP is enabled. I have researched this issue extensively and what I come up with are fixes for checkpoints on clustered instances. ISSUE: I am running a machine with XP Pro and not Server 2003, so I CANNOT have clustered instances. ALL the fixes out there refer to commands such as "cluster res" which do not exist in Win XP Pro. Here is the error log which looks exactly like everyone else's (when they are dealing with clusters on Server 2003). Can anyone shed ANY light on how to deal with this on a Win XP machine? I'm going totally crazy here. I can get the local server to load by disabling TCP/IP in SSCM. VIA does not need to be disabled, just TCP/IP. Of course you know this issue came up when I attempted to change the Listen Port / IP address. I was starting and restarting and stopping and starting the SQL service in order to apply changes within SSCM and must have attempted to apply a change while the SQL server wasn't running. Thank you in advance for any help. FYI, I attempted to run the GUI clusterrecovery.com but it failed miserably. The "browse" function gave me an ActiveX error and I couldn't locate my Cluster because I don't think I have one. Please, someone, any one... HELP.
2013-01-21 10:56:42.12 Server Microsoft SQL Server 2005 - 9.00.5000.00 (Intel X86)
Dec 10 2010 10:56:29
Copyright (c) 1988-2005 Microsoft Corporation
Express Edition with Advanced Services on Windows NT 5.1 (Build 2600: Service Pack 3)
2013-01-21 10:56:42.23 Server (c) 2005 Microsoft Corporation.
2013-01-21 10:56:42.25 Server All rights reserved.
2013-01-21 10:56:42.26 Server Server process ID is 4280.
2013-01-21 10:56:42.28 Server Authentication mode is MIXED.
2013-01-21 10:56:42.29 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2013-01-21 10:56:42.32 Server This instance of SQL Server last reported using a process ID of 5292 at 1/21/2013 10:53:24 AM (local) 1/21/2013 5:53:24 PM (UTC). This is an informational message only; no user action is required.
2013-01-21 10:56:42.37 Server Registry startup parameters:
2013-01-21 10:56:42.39 Server -d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2013-01-21 10:56:42.42 Server -e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2013-01-21 10:56:42.45 Server -l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2013-01-21 10:56:42.48 Server Command Line Startup Parameters:
2013-01-21 10:56:42.50 Server -s advisorsassist
2013-01-21 10:56:42.53 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2013-01-21 10:56:42.56 Server Detected 2 CPUs. This is an informational message; no user action is required.
2013-01-21 10:56:43.23 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.
2013-01-21 10:56:43.29 Server Database mirroring has been enabled on this instance of SQL Server.
2013-01-21 10:56:43.32 spid5s Starting up database 'master'.
2013-01-21 10:56:43.46 spid5s 1 transactions rolled forward in database 'master' (1). This is an informational message only. No user action is required.
2013-01-21 10:56:43.51 spid5s 0 transactions rolled back in database 'master' (1). This is an informational message only. No user action is required.
2013-01-21 10:56:43.54 spid5s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2013-01-21 10:56:43.67 spid5s SQL Trace ID 1 was started by login "sa".
2013-01-21 10:56:43.68 spid5s Starting up database 'mssqlsystemresource'.
2013-01-21 10:56:43.74 spid5s The resource database build version is 9.00.5000. This is an informational message only. No user action is required.
2013-01-21 10:56:43.96 spid8s Starting up database 'model'.
2013-01-21 10:56:43.96 Server Virtual Interface Architecture protocol is not supported for this particular edition of SQL Server.
2013-01-21 10:56:43.98 spid5s Server name is 'LOWELL\ADVISORSASSIST'. This is an informational message only. No user action is required.
2013-01-21 10:56:44.12 spid8s Clearing tempdb database.
2013-01-21 10:56:44.28 spid8s Starting up database 'tempdb'.
2013-01-21 10:56:44.43 spid11s The Service Broker protocol transport is disabled or not configured.
2013-01-21 10:56:44.46 spid11s The Database Mirroring protocol transport is disabled or not configured.
2013-01-21 10:56:44.54 spid11s Service Broker manager has started.
2013-01-21 10:56:44.57 Server A self-generated certificate was successfully loaded for encryption.
2013-01-21 10:56:44.62 Server Server is listening on [ 'any' <ipv4> 3136].
2013-01-21 10:56:44.64 Server Error: 26023, Severity: 16, State: 1.
2013-01-21 10:56:44.64 Server Server TCP provider failed to listen on [ 'any' <ipv4> 3136]. Tcp port is already in use.
2013-01-21 10:56:44.68 Server Error: 17182, Severity: 16, State: 1.
2013-01-21 10:56:44.68 Server TDSSNIClient initialization failed with error 0x2740, status code 0xa.
2013-01-21 10:56:44.73 Server Error: 17182, Severity: 16, State: 1.
2013-01-21 10:56:44.73 Server TDSSNIClient initialization failed with error 0x2740, status code 0x1.
2013-01-21 10:56:44.78 Server Error: 17826, Severity: 18, State: 3.
2013-01-21 10:56:44.78 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.
2013-01-21 10:56:44.84 Server Error: 17120, Severity: 16, State: 1.
2013-01-21 10:56:44.84 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.