Error 1068 Can't start SQLSERVERAGENT and MSSQLSERVER

I was rebuilding my index and my system admin rebooted the system without
shutting down the database first. After the reboot the SQLSERVERAGENT and
MSSQLSERVER services won't start and I received ERROR 1068:The dependency
service or group failed to start error while trying to start the two services.
In the Enterprise Manger screen I saw:
Connection failed, check SQL Server Registration Properties
I am not sure how to fix this problem. Can I rebuild my SQL Server
registery, and if so, how? Please advise. Thanks in advance.
Hi,
Could you please open the SQL server errorlog in program files\microsoft sql
server\log folder and investigate more on this error.
Thanks
Hari
MCDBA
"Ling" wrote:

> I was rebuilding my index and my system admin rebooted the system without
> shutting down the database first. After the reboot the SQLSERVERAGENT and
> MSSQLSERVER services won't start and I received ERROR 1068:The dependency
> service or group failed to start error while trying to start the two services.
> In the Enterprise Manger screen I saw:
> Connection failed, check SQL Server Registration Properties
> I am not sure how to fix this problem. Can I rebuild my SQL Server
> registery, and if so, how? Please advise. Thanks in advance.
|||There's only one line in the errorlog:
2004-09-22 11:28:07.03 server The system is older than SQL Server 7.0 RTM
version and is not supported by this server
"Hari Prasad" wrote:
[vbcol=seagreen]
> Hi,
> Could you please open the SQL server errorlog in program files\microsoft sql
> server\log folder and investigate more on this error.
> Thanks
> Hari
> MCDBA
>
> "Ling" wrote:
|||What exact messages do you get if you from a DOS prompt type below?
NET START MSSQLSERVER
(Adjust server name of it is a named instance.)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Ling" <Ling@.discussions.microsoft.com> wrote in message
news:F823DF33-6210-4E2D-AA98-37E2FEFD1659@.microsoft.com...
> I was rebuilding my index and my system admin rebooted the system without
> shutting down the database first. After the reboot the SQLSERVERAGENT and
> MSSQLSERVER services won't start and I received ERROR 1068:The dependency
> service or group failed to start error while trying to start the two services.
> In the Enterprise Manger screen I saw:
> Connection failed, check SQL Server Registration Properties
> I am not sure how to fix this problem. Can I rebuild my SQL Server
> registery, and if so, how? Please advise. Thanks in advance.

Error 1068 Can't start SQLSERVERAGENT and MSSQLSERVER

On manually starting SQLSERVERAGENT service, it gives the following
error:
error 1068: The depending service for group failed to start.
Can anybody tell me how to restart these SQLSERVERAGENT and MSSQLSERVER
services.
Thanks,
misecprj
Start > Run > services.msc > SLSERVERAGENT > Properties > Dependencies
See which dependant services are not running.
"misecprj@.hotmail.com" wrote:

> On manually starting SQLSERVERAGENT service, it gives the following
> error:
> error 1068: The depending service for group failed to start.
> Can anybody tell me how to restart these SQLSERVERAGENT and MSSQLSERVER
> services.
> Thanks,
> misecprj
>
|||Hi
In the services applet in control panel you can view the dependencies of a
service and start the services as well. Make sure that you are logged into an
account that has permissions to start services.
John
"misecprj@.hotmail.com" wrote:

> On manually starting SQLSERVERAGENT service, it gives the following
> error:
> error 1068: The depending service for group failed to start.
> Can anybody tell me how to restart these SQLSERVERAGENT and MSSQLSERVER
> services.
> Thanks,
> misecprj
>

Error 1068 Can't start SQLSERVERAGENT and MSSQLSERVER

On manually starting SQLSERVERAGENT service, it gives the following
error:
error 1068: The depending service for group failed to start.
Can anybody tell me how to restart these SQLSERVERAGENT and MSSQLSERVER
services.
Thanks,
misecprjStart > Run > services.msc > SLSERVERAGENT > Properties > Dependencies
See which dependant services are not running.
"misecprj@.hotmail.com" wrote:

> On manually starting SQLSERVERAGENT service, it gives the following
> error:
> error 1068: The depending service for group failed to start.
> Can anybody tell me how to restart these SQLSERVERAGENT and MSSQLSERVER
> services.
> Thanks,
> misecprj
>|||Hi
In the services applet in control panel you can view the dependencies of a
service and start the services as well. Make sure that you are logged into a
n
account that has permissions to start services.
John
"misecprj@.hotmail.com" wrote:

> On manually starting SQLSERVERAGENT service, it gives the following
> error:
> error 1068: The depending service for group failed to start.
> Can anybody tell me how to restart these SQLSERVERAGENT and MSSQLSERVER
> services.
> Thanks,
> misecprj
>

