October 21, 2010 at 4:00 am
Hello gents
Version is 9.0.3042, standard edition with SP2, sql server database engine service is running fun but the agent just can't be started by either configuration manager or services.msc snapshot.
Also I tried to change the service account from right now a domain user account to Localsystem, it failed too.
I am local admin on this box and also the sysadmin on the instance.
Any ideas?
Thanks in advance!
Bazinga!
October 21, 2010 at 4:07 am
Also an interesting error message:
The SQL Server Agent (MSSQLSERVER) service on local computer started and then stopped. Some services stop automatically if they have no work to do, for example, the Performance Logs and Alerts service.
Bazinga!
October 21, 2010 at 5:29 am
People are going to lynch me for this first question, but...
When was the last time you rebooted the box?
Has SQL Server Agent run before on this box or is it a new install?
If the prior, what's changed on the box recently? Patches (for any software), hardware, new installs, configurations?
October 21, 2010 at 5:43 am
Brandie Tarvin (10/21/2010)
People are going to lynch me for this first question, but...When was the last time you rebooted the box?
Has SQL Server Agent run before on this box or is it a new install?
If the prior, what's changed on the box recently? Patches (for any software), hardware, new installs, configurations?
Thanks very muc for your input, just have a look at all system event with ID 1074, this box was rebooted 6 months ago.
And I am not sure if it was running before I took it over on my new postition here.
Really can't trace what have happened inside this box since then anymore.
Any other thoughts that I can borrow a bit more?
Bazinga!
October 21, 2010 at 5:56 am
Check the Application and System logs in Event Viewer. That might help you track down the source of the issue.
Is this a standalone server or a clustered node?
Is this a production box?
October 21, 2010 at 6:02 am
I've seen this happen before where the location for the SQL Server Agent log file doesn't have the right permissions on it or doesn't exist.
John
October 21, 2010 at 6:32 am
Brandie Tarvin (10/21/2010)
Check the Application and System logs in Event Viewer. That might help you track down the source of the issue.Is this a standalone server or a clustered node?
Is this a production box?
It is a standalone production server and in the application log when the restart failed I can find:
Event Type:Information
Event Source:SQLSERVERAGENT
Event Category:Service Control
Event ID:102
Date:21-10-2010
Time:12:10:55
User:N/A
Computer:*****
Description:
SQLServerAgent service successfully stopped.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Bazinga!
October 21, 2010 at 7:01 am
But do you see other errors before that which might be connected to the restart fail?
John makes a good point about the log file. Find out what service SQL Agent uses, then locate the file location of the SQL Agent log. Make sure that the service account has permissions on the root folder and that those perms go all the way down to the log folder without being denied along the way.
October 21, 2010 at 7:19 am
Brandie Tarvin (10/21/2010)
But do you see other errors before that which might be connected to the restart fail?John makes a good point about the log file. Find out what service SQL Agent uses, then locate the file location of the SQL Agent log. Make sure that the service account has permissions on the root folder and that those perms go all the way down to the log folder without being denied along the way.
Thanks for your input again.
And yes, that "service successfully stop" message is the only error log i got from my restart action.
I am going to find the SQL Server agent log file and see its security settings.
Bazinga!
October 21, 2010 at 1:38 pm
Most likely this is a permissions issue of the SQL Agent startup account. Check if there are any entries in the Agent Log
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
November 3, 2010 at 9:04 am
Hello everyone who replied to this post, I can't say I found the definitive solution, but at least it is one of the ways you can try out, which is to reset the sql agent error log file location in msdb database and restart it again.
Related scripts are as follows:
sp_configure 'show advanced options', 1;
GO
RECONFIGURE;
GO
sp_configure 'Agent XPs', 1;
GO
RECONFIGURE with override
GO
USE msdb
GO
EXEC msdb.dbo.sp_set_sqlagent_properties @errorlog_file=N'D:\Programs\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLAGENT.OUT'
GO
Bazinga!
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply