SQL Instance is not able to start.

  • Hello experts,

    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.

  • Did you check the event logs for errors?

  • As Steve has mentioned, check the windows event logs, if the sql service failed to start, the reason should be there in the event logs.

    --------------------------------------------------------------------------------------
    [highlight]Recommended Articles on How to help us help you and[/highlight]
    [highlight]solve commonly asked questions[/highlight]

    Forum Etiquette: How to post data/code on a forum to get the best help by Jeff Moden[/url]
    Managing Transaction Logs by Gail Shaw[/url]
    How to post Performance problems by Gail Shaw[/url]
    Help, my database is corrupt. Now what? by Gail Shaw[/url]

  • Check the SQL error log as well (text file called ERRORLOG). It will give the reasons why the service failed to start

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • Steve and SilverFox thanks a lot for both of yours input. Yes there are 2 errors I've found in Application events log which are as follows.

    1. [sqsrves]checkODBCConnection Error: sqlstate = IM002; Native error = 0;

    Message = [Microsoft][ODBC Driver Manager] Data Soruce name not found and no default driver specified.

    2. ODBC sqldriverconnect failed.

    Now I’m not sure what is exactly is missing. Any idea?

    Thanks,

  • The application log won't help you with services. You need to check the system log.

  • SQL Error log?

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • Thanks again Steve. I checked system log but it doesn’t help much. 4 information messages shows up

    followed by 1 error message.

    Information messages:

    1.The SQL Server [SQLSERVERINS] service was successfully sent a start control.

    2.The SQL Server [SQLSERVERINS] service entered the running state

    3.The SQL Server [SQLSERVERINS] service was successfully send a stop control.

    4.The SQL Server [SQLSERVERINS] service entered the stopped state.

    Error message:

    Cluster resource ‘SQL Server [SQLSERVERINS] ’ in Resource Group ‘SQL_2005’failed.

    Now I’m not sure at all after service starts successfully then who/what send stop control to it?

  • Thanks Gail 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\query ].

    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.

    Thanks

  • mr_adeelalisyed (10/19/2009)


    You were right I’ve notice Service Broker start but then stop. And this is why Server is not able to start.

    Nope, other way around. Service broker is stopping because the SQL server is stopping.

    There's an external request coming to SQL to terminate. Could be coming from cluster administration. Can you check the cluster administration logs?

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • Not sure how to check Cluster Administrator logs. Can you please tell?

  • Gail and all others thanks for your input. I’ve notice something strange.When I've started SQL Server Services though Service. I witness SQL Server Status 'Started' within service however still when I look at cluster Administrator it still shows SQL Server is not running. Since it's in cluster environment it tries 3 times and then switch to passive node. For sure something is stopping it but don't know what is it. Does something is wrong Cluster Administrator?

Viewing 12 posts - 1 through 11 (of 11 total)

You must be logged in to reply to this topic. Login to reply