Error 1068 Can't start SQLSERVERAGENT and MSSQLSERVER

On manually starting SQLSERVERAGENT service, it gives the following
error:
error 1068: The depending service for group failed to start.
Can anybody tell me how to restart these SQLSERVERAGENT and MSSQLSERVER
services.
Thanks,
misecprjStart > Run > services.msc > SLSERVERAGENT > Properties > Dependencies
See which dependant services are not running.
"misecprj@.hotmail.com" wrote:
> On manually starting SQLSERVERAGENT service, it gives the following
> error:
> error 1068: The depending service for group failed to start.
> Can anybody tell me how to restart these SQLSERVERAGENT and MSSQLSERVER
> services.
> Thanks,
> misecprj
>|||Hi
In the services applet in control panel you can view the dependencies of a
service and start the services as well. Make sure that you are logged into an
account that has permissions to start services.
John
"misecprj@.hotmail.com" wrote:
> On manually starting SQLSERVERAGENT service, it gives the following
> error:
> error 1068: The depending service for group failed to start.
> Can anybody tell me how to restart these SQLSERVERAGENT and MSSQLSERVER
> services.
> Thanks,
> misecprj
>

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 1001

Hi,
Is anyone aware when this error comes in sql server?
Error 1001: Cannot start service MSSQLSERVER.An instance of the server is
already running.
regards,
Harshal."harshal mistry" <harshal_in@.hotmail.com> wrote in message
news:%23t%23ufwv9EHA.3368@.TK2MSFTNGP10.phx.gbl...
> Hi,
> Is anyone aware when this error comes in sql server?
> Error 1001: Cannot start service MSSQLSERVER.An instance of the server is
> already running.
> regards,
> Harshal.
>
This error means that the MSSQLServer service is already running and you are
trying to start it again. What are you doing when this error occurs?
You may have your SQL Server set up to start automatically when the computer
restarts. If you then run a program or a command-line utility that issues
a NET START MSSQLServer command, you will get this error.
HTH
Rick Sawtell
MCT, MCSD, MCDBA|||thanks for the reply... from the error I had guessed it, but since it is
happening at a clients place so I don't have the details yet.
He was trying to start the MSDE setup when the error occured...
thanks
harshal.
"Rick Sawtell" <quickening@.msn.com> wrote in message
news:%23SE36bx9EHA.220@.TK2MSFTNGP09.phx.gbl...
> "harshal mistry" <harshal_in@.hotmail.com> wrote in message
> news:%23t%23ufwv9EHA.3368@.TK2MSFTNGP10.phx.gbl...
is[vbcol=seagreen]
> This error means that the MSSQLServer service is already running and you
are
> trying to start it again. What are you doing when this error occurs?
> You may have your SQL Server set up to start automatically when the
computer
> restarts. If you then run a program or a command-line utility that
issues
> a NET START MSSQLServer command, you will get this error.
> HTH
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>

Error 1001

Hi,
Is anyone aware when this error comes in sql server?
Error 1001: Cannot start service MSSQLSERVER.An instance of the server is
already running.
regards,
Harshal.
"harshal mistry" <harshal_in@.hotmail.com> wrote in message
news:%23t%23ufwv9EHA.3368@.TK2MSFTNGP10.phx.gbl...
> Hi,
> Is anyone aware when this error comes in sql server?
> Error 1001: Cannot start service MSSQLSERVER.An instance of the server is
> already running.
> regards,
> Harshal.
>
This error means that the MSSQLServer service is already running and you are
trying to start it again. What are you doing when this error occurs?
You may have your SQL Server set up to start automatically when the computer
restarts. If you then run a program or a command-line utility that issues
a NET START MSSQLServer command, you will get this error.
HTH
Rick Sawtell
MCT, MCSD, MCDBA
|||thanks for the reply... from the error I had guessed it, but since it is
happening at a clients place so I don't have the details yet.
He was trying to start the MSDE setup when the error occured...
thanks
harshal.
"Rick Sawtell" <quickening@.msn.com> wrote in message
news:%23SE36bx9EHA.220@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> "harshal mistry" <harshal_in@.hotmail.com> wrote in message
> news:%23t%23ufwv9EHA.3368@.TK2MSFTNGP10.phx.gbl...
is
> This error means that the MSSQLServer service is already running and you
are
> trying to start it again. What are you doing when this error occurs?
> You may have your SQL Server set up to start automatically when the
computer
> restarts. If you then run a program or a command-line utility that
issues
> a NET START MSSQLServer command, you will get this error.
> HTH
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>

Error 1001

