Results 1 to 4 of 4
  1. #1
    Join Date
    Jan 2009
    Posts
    2

    Unanswered: Sql server resource fails to start on one node

    Hey all,

    New to these forums and I'm desperately searching for some answers to this problem I'm having. Recently setup a SQL 2005 failover cluster on a Windows Server 2008 (64bit) cluster with 2 nodes. Everything during the installation went fine, but regardless of how many times I've tried to install it, the SQL server resource always fails to start on one node. I've been doing some digging and found this in the SQL ERRORLOG of the node that always fails:

    2009-01-13 14:43:38.38 Server Microsoft SQL Server 2005 - 9.00.3042.00 (X64)
    Feb 10 2007 00:59:02
    Copyright (c) 1988-2005 Microsoft Corporation
    Enterprise Edition (64-bit) on Windows NT 6.0 (Build 6001: Service Pack 1)

    2009-01-13 14:43:38.38 Server (c) 2005 Microsoft Corporation.
    2009-01-13 14:43:38.38 Server All rights reserved.
    2009-01-13 14:43:38.38 Server Server process ID is 1284.
    2009-01-13 14:43:38.38 Server Authentication mode is WINDOWS-ONLY.
    2009-01-13 14:43:38.38 Server Logging SQL Server messages in file 'D:\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
    2009-01-13 14:43:38.38 Server This instance of SQL Server last reported using a process ID of 2852 at 1/13/2009 2:43:17 PM (local) 1/13/2009 9:43:17 PM (UTC). This is an informational message only; no user action is required.
    2009-01-13 14:43:38.38 Server Registry startup parameters:
    2009-01-13 14:43:38.38 Server -d D:\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
    2009-01-13 14:43:38.38 Server -e D:\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
    2009-01-13 14:43:38.38 Server -l D:\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
    2009-01-13 14:43:38.40 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2009-01-13 14:43:38.40 Server Detected 4 CPUs. This is an informational message; no user action is required.
    2009-01-13 14:43:38.40 Server Cannot use Large Page Extensions: lock memory privilege was not granted.
    2009-01-13 14:43:38.51 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-01-13 14:43:38.54 Server Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
    2009-01-13 14:43:38.62 spid1s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 37968, committed (KB): 121208, memory utilization: 31%.
    2009-01-13 14:43:39.64 Server Attempting to recover in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
    2009-01-13 14:43:39.64 Server Database mirroring has been enabled on this instance of SQL Server.
    2009-01-13 14:43:39.66 spid5s Starting up database 'master'.
    2009-01-13 14:43:39.72 spid5s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
    2009-01-13 14:43:39.72 spid5s SQL Trace ID 1 was started by login "sa".
    2009-01-13 14:43:39.74 spid5s Starting up database 'mssqlsystemresource'.
    2009-01-13 14:43:39.74 spid5s The resource database build version is 9.00.1399. This is an informational message only. No user action is required.
    2009-01-13 14:43:39.85 spid5s Server name is 'SQLCLUSTER'. This is an informational message only. No user action is required.
    2009-01-13 14:43:39.85 spid9s Starting up database 'model'.
    2009-01-13 14:43:39.85 spid5s The NETBIOS name of the local node that is running the server is 'OPTIMUS'. This is an informational message only. No user action is required.
    2009-01-13 14:43:39.86 spid9s Clearing tempdb database.
    2009-01-13 14:43:39.91 spid9s Starting up database 'tempdb'.
    2009-01-13 14:43:39.93 spid12s The Service Broker protocol transport is disabled or not configured.
    2009-01-13 14:43:39.93 spid12s The Database Mirroring protocol transport is disabled or not configured.
    2009-01-13 14:43:39.96 spid12s Service Broker manager has started.
    2009-01-13 14:43:39.96 Server A self-generated certificate was successfully loaded for encryption.
    2009-01-13 14:43:39.99 Server Server is listening on [ 10.44.128.184 <ipv4> 1433].
    2009-01-13 14:43:39.99 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
    2009-01-13 14:43:39.99 Server Server named pipe provider is ready to accept connection on [ \\.\pipe\$$\sqlcluster\sql\query ].
    2009-01-13 14:43:40.03 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-01-13 14:43:40.03 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
    2009-01-13 14:43:40.03 spid5s Starting up database 'msdb'.
    2009-01-13 14:43:40.07 spid5s Recovery of any in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC) has completed. This is an informational message only. No user action is required.
    2009-01-13 14:43:40.07 spid5s Recovery is complete. This is an informational message only. No user action is required.
    2009-01-13 14:44:32.58 Logon Error: 18456, Severity: 14, State: 11.
    2009-01-13 14:44:32.58 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.44.128.174]
    2009-01-13 14:44:32.58 Logon Error: 18456, Severity: 14, State: 11.
    2009-01-13 14:44:32.58 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.44.128.174]
    2009-01-13 14:44:32.58 Logon Error: 18456, Severity: 14, State: 11.

    It goes on to spam this and then finishes with:

    2009-01-13 14:44:55.16 spid12s Service Broker manager has shut down.
    2009-01-13 14:44:55.21 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-01-13 14:44:55.21 spid5s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.

    So I'm just wondering if anyone has any ideas as to why this is happening, or what I can possibly do to fix this and get it working. I even found an hour long webcast of a MS Professional doing this exact install on the same type of configuration, and I'm not doing anything differently than he is but still it continues to fail on this node. If anyone can help me out I'd greatly appreciate it.

  2. #2
    Join Date
    Jan 2003
    Location
    Massachusetts
    Posts
    5,800
    Provided Answers: 11
    The problem (as you probably already know) is with the Service Broker. the Database Engine has come up correctly. It looks to me that the Service Broker is attempting and failing to log in to the instance, and then giving up after a while (thus failing the whole instance). Have you removed the BUILTIN\ADMINISTRATORS group from the set of logins for the instance?

  3. #3
    Join Date
    Jan 2009
    Posts
    2
    No I haven't and honestly I'm not exactly sure how. I'm by no means an SQL guru, this project was dropped in my lap and I've basically just ran with it. I tried to connect to the SQL instance on the good node, and had no luck. It tells me my login failed, whether I use my domain account through windows authentication, or if I try to use the SQL sa account (I set it up with mixed mode authentication). I found some more information stating that the Windows server 2008 firewall may be causing this, but turning the firewall off hasn't helped either.

  4. #4
    Join Date
    Feb 2009
    Posts
    1
    Any luck with your SQL 2005 Cluster?

    I've exactly the same problem so i'm wondering if you have found an anwser?

Posting Permissions

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