April 5, 2006 at 8:15 am
I have a two node cluster. When I try to failover from active node which is node2 to node1 I get the following errors in the event viewer/ system logs
The MSSQLSERVER service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.
Timeout (30000 milliseconds) waiting for the MSSQLSERVER service to connect.
Cluster resource 'SQL Cluster Group Server Service' in Resource Group '006-PM2-DBASQL' failed.
SQL Server Error Logs dont show any error either execpt one which i think is unrelated to this issue:
2006-04-05 09:51:43.86 server Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
2006-04-05 09:51:43.86 server Copyright (C) 1988-2002 Microsoft Corporation.
2006-04-05 09:51:43.86 server All rights reserved.
2006-04-05 09:51:43.86 server Server Process ID is 5508.
2006-04-05 09:51:43.86 server Logging SQL Server messages in file 'S:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
2006-04-05 09:51:43.86 server SQL Server is starting at priority class 'normal'(1 CPU detected).
2006-04-05 09:51:44.00 server SQL Server configured for thread mode processing.
2006-04-05 09:51:44.08 server Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
2006-04-05 09:51:44.10 server Attempting to initialize Distributed Transaction Coordinator.
2006-04-05 09:51:46.97 spid3 Starting up database 'master'.
2006-04-05 09:51:47.11 server Using 'SSNETLIB.DLL' version '8.0.2039'.
2006-04-05 09:51:47.14 server SQL server listening on 10.14.200.155: 1433.
2006-04-05 09:51:47.16 spid5 Starting up database 'model'.
2006-04-05 09:51:47.16 spid3 Server name is '006-PM2-DBASQL'.
2006-04-05 09:51:47.18 spid8 Starting up database 'msdb'.
2006-04-05 09:51:47.21 spid9 Starting up database 'pubs'.
2006-04-05 09:51:47.21 spid10 Starting up database 'Northwind'.
2006-04-05 09:51:47.21 server SQL server listening on TCP, Shared Memory, Named Pipes.
2006-04-05 09:51:47.21 server SQL Server is ready for client connections
2006-04-05 09:51:47.21 spid11 Starting up database 'Workflow'.
2006-04-05 09:51:47.29 spid5 Clearing tempdb database.
2006-04-05 09:51:47.30 spid9 Starting up database 'Cube'.
2006-04-05 09:51:47.35 spid10 Starting up database 'SABADev2'.
2006-04-05 09:51:47.36 spid8 Starting up database 'WorkflowTest'.
2006-04-05 09:51:47.55 spid10 Starting up database 'WSS-Config'.
2006-04-05 09:51:47.79 spid5 Starting up database 'tempdb'.
2006-04-05 09:51:53.47 spid9 Analysis of database 'Cube' (8) is 100% complete (approximately 0 more seconds)
2006-04-05 09:51:53.63 spid3 Recovery complete.
2006-04-05 09:51:53.64 spid3 SQL global counter collection task is created.
2006-04-05 09:51:53.99 spid52 Using 'xpsqlbot.dll' version '2000.80.2039' to execute extended stored procedure 'xp_qv'.
2006-04-05 09:52:00.29 spid53 Using 'xpstar.dll' version '2000.80.2039' to execute extended stored procedure 'xp_sqlmaint'.
2006-04-05 09:52:01.25 backup Log backed up: Database: Northwind, creation date(time): 2000/08/06(01:41:00), first LSN: 23:419:1, last LSN: 23:421:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'S:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\TransactionLogs\Northwind_tlog_200604050952.TRN'}).
2006-04-05 09:52:01.49 spid54 Using 'xpstar.dll' version '2000.80.2039' to execute extended stored procedure 'sp_MSgetversion'.
2006-04-05 09:52:08.63 spid55 Error: 15457, Severity: 0, State: 1
2006-04-05 09:52:08.63 spid55 Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install..
2006-04-05 09:52:08.74 spid55 Using 'xplog70.dll' version '2000.80.2039' to execute extended stored procedure 'xp_msver'.
2006-04-05 09:53:34.49 spid54 Error: 15457, Severity: 0, State: 1
2006-04-05 09:53:34.49 spid54 Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install..
MSSQLServer and SQLServerAgent services are running under a system admin user account. What possibly could be the issue here?
Thanks
April 5, 2006 at 9:05 am
The most common cause of this in my experience has been when one of the files needed by sql server was not on a shared resource, and Sql Server, once failed to the other node, couldn't access it. Does this error occur when failing to either node, or only to one of them. In other words, if you fail it back to the origional node, does it still give this error?
If not, verify that the files being accessed can be seen by both nodes.
April 5, 2006 at 9:07 am
Ah, I had a link to a resource for this as well.......
http://support.microsoft.com/default.aspx?scid=kb;en-us;322140
April 5, 2006 at 9:19 am
can you tell me which file are you referring to?
April 5, 2006 at 9:22 am
Try one of these:
| • | The SQLServerAgent service startup account may not have the correct permissions on the folder that contains SQLAgent.out files. In this case, make sure that the specified SQLServerAgent service account has full control permissions to the folder in which the SQLAgent.out, SQLAgent.1, SQLAgent.2, and other SQL Server files are located. These files are typically stored in the LOG folder, which is in the SQL Server installation path. | ||||||||
| • | The SQL Server Agent error log may include a path or a file name that is not correct. In this case, verify that the path and file name for SQLAgent.out is valid:
| ||||||||
| • | Some executable .dll files may be corrupted or damaged. In this case, try starting SQL Server Agent from the command prompt by running the following command: Default Instance sqlagent -c -v Named Instance sqlagent -i[Instance Name] -c -v If you receive the following error message execution can't continue as the language resource file sqlagent.rll could not be loaded replace the SQLAgent.dll and SQLAgent.rll files with different copies of these files (SQLAgent.dll and SQLAgent.rll). | ||||||||
| • | The SQLServerAgent service startup account may not have the correct permissions to use the registry. In this case, make sure that the MSSQLSERVER startup account, the SQL Server Agent startup account, and the Microsoft Distributed Transaction Coordinator (MS DTC) startup account have full control of the following keys in the registry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSDTC The following keys are for the default instance: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSSQLSERVER HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlset\Services\SQLSERVERAGENT The following keys are for the named instance: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSSQL$<INSTANCE> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlset\Services\SQLAgent$<INSTANCE> Note The placeholder INSTANCE is replaced with the actual name of an instance of SQL Server. |
April 5, 2006 at 9:46 am
Issue was that one the second node domain account under which sql server service runs was not part of the local admin group.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply