November 29, 2007 at 3:26 am
Hello,
I have SQLServer2000.
A REstart of sqlserveragent does NOT work anymore. Then I receive the following message:
The SQLServerAgent 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.
The problem came about recently after I changed the password for the admin account that I use for the service and for some others.
I also changed the password for the sa user inside Enterprise Manager.
The error message didn't happen before.
Now it occurs on all three servers.
In Windows 2000 the error message is slightly different than on Windows Server 2003:
Could not start the SQLSERVERAGENT service on Local Computer.
The service did not return an error. This could be an internal Windows error or an internal service error. If the problem persists, contact your system administrator.
Stopping the SQLSERVERAGENT service first and then starting it DOES work (on all three servers), however.
How come?
Does anybody have an idea?
Thank you
November 29, 2007 at 2:38 pm
On the server, pull up the Services display. Find the SQLSERVERAGENT service, right-click, and select Properties.
Select the Log On tab
Is it logging on as a specific account? Did you change that account's password? Did you remember to change it here?
This is one of those 'Been here, done this, burned the T-Shirt' moments
December 3, 2007 at 2:47 am
Hi,
as so often, I found the remedy myself and submit it here for whoever runs into the problem hereafter:
I had jobs in SQL-Server scheduled that were authorized with the local user for whom I changed the password. On Restarting SQLSERVERAGENT it obviously checked the scheduled jobs and wether they ran under the user that was set for the SQLSERVERAGENT service.
The SQLSERVERAGENT service resists a restart until the password of this user has been updated on the jobs, too. A Restart of the service obviously checks whether they match.
As soon as I updated the password on the jobs, the restart worked again.
The funny thing was that when stopping and starting the service it would obviously not check on the passwords of the scheduled jobs and did start the service anyway.
Sincerely
Andreas
December 11, 2007 at 12:53 am
Hi,
the problem occurred again, so I did not have the solution after all.
Too bad.
If I find anything, I post it here.
December 12, 2007 at 4:14 am
Have you checked the SQL Server Errorlog, the SQL Agent Errorlog and the Windows System and Application Event Logs? Is there anything in these that could identify the problem.
Is SQL Agent running any jobs when it shuts down? SQL 2000 is a terror for saying its services have started or stopped before all required startup/shutdown work has completed. It may be that Agent is still completing its shutdown when it is given the startup command, and the new service instance fails because it detects an instance of Agent still running.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply