error 1053 when try to start mssqlserver service

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
You could try either trace flag 3607 or 3608. See http://support.microsoft.com/kb/224071/en-us for
some info.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"shahab" <shahab@.discussions.microsoft.com> wrote in message
news:329CA91B-6855-4F1F-B69F-B972163804C2@.microsoft.com...
>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

error 1053 when try to start mssqlserver service

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] L
ock
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\Nort
hwind_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?
ThanksYou could try either trace flag 3607 or 3608. See http://support.microsoft.com/kb/
224071/en-us for
some info.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"shahab" <shahab@.discussions.microsoft.com> wrote in message
news:329CA91B-6855-4F1F-B69F-B972163804C2@.microsoft.com...
>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 connec
t.
> 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: 14
33.
> 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 Memor
y,
> Named Pipes.
> 2006-04-05 09:51:47.21 server SQL Server is ready for client connection
s
> 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.203
9'
> 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=DIS
K:
> {'S:\Program Files\Microsoft SQL
> Server\MSSQL\BACKUP\TransactionLogs\Nort
hwind_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

error 1053 when try to start mssqlserver service

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?
ThanksYou could try either trace flag 3607 or 3608. See http://support.microsoft.com/kb/224071/en-us for
some info.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"shahab" <shahab@.discussions.microsoft.com> wrote in message
news:329CA91B-6855-4F1F-B69F-B972163804C2@.microsoft.com...
>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

error : 18452 in clustering; very urgent

We have 2 failover servers and one client in our test environment. We have all the three configured in mixed mode authentication(windows + sql server authentication). But when we are failing over from 1st server to 2nd one, we are getting the following error message,
'Unable to connected to server xxxx: Server : Msg 18452, Level 16, State 1 [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'null'. Reason: Not associated with a trusted SQL server connection.'

I got some clue.

For instance we have ser1 and ser2 as clusters. I registered both in the client's EM. Now what I did was, I made ser1 to run and stopped sql service in ser2 (active/passive) through failover. Now in the client's EM I'm able to open ser1 and I cannot access ser2. Now what I did was, I failed over to ser2 ( so sql service in ser1 is stopped). But now I can still be able to access ser1 and also I can access ser2, even I'm able to open query analyzer in ser1 through EM.But when I try to open query analyzer directly, it is giving the same error message. ser1 is the virtual name given to both ser1 and ser2. So I think when connecting through EM, failover is occuring fine.I'm just wondering why is this happening only with dsn. Can anybody help me?

You can get this particular error in a number of scenarios -- the common scenario is when one attempts SQL authentication using an NT login account. If the system is unable to find the login account it will raise this error. It is not clear the scenario behind this error.

|||The information you provided is not sufficient to diagnose the problem. Do you get this error only after failover? If you start the SQL Server serive on node ser2 (using net start and not via cluster admin) do you still get the same error when the client is also running on node2? Do you get this error only when the client is running on a different node than the SQL Server?
The error will be raised when SQL authentication is tried using an NT login account and it seems like the system is not able to find the login account. Make sure you are using the same account to connect after failover.