• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 734
  • Last Modified:

Random SQL Server 2005 SP2 service stop ?

Hi All,

I'm having problem with my SQL Server 2005 (Developer Edition) SP2 x64, it suddenly stop without no apparent reason, therefore i have to go to SS Config. mgr and then start it up manually everytime.

is there any Event viewer error that i should be aware of ?
at the moment the SQL Server (MSSQLServer) service is running under BUILTIN account\ Local System with AUTOMATIC start mode already set.

Any kind of suggestion and comments would be greatly appreciated.

Thanks
0
jjoz
Asked:
jjoz
  • 4
  • 2
2 Solutions
 
Raja Jegan RSQL Server DBA & ArchitectCommented:
Check out SQL Server Error Logs under SQL Server Agent in SSMS.
Also check for any errors in Event Viewer which captures any error messages
0
 
jjozAuthor Commented:
Here it is Jegan,

So far i could not find any obvious error message :-| apart from these two:

the SQL Agent error looks fine from here, could that be failed Windows Update (WSUS) at 3 AM stopped the SQL Service ?
Type:		Error
Date:		21/04/2010
Time:		2:13:04 PM
Event:		100
Source:		MSSQLServerADHelper
Category:	None
User:		N/A
Computer:	RSDB01
Description:
'0' is an invalid number of start up parameters. This service takes two start up parameters.
###############################################################################################
Type:		Error
Date:		27/04/2010
Time:		3:00:30 AM
Event:		1023
Source:		MsiInstaller
Category:	None
User:		\SYSTEM
Computer:	RSDB01
Description:
Product: Microsoft SQL Server 2005 (64-bit) - Update 'GDR 3080 for SQL Server Database Services 2005 (64-bit) ENU (KB970895)' could not be installed. Error code 1603. Additional information is available in the log file C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB970895_sqlrun_sql.msp.log.

Open in new window

SQL-Agent.jpg
0
 
pnautaCommented:
jjoz,

The MSSQLServerADHelper is not a dependancy, so it should not be a reason.  The SQL Agent again, could not be a reason.  SQLAgent will not start when SQLServer is not running, but again, the other way round is not a problem.

Your SQL log shows no errors that are fatal.  The only remark I have is that apparently not everything is at SP2 level (build 3042), as some are at build 4035 (SP3).

Next step would be to have a look at your event logs.  Maybe something or someone killed the process.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell┬« is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
jjozAuthor Commented:
yes, that could be it man.
let me upgrade all of the components to SP3 and see how it goes.
0
 
Raja Jegan RSQL Server DBA & ArchitectCommented:
Regret for the delay as I was in a short vacation..
Appplying SP3 with latest Cumulative updates might help you out.
Else let us know the startup accounts of SQL Server services and list of any major applications running in that server.. ( Resource intensive applications running in that machine can also be a cause for this).
0
 
jjozAuthor Commented:
yes it works man.
0
 
jjozAuthor Commented:
after installing SP3 now it works just fine :-)

Thanks guys.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now