Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AndreasMeyer
Starting Member
9 Posts |
 Posted - 2007-11-29 : 05:19:07
|
| 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 |
|
|
RickD
Slow But Sure Yak Herding Master
3608 Posts |
Posted - 2007-11-29 : 05:36:15
|
| Please go into your services and cgange the password in there. I know sometime this still keeps hold of the last password for some reason until you change it manually. |
 |
|
|
Arpan
Starting Member
3 Posts |
Posted - 2007-12-01 : 01:59:50
|
| Hi,Its not SQL Server problem, it is due to hardening of Operating system where your SQL server is installed. Ask system person, he can help you to release hardening restrictions. |
|
|
|
AndreasMeyer
Starting Member
9 Posts |
Posted - 2007-12-03 : 04:44:50
|
| 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.SincerelyAndreas |
|
|
|
AndreasMeyer
Starting Member
9 Posts |
Posted - 2008-01-10 : 07:48:25
|
| The problem re-occurred and is still not solved.I only thought it was.Sorry.Andreas |
|
|
|
|
|
|
|
|
SQLSERVERAGENT error when REstarting service