Hi,
Is anyone aware when this error comes in sql server?
Error 1001: Cannot start service MSSQLSERVER.An instance of the server is
already running.
regards,
Harshal."harshal mistry" <harshal_in@.hotmail.com> wrote in message
news:%23t%23ufwv9EHA.3368@.TK2MSFTNGP10.phx.gbl...
> Hi,
> Is anyone aware when this error comes in sql server?
> Error 1001: Cannot start service MSSQLSERVER.An instance of the server is
> already running.
> regards,
> Harshal.
>
This error means that the MSSQLServer service is already running and you are
trying to start it again. What are you doing when this error occurs?
You may have your SQL Server set up to start automatically when the computer
restarts. If you then run a program or a command-line utility that issues
a NET START MSSQLServer command, you will get this error.
HTH
Rick Sawtell
MCT, MCSD, MCDBA|||thanks for the reply... from the error I had guessed it, but since it is
happening at a clients place so I don't have the details yet.
He was trying to start the MSDE setup when the error occured...
thanks
harshal.
"Rick Sawtell" <quickening@.msn.com> wrote in message
news:%23SE36bx9EHA.220@.TK2MSFTNGP09.phx.gbl...
> "harshal mistry" <harshal_in@.hotmail.com> wrote in message
> news:%23t%23ufwv9EHA.3368@.TK2MSFTNGP10.phx.gbl...
> > Hi,
> >
> > Is anyone aware when this error comes in sql server?
> >
> > Error 1001: Cannot start service MSSQLSERVER.An instance of the server
is
> > already running.
> >
> > regards,
> >
> > Harshal.
> >
> >
> This error means that the MSSQLServer service is already running and you
are
> trying to start it again. What are you doing when this error occurs?
> You may have your SQL Server set up to start automatically when the
computer
> restarts. If you then run a program or a command-line utility that
issues
> a NET START MSSQLServer command, you will get this error.
> HTH
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>

Error ?

Hi,
any ideas on this error '?
Event Type: Information
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
Date: 23-10-2003
Time: 21:45:44
User: N/A
Computer: LX1SQL004
Description:
Error: 17883, Severity: 1, State: 0
The Scheduler 0 appears to be hung. SPID 68, ECID 0, UMS Context 0x03843DE8 Data:
0000: db 45 00 00 01 00 00 00 =DBE.....
0008: 0a 00 00 00 4c 00 58 00 ...L.X.
0010: 31 00 53 00 51 00 4c 00 1.S.Q.L.
0018: 30 00 30 00 34 00 00 00 0.0.4...
0020: 00 00 00 00 ...
Thanks in advance
Miguel CorreiaHave a look at this KB article
http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B810885
--
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org
"Miguel" <cmlcorreia@.netcabo.pt> wrote in message
news:084c01c39a1c$c9a680c0$a501280a@.phx.gbl...
Hi,
any ideas on this error '?
Event Type: Information
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
Date: 23-10-2003
Time: 21:45:44
User: N/A
Computer: LX1SQL004
Description:
Error: 17883, Severity: 1, State: 0
The Scheduler 0 appears to be hung. SPID 68, ECID 0, UMS
Context 0x03843DE8
Data:
0000: db 45 00 00 01 00 00 00 ÛE.....
0008: 0a 00 00 00 4c 00 58 00 ...L.X.
0010: 31 00 53 00 51 00 4c 00 1.S.Q.L.
0018: 30 00 30 00 34 00 00 00 0.0.4...
0020: 00 00 00 00 ...
Thanks in advance
Miguel Correia|||Thanks a lot :)
>--Original Message--
>Have a look at this KB article
>http://support.microsoft.com/default.aspx?scid=3Dkb%3Ben-us%
3B810885
>-- >
>Allan Mitchell (Microsoft SQL Server MVP)
>MCSE,MCDBA
>www.SQLDTS.com
>I support PASS - the definitive, global community
>for SQL Server professionals - http://www.sqlpass.org
>
>
>"Miguel" <cmlcorreia@.netcabo.pt> wrote in message
>news:084c01c39a1c$c9a680c0$a501280a@.phx.gbl...
>Hi,
>any ideas on this error '?
>Event Type: Information
>Event Source: MSSQLSERVER
>Event Category: (2)
>Event ID: 17052
>Date: 23-10-2003
>Time: 21:45:44
>User: N/A
>Computer: LX1SQL004
>Description:
>Error: 17883, Severity: 1, State: 0
>The Scheduler 0 appears to be hung. SPID 68, ECID 0, UMS
>Context 0x03843DE8
>Data:
>0000: db 45 00 00 01 00 00 00 =DBE.....
>0008: 0a 00 00 00 4c 00 58 00 ...L.X.
>0010: 31 00 53 00 51 00 4c 00 1.S.Q.L.
>0018: 30 00 30 00 34 00 00 00 0.0.4...
>0020: 00 00 00 00 ...
>
>Thanks in advance
>Miguel Correia
>
>.
>