Results 1 to 5 of 5
  1. #1
    Join Date
    Feb 2009
    Posts
    3

    Unanswered: SQL Server Cluster Failing on One Node

    Hello,

    I am new to this forum. I need help on my issue with SQL server not starting on one node of the cluster. I already checked the service user for both nodes and they are the same. In the event viewer, I see the following logs:

    [sqsrvres] checkODBCConnectError: sqlstate = 08001; native error = ffffffff; message = [Microsoft][SQL Native Client]An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.

    [sqsrvres] ODBC sqldriverconnect failed

    [sqsrvres] checkODBCConnectError: sqlstate = HYT00; native error = 0; message = [Microsoft][SQL Native Client]Login timeout expired

    The ERRORLOG on the other hand is as follows:
    2009-02-12 03:44:04.48 Server Microsoft SQL Server 2005 - 9.00.3257.00 (X64)
    Jun 12 2008 16:47:07
    Copyright (c) 1988-2005 Microsoft Corporation
    Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)

    2009-02-12 03:44:04.48 Server (c) 2005 Microsoft Corporation.
    2009-02-12 03:44:04.48 Server All rights reserved.
    2009-02-12 03:44:04.48 Server Server process ID is 7208.
    2009-02-12 03:44:04.48 Server Authentication mode is MIXED.
    2009-02-12 03:44:04.48 Server Logging SQL Server messages in file 'S:\MSSQL\MSSQL.1\MSSQL\LOG\ERRORLOG'.
    2009-02-12 03:44:04.48 Server This instance of SQL Server last reported using a process ID of 4552 at 2/12/2009 3:42:34 AM (local) 2/12/2009 3:42:34 AM (UTC). This is an informational message only; no user action is required.
    2009-02-12 03:44:04.48 Server Registry startup parameters:
    2009-02-12 03:44:04.48 Server -d S:\MSSQL\MSSQL.1\MSSQL\DATA\master.mdf
    2009-02-12 03:44:04.48 Server -e S:\MSSQL\MSSQL.1\MSSQL\LOG\ERRORLOG
    2009-02-12 03:44:04.48 Server -l S:\MSSQL\MSSQL.1\MSSQL\DATA\mastlog.ldf
    2009-02-12 03:44:04.48 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2009-02-12 03:44:04.48 Server Detected 4 CPUs. This is an informational message; no user action is required.
    2009-02-12 03:44:04.49 Server Cannot use Large Page Extensions: lock memory privilege was not granted.
    2009-02-12 03:44:04.62 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-02-12 03:44:04.63 Server Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
    2009-02-12 03:44:04.65 Server The Microsoft Distributed Transaction Coordinator (MS DTC) service could not be contacted. If you would like distributed transaction functionality, please start this service.
    2009-02-12 03:44:04.65 Server Database mirroring has been enabled on this instance of SQL Server.
    2009-02-12 03:44:04.66 spid5s Starting up database 'master'.
    2009-02-12 03:44:04.68 spid5s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
    2009-02-12 03:44:04.70 spid5s SQL Trace ID 1 was started by login "sa".
    2009-02-12 03:44:04.70 spid5s Starting up database 'mssqlsystemresource'.
    2009-02-12 03:44:04.70 spid5s The resource database build version is 9.00.3257. This is an informational message only. No user action is required.
    2009-02-12 03:44:04.76 spid5s Server name is 'USGDC-VBWDBP\BP1'. This is an informational message only. No user action is required.
    2009-02-12 03:44:04.76 spid5s The NETBIOS name of the local node that is running the server is 'USGDC-SBW02P'. This is an informational message only. No user action is required.
    2009-02-12 03:44:04.76 spid9s Starting up database 'model'.
    2009-02-12 03:44:04.79 spid9s Clearing tempdb database.
    2009-02-12 03:44:04.85 spid9s Starting up database 'tempdb'.
    2009-02-12 03:44:04.87 spid9s Analysis of database 'tempdb' (2) is 100% complete (approximately 0 seconds remain). This is an informational message only. No user action is required.
    2009-02-12 03:44:04.88 spid12s The Service Broker protocol transport is disabled or not configured.
    2009-02-12 03:44:04.88 spid12s The Database Mirroring protocol transport is disabled or not configured.
    2009-02-12 03:44:04.90 spid12s Service Broker manager has started.
    2009-02-12 03:44:04.99 Server A self-generated certificate was successfully loaded for encryption.
    2009-02-12 03:44:05.01 Server Server is listening on [ 192.168.4.115 <ipv4> 4052].
    2009-02-12 03:44:05.01 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\BP1 ].
    2009-02-12 03:44:05.01 Server Server named pipe provider is ready to accept connection on [ \\.\pipe\$$\USGDC-VBWDBP\MSSQL$BP1\sql\query ].
    2009-02-12 03:44:05.02 Server The SQL Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x2098, state: 15. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
    2009-02-12 03:44:05.02 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
    2009-02-12 03:44:05.04 spid18s Starting up database 'BP1'.
    2009-02-12 03:44:05.04 spid19s Starting up database 'msdb'.
    2009-02-12 03:44:05.09 spid18s Analysis of database 'BP1' (5) is 100% complete (approximately 0 seconds remain). This is an informational message only. No user action is required.
    2009-02-12 03:44:05.29 spid18s CHECKDB for database 'BP1' finished without errors on 2009-02-01 01:00:21.997 (local time). This is an informational message only; no user action is required.
    2009-02-12 03:44:05.31 spid5s Recovery is complete. This is an informational message only. No user action is required.
    2009-02-12 03:47:35.29 spid12s Service Broker manager has shut down.
    2009-02-12 03:47:35.31 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-02-12 03:47:35.31 spid5s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.

    Can someone help me on this? Thanks!

    Regards,
    Regina

  2. #2
    Join Date
    Jan 2003
    Location
    Massachusetts
    Posts
    5,800
    Provided Answers: 11
    Are there any cluster resources dependent on the SQL Server resource (beside SQL Agent)? There is a cluster log at C:\Windows\Cluster\cluster.log, but it is considerably verbose. It will take some time to go through, but it will tell you what happened. I am thinking some cluster resource fails on the affected node, and the whole group fails back to where it feels safe.

  3. #3
    Join Date
    Feb 2009
    Posts
    3
    There is no other resource that is dependent of SQL Server besides the SQL agent. Other cluster groups and other cluster resources within the SQL Cluster groups come up online successfully. So only the SQL server and SQL server agent are not.

    The same logs are in the cluster.log file:

    I am new to this forum. I need help on my issue with SQL server not starting on one node of the cluster. I already checked the service user for both nodes and they are the same. In the event viewer, I see the following logs:

    [sqsrvres] checkODBCConnectError: sqlstate = 08001; native error = ffffffff; message = [Microsoft][SQL Native Client]An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.

    [sqsrvres] ODBC sqldriverconnect failed

    [sqsrvres] checkODBCConnectError: sqlstate = HYT00; native error = 0; message = [Microsoft][SQL Native Client]Login timeout expired

  4. #4
    Join Date
    Feb 2009
    Posts
    3
    Is there a way to increase the trace level for the errorlog? I'm just thinking that there could be other information before: "2009-02-12 03:47:35.29 spid12s Service Broker manager has shut down" if the trace level were higher.

  5. #5
    Join Date
    Feb 2004
    Location
    In front of the computer
    Posts
    15,579
    Provided Answers: 54
    The clue that you need is in
    Code:
    2009-02-12 03:44:04.88 spid12s The Service Broker protocol transport is disabled or not configured.
    Based on that message and nearby messages you can see that the Windows Service Login for this server doesn't have sufficient authority, and that this node probably isn't properly configured to support SQL Server.

    You really need to get an experienced SQL Server DBA to help you with fixing this problem. I almost never "take threads offline", but in this case that's exactly what I'm going to do... Check for a Private Message from me.

    -PatP

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •