10-19-09, 10:21 #1Registered User
- Join Date
- Oct 2009
Unanswered: SQL Instance is not able to start.
Iím trying to make Cluster SQL Server 2005 and have encountered an error. It actually happened even during installation when I was making SQL Cluster. During installation when SQL Setup tired to start SQL Server instance it couldnít and I had error saying ĎSome services need to be start manually as setup has failed to start them.í It was obvious that itís SQL Instance who is not able to start. When I went to start it manually it still didnít stared. Then I checked processes though Task Manager & I observed a process (sqlserver.exe) tries to start but then suddenly get vanished. NOT SURE AT ALL WHY THOUGH. Since Iíve made cluster so when I move my groups (Cluster Group, MSDTC & SQL_2005) from active SANDBOX1 (where instance is not able to start and keep getting fail) to passive SANDBOX2 SQL Instance starts and everything start working fine. So at this point its clear something is wrong with SANDBOX1 and instances is not able to start. Did anybody faced this problem or have any clue what is causing this problem?
Thanks a lot in advance.
10-19-09, 12:01 #2Resident Curmudgeon
Provided Answers: 54
- Join Date
- Feb 2004
- In front of the computer
Check the SQL errorlog text file(s). If you don't find the answer there, check your Windows Event Log.
SQL Server is designed as a Windows Service, so it issues almost all of its diagnostic information into the logs instead of to the console.
For what it is worth, SQL clustering is FAR cleaner and easier to manage in SQL 2008 than it was in SQL 2005. An aborted cluster install in SQL 2005 is difficult to recover. In comparison, SQL 2008 is almost trivially easy to repair.
-PatPIn theory, theory and practice are identical. In practice, theory and practice are unrelated.
10-19-09, 12:28 #3Registered User
- Join Date
- Oct 2009
Thanks Pat for your input. Here is what I've found in errorlog. Open it with Notepad. You were right Iíve notice Service Broker start but then stop. And this is why Server is not able to start. What should I do to fix Service broker? Here is ERRORLOG details
2009-10-19 11:06:24.82 Server (c) 2005 Microsoft Corporation.
2009-10-19 11:06:24.82 Server All rights reserved.
2009-10-19 11:06:24.82 Server Server process ID is 1080.
2009-10-19 11:06:24.82 Server Logging SQL Server message in file 'S:\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2009-10-19 11:06:24.82 Server This instance of SQL Server last reported using a process ID of 2716 at 10/19/2009 11:06:23 AM (local) 10/19/2009. This is an informational message only; no user action is required.
2009-10-19 11:06:24.82 Server Registry Startup parameters:
2009-10-19 11:06:24.82 Server -d S:\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2009-10-19 11:06:24.82 Server -e S:\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2009-10-19 11:06:24.82 Server -l S:\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.ldf
2009-10-19 11:06:24.83 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2009-10-19 11:06:24.83 Server Detected 1 CPUs. This is an informational message; no user action is required.
2009-10-19 11:06:25.07 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock ower blocks per node. This is an informational message only. No user action is required.
2009-10-19 11:06:25.10 Server Attempting to initialize Microsoft Distrubuted Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2009-10-19 11:06:27.47 Server Attempting to recover in-doubt distributed transactions involving Microsoft Distrubured Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2009-10-19 11:06:27.47 Server Database Mirroring Transport is disabled in the endpoint configuration.
2009-10-19 11:06:27.49 spid5s Starting up database 'master'.
2009-10-19 11:06:27.57 spid5s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is requried.
2009-10-19 11:06:27.61 spid5s SQL Trace ID 1 was started by login "sa".
2009-10-19 11:06:27.63 spid5s Starting up database 'mssqlsystemresource'.
2009-10-19 11:06:27.79 spid5s Server name is 'SQLSERVERSVR\SQLSERVERINS'. This is an indormational message only. No user action is required.
2009-10-19 11:06:28.30 spid5s The NETBIOS name of the local node that is rurnnig the server is 'SANDBOX1'. This is an informational message ony. No user action is required.
2009-10-19 11:06:28.32 spid5s Starting up database 'model'.
2009-10-19 11:06:28.51 Server A self-generated certificate was successfully loaded for encryption.
2009-10-19 11:06:28.52 Server Server is listening on [10.151.244.180 <ipv4> 2834].
2009-10-19 11:06:28.52 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQLSERVERINS].
2009-10-19 11:06:28.52 Server Server named pipe provide is ready to accept aconnection on [ \\.\pipe\$$\SQLSERVERSVR\MSSQL$SQLSERVERINS\sql\qu ery ].
2009-10-19 11:06:28.60 Server SQL Server is now ready for client connection. This is an informationl message; no user action is required.
2009-10-19 11:06:28.63 spid9s Clearing tempdb database.
2009-10-19 11:06:28.63 spid5s Starting up database 'msdb'.
2009-10-19 11:06:28.77 spid5s Recovery of any in-doubt distributed transactions involving Microsoft Distribured Transaction Coordinator (MS DTC) has completed. This is an informationl message only. No user action is required.
2009-10-19 11:06:28.91 spid9s Starting up database 'tempdb'.
2009-10-19 11:06:29.05 spid5s Recovery is complete. This is an informationl message only. No user action is required.
2009-10-19 11:06:29.05 spid12s The Service Broker protocol transport is disabled or not configured.
2009-10-19 11:06:29.05 spid12s The Database Mirroring protocol transport is disabled or not configured.
2009-10-19 11:06:29.07 spid12s Service Broker manager has started.
2009-10-19 11:06:50.74 spid12s Service Broker manager has shut down.
2009-10-19 11:06:50.77 spid5s SQL Server is terminating in response to a 'stop' request from Service Control Manager. This is an informational message only. No user action is required.
2009-10-19 11:06:50.77 spid5s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is informational message only; No user action is required.
10-20-09, 15:00 #4Registered User
- Join Date
- Jul 2003
- San Antonio, TX
If after moving the cluster groups to the second node you're able to start the service, you need to go back to the configuration of the nodes. The must be configured identically. Run syscompare utility to verify that the nodes are identical. Also check the private network configuration, because the stop request is most likely issued by the cluster service which found a problem. Also, you're saying that the service stops. Doesn't it attempt to be restarted by the cluster service, and then failed over? If it doesn't happen, - SQL cluster was not correctly installed. You will need to review the installation logs in Bootstrap directory (just search for it, I don't remember exactly where it creates them)."The data in a record depends on the Key to the record, the Whole Key, and
nothing but the Key, so help me Codd."