May 21, 2009 at 4:02 am
Hello,
Apologies if this has already been posted but I cannot find it anywhere. My SQL server and SQL agents will not start on both nodes in my Active / Active SQL 2005 SP3 x64 Enterprise cluster on Windows 2008 Enterprise SP1 x64 after applying KB958644 which is the conficker patch. This is the second time I have built the cluster and I tested it and it worked perfectly prior to applying the KB. Has anyone seen this issue before and do they have a fix? Basically not patching the 2 servers is a no go and I have already patched 2 separate clusters with KB958644 and they worked fine, those clusters were W2k3 R2 SP2 2 node with SQL 2005 SP2 and Windows 2008 Enterprise File and Print cluster with 5 nodes.
Whats happening is all the services on both nodes come online except SQL server and sql agent. The are all connected to EMC2 sans via fibre channell cable on HP DL380 G5 with 32 gb RAM and 2 x Quad core 3 ghz CPUs. When I look in cluster event log I get the following errors:
event ID 1069: Cluster resource 'Cluster Disk 5' in clustered service or application 'Cluster Group' failed.
and Cluster resource 'SQL Server (servername1)' in clustered service or application 'clusterservicename' failed.
In the event viewer on Windows 2008 I get these 3 errors:
event id: 19019 [sqsrvres] OnlineThread: Error 1 bringing resource online. (more info in code)
event id: 19019 [sqsrvres] OnlineThread: service stopped while waiting for QP.
event id: [sqsrvres] CheckServiceAlive: Service is dead
I got the above error with KB958644 installed and as I said before the cluster was working perfectly prior to the patch. I tried uninstalling the patch but the same error happens above. I need to get this working with the patch installed otherwise I will have to recommend going back to Windows 2003. If anyone can shed some light on this I would appreciate it and if you require any more information please let me know.
I have also noticed that the sql server and sql agent services are not started in SSCM on the active node and when I try to manually start them I get the same 3 error messages as above:
event id: 19019 [sqsrvres] OnlineThread: Error 1 bringing resource online. (more info in code)
event id: 19019 [sqsrvres] OnlineThread: service stopped while waiting for QP.
event id: [sqsrvres] CheckServiceAlive: Service is dead
I guess my next question is due to the lack of response, Does anyone have the same setup above with KB958644 installed and working? thanks Bruce
May 21, 2009 at 8:15 am
What does the SQL Server error log show when you try to start the instance?
May 21, 2009 at 8:50 am
2009-05-21 15:41:28.15 Server Microsoft SQL Server 2005 - 9.00.4035.00 (X64)
Nov 24 2008 16:17:31
Copyright (c) 1988-2005 Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 6.0 (Build 6001: Service Pack 1)
2009-05-21 15:41:28.15 Server (c) 2005 Microsoft Corporation.
2009-05-21 15:41:28.15 Server All rights reserved.
2009-05-21 15:41:28.15 Server Server process ID is 5212.
2009-05-21 15:41:28.15 Server Authentication mode is WINDOWS-ONLY.
2009-05-21 15:41:28.15 Server Logging SQL Server messages in file 'H:\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2009-05-21 15:41:28.15 Server This instance of SQL Server last reported using a process ID of 1808 at 5/21/2009 3:09:47 PM (local) 5/21/2009 2:09:47 PM (UTC). This is an informational message only; no user action is required.
2009-05-21 15:41:28.15 Server Registry startup parameters:
2009-05-21 15:41:28.15 Server -d H:\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2009-05-21 15:41:28.15 Server -e H:\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2009-05-21 15:41:28.15 Server -l H:\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2009-05-21 15:41:28.16 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2009-05-21 15:41:28.16 Server Detected 8 CPUs. This is an informational message; no user action is required.
2009-05-21 15:41:28.16 Server Cannot use Large Page Extensions: lock memory privilege was not granted.
2009-05-21 15:41:28.25 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-05-21 15:41:28.28 Server Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2009-05-21 15:41:28.36 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): 40932, committed (KB): 187776, memory utilization: 21%.
2009-05-21 15:41:30.51 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-05-21 15:41:30.51 Server Database mirroring has been enabled on this instance of SQL Server.
2009-05-21 15:41:30.52 spid4s Starting up database 'master'.
2009-05-21 15:41:30.58 spid4s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2009-05-21 15:41:30.63 spid4s SQL Trace ID 1 was started by login "sa".
2009-05-21 15:41:30.63 spid4s Starting up database 'mssqlsystemresource'.
2009-05-21 15:41:30.64 spid4s The resource database build version is 9.00.1399. This is an informational message only. No user action is required.
2009-05-21 15:41:30.85 spid9s Starting up database 'model'.
2009-05-21 15:41:30.85 spid4s Server name is 'CLWVL003\CARELIVE'. This is an informational message only. No user action is required.
2009-05-21 15:41:30.85 spid4s The NETBIOS name of the local node that is running the server is 'CLW-SQL-002'. This is an informational message only. No user action is required.
2009-05-21 15:41:30.93 spid9s Clearing tempdb database.
2009-05-21 15:41:31.04 Server A self-generated certificate was successfully loaded for encryption.
2009-05-21 15:41:31.05 spid9s Starting up database 'tempdb'.
2009-05-21 15:41:31.07 Server Server is listening on [ 10.157.95.195 61059].
2009-05-21 15:41:31.09 Server Server is listening on [ 10.157.95.195 1433].
2009-05-21 15:41:31.09 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\CARELIVE ].
2009-05-21 15:41:31.09 Server Server named pipe provider is ready to accept connection on [ \\.\pipe\$$\clwvcarsql003\MSSQL$careLive\sql\query ].
2009-05-21 15:41:31.10 spid12s The Service Broker protocol transport is disabled or not configured.
2009-05-21 15:41:31.10 spid12s The Database Mirroring protocol transport is disabled or not configured.
2009-05-21 15:41:31.12 spid12s Service Broker manager has started.
2009-05-21 15:41:31.12 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2009-05-21 15:41:31.13 spid4s Starting up database 'msdb'.
2009-05-21 15:41:31.17 spid4s 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-05-21 15:41:31.17 spid4s Recovery is complete. This is an informational message only. No user action is required.
2009-05-21 15:41:31.32 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:31.32 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:31.33 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:31.33 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:31.33 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:31.33 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:31.34 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:31.34 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:31.34 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:31.34 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:31.34 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:31.34 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:31.35 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:31.35 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:31.35 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:31.35 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:31.35 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:31.35 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:31.36 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:31.36 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:31.36 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:31.36 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:33.37 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:33.37 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:33.37 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:33.37 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:33.37 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:33.37 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:33.38 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:33.38 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:33.38 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:33.38 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:33.38 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:33.38 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:33.39 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:33.39 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:33.39 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:33.39 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:33.40 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:33.40 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:33.40 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:33.40 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:33.40 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:33.40 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:35.41 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:35.41 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:35.41 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:35.41 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:35.41 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:35.41 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:35.42 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:35.42 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:35.42 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:35.42 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:35.42 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:35.42 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:35.43 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:35.43 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:35.43 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:35.43 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:35.43 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:35.43 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:35.44 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:35.44 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:35.44 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:35.44 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:37.45 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:37.45 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:37.45 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:37.45 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:37.45 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:37.45 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:37.46 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:37.46 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:37.46 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:37.46 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:37.46 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:37.46 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:37.47 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:37.47 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:37.47 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:37.47 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:37.48 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:37.48 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:37.48 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:37.48 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:37.48 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:37.48 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:39.49 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:39.49 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:39.49 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:39.49 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:39.49 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:39.49 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:39.50 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:39.50 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:39.50 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:39.50 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:39.51 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:39.51 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:39.51 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:39.51 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:39.51 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:39.51 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:39.52 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:39.52 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:39.52 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:39.52 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:39.52 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:39.52 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:41.53 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:41.53 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:41.53 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:41.53 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:41.54 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:41.54 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:41.54 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:41.54 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:41.54 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:41.54 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:41.55 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:41.55 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:41.55 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:41.55 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:41.55 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:41.55 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:41.56 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:41.56 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:41.56 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:41.56 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:41.56 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:41.56 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:43.57 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:43.57 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:43.57 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:43.57 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:43.57 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:43.57 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:43.58 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:43.58 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:43.58 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:43.58 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:43.59 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:43.59 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:43.59 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:43.59 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:43.59 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:43.59 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:43.60 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:43.60 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:43.60 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:43.60 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:43.60 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:43.60 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:45.61 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:45.61 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:45.61 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:45.61 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:45.61 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:45.61 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:45.62 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:45.62 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:45.62 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:45.62 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:45.62 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:45.62 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:45.63 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:45.63 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:45.63 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:45.63 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:45.64 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:45.64 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:45.64 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:45.64 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:45.64 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:45.64 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:47.65 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:47.65 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:47.65 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:47.65 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:47.65 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:47.65 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:47.66 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:47.66 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:47.66 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:47.66 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:47.66 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:47.66 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:47.67 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:47.67 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:47.67 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:47.67 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:47.67 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:47.67 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:47.68 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:47.68 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:47.68 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:47.68 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:49.69 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:49.69 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:49.69 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:49.69 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:49.69 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:49.69 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:49.70 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:49.70 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:49.70 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:49.70 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:49.70 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:49.70 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:49.71 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:49.71 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:49.71 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:49.71 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:49.71 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:49.71 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:49.72 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:49.72 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:49.72 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:49.72 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:51.72 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:51.72 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:51.73 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:51.73 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:51.73 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:51.73 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:51.74 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:51.74 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:51.74 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:51.74 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:51.74 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:51.74 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:51.75 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:51.75 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:51.75 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:51.75 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:51.75 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:51.75 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:51.76 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:51.76 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:51.76 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:51.76 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:53.80 spid12s Service Broker manager has shut down.
2009-05-21 15:41:53.82 spid4s 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-05-21 15:41:53.82 spid4s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
May 21, 2009 at 11:22 am
That error log looks as though SQL Server has started up successfully, but for some reason the Cluster software thinks it hasn't.
The cluster software continually connects to the SQL Instance every second or so to verify that it is running. It looks very much like these lines
2009-05-21 15:41:51.74 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.198]
2009-05-21 15:41:51.74 Logon Error: 18456, Severity: 14, State: 11.
are the cluster software trying to connect and failing.
These lines show what ports SQL Server is listening on.
2009-05-21 15:41:31.07 Server Server is listening on [ 10.157.95.195 61059].
2009-05-21 15:41:31.09 Server Server is listening on [ 10.157.95.195 1433].
2009-05-21 15:41:31.09 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\CARELIVE ].
2009-05-21 15:41:31.09 Server Server named pipe provider is ready to accept connection on [ \\.\pipe\$$\clwvcarsql003\MSSQL$careLive\sql\query ].
The cluster software will use whatever is configured using the SQL Server 2005 Network Configuration tool. Has anybody set up a client alias forcing a different port or blocked named pipes or blocked the relevant TCP ports etc etc.
May 21, 2009 at 10:07 pm
Looking at the log file - there are no user databases mentioned. This suggests to me that SQL Server has not gotten to point where it is ready for use (I am not even sure that it finished recovering msdb)
My recollection of the out of the box configuration of SQL Server clustering is that the cluster resource needs to make a positive response to a "ping" (which for SQL Server I think is something like SELECT @@VERSION). If a positive response is not received after 30 seconds, then the cluster software decides that the cluster resouce is no longer operating correctly and it fails over to another node in the cluster.
I am not sure what screen you need to use but I suggest that you try to find where (in Cluster Adminstrator) you can change the timeout. Try increasing it (perhaps to 120 seconds for now) and then start the service.
May 22, 2009 at 1:28 am
First of all thank you very much for responding Ian Scarlett, i have posted this same issue up on Experts Exchange and no one has responded yet, i am in to day 2. The sql cluster I have setup is brand new so there will be no live databases in there just yet. I am obviously reluctant to hand over the cluster to the developers until it fails over and fails back and all the services start. This was happening before I put this damn conficker patch on but my organisation will not allow un patched servers as we got hit with the virus a few weeks ago.
RE: The cluster software will use whatever is configured using the SQL Server 2005 Network Configuration tool. Has anybody set up a client alias forcing a different port or blocked named pipes or blocked the relevant TCP ports etc etc. Yes i did add tcp port number 1433 in SQL Network Conf Man tool under protocols for (instance name) > IP addresses TAB > scroll to the bottom and where it says tcp i added in 1433 manually. I only put this in there because if i open up sql management studio i cannot connect and i found this fix on a website. Should i take this setting out?
May 22, 2009 at 1:33 am
thanks for your post happycat59, this is a brand new fresh install of W2k8 and sql 2005 and until I'm happy with the cluster i will not hand it over to our sql dbas and developers, so your right there is no DBs on it just yet.
RE: I am not sure what screen you need to use but I suggest that you try to find where (in Cluster Adminstrator) you can change the timeout. Try increasing it (perhaps to 120 seconds for now) and then start the service I will have a look around to try and find this setting and give this a go.
once again thanks for posting.
May 22, 2009 at 2:25 am
But I can't help thinking, why was the cluster working fine before I put the patch on?
May 22, 2009 at 2:31 am
Before looking at ports etc, are you sure that the Cluster Services account has the relevant permissions to allow it to connect to SQL Server. These are the lines that concern me.
2009-05-21 15:41:51.74 Logon Error: 18456, Severity: 14, State: 11.
2009-05-21 15:41:51.74 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [
I suspect this is the cluster service trying to connect, but failing. I wouldn't have expected it to connect as an anonymous user.
If you can't see anything obvious, try logging on to one of the nodes as the cluster user, and see if you can connect to SQL Server using SSMS (you may have to grant the Cluster service account permissions to log on interactively first).
I don't have access to a cluster at the moment to check anything out and give you exact instructions.
May 22, 2009 at 3:09 am
Hi Ian, Windows 2008 Cluster uses local system account to run the cluster service. It is recommended that you use this account on the cluster service, I have tried changing this and granting the account the appropriate permissions (there are about 7 or so) in secpol (local security policy) on the servers but it had no effect, i could start the service but could not start the sql services on the cluster. also i can start the sql services in servcies.msc but i cannot start them in SQL SCM
The other thing i noticed with the conficker patch is I couldn't even install sql on the cluster if i had the servers patched, the sql install would run through the installation and then right at the last part of installing it would fail with red x and the error, the installation was cancelled by the user. It took me quite a while to find out why this was happening and I eventually found a website saying that when sql installs components onto a second node it uses task scheduler to do so and then it clicked that I had the servers in an OU that had the GPO to disable task scheduler (as per MS instructions) and also the conficker patch. So i reversed the GPO and uninstalled the patch and voila the sql cluster installed beautifully. I then proceeded to setup my sql resource groups in W2k8 and allocated the appropriate storage, i setup MSDTC, i failed over the cluster and failed it back many many times and it worked a treat. I then suspected that the conficker patch would break things again if i reapplied it but i have no choice in the matter its a necessity that our servers are patched with this. I put the patch on and low and behold the services won't start. There has to be a work around to this somewhere...... thanks again Ian for trying to help me out hopefully we can resolve this.
May 22, 2009 at 3:34 am
If the service starts successfully from services.msc, then it is definitely an issue with the cluster service being able to connect to SQL Server.
Where did you read that the Local System account was reccommended?
The Local System account has no rights to access anything off the box, so wouldn't be able to access SQL Server if it was running on the other node.
The cluster service must use a domain user account, which should be made a member of the sysadmin group in SQL Server.
EDIT
Just spotted that you are on Windows Server 2008, so ignore what I've just said above about the local system account.
Have you removed BUILTIN\Administrators from SQL Server?
If you have, you will need to add NT AUTHORITY\SYSTEM as a 'sysadmin' to SQL Server.
May 22, 2009 at 3:51 am
here is one link: http://technet.microsoft.com/en-us/magazine/cc672627.aspx
about half way down the page:
Enhanced Security Features
Failover Clusters feature several new security enhancements. Perhaps the most significant involves the removal of the requirement for a Cluster Service Account (CSA). In previous versions of the Microsoft Cluster Service, a domain user account was required during the configuration process. This account, which was used to start the cluster service, was added to the local administrators group on each node of the cluster and given the required local user rights to allow the cluster service to function properly. As a domain user account, the CSA was subject to a number of domain-level policies that could be applied to cluster nodes. These policies could adversely impact high availability by causing the cluster service to fail.
The cluster service now runs under a local system account with a specific set of rights on the local cluster node that allows it to function properly. The security context for the cluster has transitioned to the Cluster Name Object (CNO), which is the computer object that is created, by default, in the Computers container in Active Directory® when the cluster is first created. Once a cluster is successfully created and the CNO exists in Active Directory, the user account that was used to install and configure the cluster is no longer needed.
Additional computer objects created in Active Directory in the Computers container are associated with a Failover Cluster. These objects, called Virtual Computer Objects (VCOs), equate to cluster Network Name resources that are created as part of Client Access Points (CAPs) in the cluster. The CNO, which is responsible for creating all VCOs in a cluster, is added to the System Access Control List (SACL) for the object in Active Directory
May 22, 2009 at 3:52 am
sorry just got your edited post ignore my reply
May 22, 2009 at 3:54 am
re: Have you removed BUILTIN\Administrators from SQL Server?
If you have, you will need to add NT AUTHORITY\SYSTEM as a 'sysadmin' to SQL Server.
I have not done this, i will give this a shot....
May 22, 2009 at 4:05 am
when I try an add NT AUTHORITY\SYSTEM to the sysadmin role in sql server user provisioning i get the error:
a network-related or instance-specific error occured while establishing a connection to sql server. the server was not found or was not accessible. verfiy the instance name is correct and that sql is configured to allow remote connections. (provider: sql network interfaces, error: 26 - error locating server/instance specified)
is this because the services are not running? thanks Ian
Viewing 15 posts - 1 through 15 (of 21 total)
You must be logged in to reply to this topic. Login to reply