February 20, 2007 at 5:09 am
Hi
For 15 days now my SQL server service is terminating with the following error
MSSQLSERVER service terminated unexpectedly. It has done this 2 Time(s).
This service terminates and restarts automatically and sometimes doesnt restart we have to mannuly start it again.
Event ID: 7034.
Version Details
Version: MSSQL Server 2000
Service Pack: 3a
Build: 8.0.0.760
I have checked many forums most of them suggest to apply the latest service pack. But the same error has been reported by sites having SP4 also.
Kindly help.
Thank you
wasim
February 20, 2007 at 5:42 am
sql server doesn't normally stop and restart without some kind of message. What is reported in the event and sql logs?
Do you have any dmp files created, they'll be in the same folder as your sql server logs ( unless you've redirected output )
I assume this is a server ?
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/
February 20, 2007 at 6:06 am
Hi
No logs with the error reference are there nor any dmp files. Below is the the contents of the file at the time when this occured. We are running
MSSQL Server 2000 (Standard Edition)
Service Pack: 3a
OS: Windows Server 2003
Log is as below
2007-02-19 21:12:51.25 server Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: )
2007-02-19 21:12:51.25 server Copyright (C) 1988-2002 Microsoft Corporation.
2007-02-19 21:12:51.25 server All rights reserved.
2007-02-19 21:12:51.25 server Server Process ID is 4312.
2007-02-19 21:12:51.25 server Logging SQL Server messages in file 'G:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
2007-02-19 21:12:51.25 server SQL Server is starting at priority class 'normal'(4 CPUs detected).
2007-02-19 21:12:51.89 server SQL Server configured for thread mode processing.
2007-02-19 21:12:51.89 server Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
2007-02-19 21:12:51.97 server Attempting to initialize Distributed Transaction Coordinator.
2007-02-19 21:12:54.16 spid3 CreateRecEvent failed: 5
2007-02-19 21:12:54.16 spid3 Starting up database 'master'.
2007-02-19 21:12:54.27 spid3 0 transactions rolled back in database 'master' (1).
2007-02-19 21:12:54.27 spid3 Recovery is checkpointing database 'master' (1)
2007-02-19 21:12:54.33 server Using 'SSNETLIB.DLL' version '8.0.766'.
2007-02-19 21:12:54.33 spid5 Starting up database 'model'.
2007-02-19 21:12:54.33 spid3 Server name is 'ES-PROD'.
2007-02-19 21:12:54.36 spid8 Starting up database 'msdb'.
2007-02-19 21:12:54.36 spid9 Starting up database 'pubs'.
2007-02-19 21:12:54.36 spid10 Starting up database 'Northwind'.
2007-02-19 21:12:54.36 spid11 Starting up database 'JDE9'.
2007-02-19 21:12:54.36 spid12 Starting up database 'JDE_PY9'.
2007-02-19 21:12:54.36 spid17 Starting up database 'JDE_PRODUCTION'.
2007-02-19 21:12:54.36 spid15 Starting up database 'JDE_PRISTINE'.
2007-02-19 21:12:54.36 spid18 Starting up database 'JDE_DV9'.
2007-02-19 21:12:54.36 spid16 Starting up database 'JDE_PD9'.
2007-02-19 21:12:54.36 spid19 Starting up database 'JDE_DEVELOPMENT'.
2007-02-19 21:12:54.36 spid13 Starting up database 'JDE_CRP'.
2007-02-19 21:12:54.36 spid20 Starting up database 'JDE_EURO'.
2007-02-19 21:12:54.36 spid21 Starting up database 'DATAOFCRP'.
2007-02-19 21:12:54.36 spid14 Starting up database 'JDE_JD9'.
2007-02-19 21:12:54.52 server SQL server listening on TCP, Named Pipes.
2007-02-19 21:12:54.52 server SQL Server is ready for client connections
2007-02-19 21:12:54.58 spid5 Clearing tempdb database.
2007-02-19 21:12:54.59 spid8 1 transactions rolled forward in database 'msdb' (4).
2007-02-19 21:12:54.59 spid19 Analysis of database 'JDE_DEVELOPMENT' (15) is 100% complete (approximately 0 more seconds)
2007-02-19 21:12:54.59 spid8 0 transactions rolled back in database 'msdb' (4).
2007-02-19 21:12:54.61 spid14 Analysis of database 'JDE_JD9' (10) is 100% complete (approximately 0 more seconds)
2007-02-19 21:12:54.59 spid19 Recovery of database 'JDE_DEVELOPMENT' (15) is 0% complete (approximately 14 more seconds) (Phase 2 of 3).
2007-02-19 21:12:54.64 spid13 Analysis of database 'JDE_CRP' (9) is 100% complete (approximately 0 more seconds)
2007-02-19 21:12:54.64 spid13 Recovery of database 'JDE_CRP' (9) is 0% complete (approximately 20 more seconds) (Phase 2 of 3).
2007-02-19 21:12:54.64 spid8 Recovery is checkpointing database 'msdb' (4)
2007-02-19 21:12:54.64 spid19 Recovery of database 'JDE_DEVELOPMENT' (15) is 100% complete (approximately 0 more seconds) (Phase 2 of 3).
2007-02-19 21:12:54.64 spid19 2 transactions rolled forward in database 'JDE_DEVELOPMENT' (15).
2007-02-19 21:12:54.66 spid19 0 transactions rolled back in database 'JDE_DEVELOPMENT' (15).
2007-02-19 21:12:54.67 spid19 Recovery is checkpointing database 'JDE_DEVELOPMENT' (15)
2007-02-19 21:12:54.72 spid13 Recovery of database 'JDE_CRP' (9) is 100% complete (approximately 0 more seconds) (Phase 2 of 3).
2007-02-19 21:12:54.72 spid13 12 transactions rolled forward in database 'JDE_CRP' (9).
2007-02-19 21:12:54.78 spid13 0 transactions rolled back in database 'JDE_CRP' (9).
2007-02-19 21:12:54.80 spid13 Recovery is checkpointing database 'JDE_CRP' (9)
2007-02-19 21:12:54.91 spid5 Starting up database 'tempdb'.
2007-02-19 21:12:55.08 spid17 Analysis of database 'JDE_PRODUCTION' (13) is 100% complete (approximately 0 more seconds)
2007-02-19 21:12:55.08 spid17 Recovery of database 'JDE_PRODUCTION' (13) is 0% complete (approximately 14 more seconds) (Phase 2 of 3).
2007-02-19 21:12:55.83 spid16 758 transactions rolled forward in database 'JDE_PD9' (12).
2007-02-19 21:12:55.87 spid11 Analysis of database 'JDE9' (7) is 100% complete (approximately 0 more seconds)
2007-02-19 21:12:55.87 spid11 Recovery of database 'JDE9' (7) is 0% complete (approximately 10 more seconds) (Phase 2 of 3).
2007-02-19 21:12:56.02 spid18 Analysis of database 'JDE_DV9' (14) is 100% complete (approximately 0 more seconds)
2007-02-19 21:12:56.03 spid18 Recovery of database 'JDE_DV9' (14) is 0% complete (approximately 6 more seconds) (Phase 2 of 3).
2007-02-19 21:12:56.03 spid16 0 transactions rolled back in database 'JDE_PD9' (12).
2007-02-19 21:12:56.14 spid16 Recovery is checkpointing database 'JDE_PD9' (12)
2007-02-19 21:12:56.59 spid17 Recovery of database 'JDE_PRODUCTION' (13) is 100% complete (approximately 0 more seconds) (Phase 2 of 3).
2007-02-19 21:12:56.59 spid17 1819 transactions rolled forward in database 'JDE_PRODUCTION' (13).
2007-02-19 21:12:56.89 spid17 0 transactions rolled back in database 'JDE_PRODUCTION' (13).
2007-02-19 21:12:56.95 spid17 Recovery is checkpointing database 'JDE_PRODUCTION' (13)
2007-02-19 21:12:57.41 spid11 Recovery of database 'JDE9' (7) is 100% complete (approximately 0 more seconds) (Phase 2 of 3).
2007-02-19 21:12:57.41 spid11 900 transactions rolled forward in database 'JDE9' (7).
2007-02-19 21:12:57.44 spid11 0 transactions rolled back in database 'JDE9' (7).
2007-02-19 21:12:57.50 spid11 Recovery is checkpointing database 'JDE9' (7)
2007-02-19 21:12:58.31 spid21 Analysis of database 'DATAOFCRP' (17) is 100% complete (approximately 0 more seconds)
February 20, 2007 at 7:52 am
I would look at the windows event log first, then the sql log files, typically here: C:\Program Files\Microsoft SQL Server\MSSQL\LOG.
You will probably find a disk write issue.
[font="Arial"]Clifton G. Collins III[/font]
February 20, 2007 at 12:51 pm
hmm .. and nothing in the windows event logs?
When the server is up have you done a sweep of checkdb etc.
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply