July 1, 2010 at 8:44 am
Strange one at least to me. SQL Server and agent will not start on boot. The SQL Server Service manager shows both set to Auto Start.
The services are set to automatic in the services manager.
When I start the services manually they start up with no errors.
The Event Viewers-Application logs show no SQL server messages during reboot.
Below is from SQL server log
2010-06-30 18:18:47.31 server Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
2010-06-30 18:18:47.31 server Copyright (C) 1988-2002 Microsoft Corporation.
2010-06-30 18:18:47.31 server All rights reserved.
2010-06-30 18:18:47.31 server Server Process ID is 4200.
2010-06-30 18:18:47.31 server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
2010-06-30 18:18:47.32 server SQL Server is starting at priority class 'normal'(4 CPUs detected).
2010-06-30 18:18:47.39 server SQL Server configured for thread mode processing.
2010-06-30 18:18:47.40 server Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
2010-06-30 18:18:47.49 server Attempting to initialize Distributed Transaction Coordinator.
2010-06-30 18:18:48.81 spid3 Starting up database 'master'.
2010-06-30 18:18:48.98 server Using 'SSNETLIB.DLL' version '8.0.2039'.
2010-06-30 18:18:48.98 spid5 Starting up database 'model'.
2010-06-30 18:18:48.98 spid3 Server name is 'MYSERVER'.
2010-06-30 18:18:48.98 spid8 Starting up database 'msdb'.
2010-06-30 18:18:48.98 spid9 Starting up database 'pubs'.
2010-06-30 18:18:48.98 spid10 Starting up database 'Northwind'.
2010-06-30 18:18:48.98 spid11 Starting up database 'MyprodDatabase'.
2010-06-30 18:18:51.32 server SQL server listening on 192.168.1.150: 1433.
2010-06-30 18:18:51.32 server SQL server listening on 127.0.0.1: 1433.
2010-06-30 18:18:51.40 spid5 Clearing tempdb database.
2010-06-30 18:18:51.45 server SQL server listening on TCP, Shared Memory, Named Pipes.
2010-06-30 18:18:51.45 server SQL Server is ready for client connections
2010-06-30 18:18:51.48 spid5 Starting up database 'tempdb'.
2010-06-30 18:18:52.49 spid3 Recovery complete.
2010-06-30 18:18:52.49 spid3 SQL global counter collection task is created.
2010-06-30 18:19:23.01 spid51 Using 'xpsqlbot.dll' version '2000.80.2039' to execute extended stored procedure 'xp_qv'.
2010-07-01 02:00:01.03 spid55 Using 'xpstar.dll' version '2000.80.2039' to execute extended stored procedure 'xp_sqlmaint'.
July 1, 2010 at 9:33 am
Have you checked the System/Security logs for messages?
Agent typically won't start if the db engine doesn't, so worry about SQL Server relational engine.
Follow me on Twitter: http://www.twitter.com/way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
July 1, 2010 at 9:54 am
Thanks Steve!
Yes agent is dependent on server so I am focused on server.
The security log is clean.
2 notable entries in System
http://support.microsoft.com/kb/938449
We can log on to the domain so we are ignoring as per the kb.
http://support.microsoft.com/kb/830092
Event ID: 29
Source: W32time
Type: Error
The time provider NtpClient is configured to acquire time from one or more time sources. However, none of the sources are currently accessible. No attempt to contact a source will be made for 15 minutes. NtpClient has no source of accurate time.
July 2, 2010 at 10:04 am
This is resolved. I had to reset the service accounts through enterprise manager, not sure what caused this. thanks all.
July 2, 2010 at 10:17 am
Thanks for the update.
Someone must have changed something for the service, or the AD accounts.
Follow me on Twitter: http://www.twitter.com/way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply