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 |
|
svicky9
Posting Yak Master
232 Posts |
 Posted - 2005-11-20 : 02:36:49
|
| hi friends When i restarted my sql server the sql server service did not start.I went to administrative tools and services then tried starting the MSSQL Service but it come up with the following error " MSSSQL server service on the Local computer started and then stopped.Some services stop automatically if they have no work to do,for example the performance logs and alerts services" what could be the errors?ThanksVicky |
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2005-11-20 : 10:57:17
|
| Did you look in the application event log and system event log to see if there were any other errors?MeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
 |
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2005-11-20 : 21:57:26
|
quote:
from BOL If you are running SQLServerAgent in an account other than a Windows NT 4.0 or Windows 2000 domain account, the following will occur: CmdExec and ActiveScripting steps of jobs owned by nonsysadmins will fail.The autorestart features in SQLServerAgent will not work.On-idle job schedules will not allow the job to run. For best results, use a Windows NT 4.0 or Windows 2000 domain account that has sufficient permissions across the domain to access information necessary for SQL Server Agent job execution. You can change the SQLServerAgent service account to a non-Windows NT 4.0 administrator account. However, the Windows NT 4.0 account must be a member of the sysadmin fixed server role to run SQL Server Agent.
HTH--------------------keeping it simple... |
|
|
|
AnnF
Starting Member
1 Post |
Posted - 2005-12-01 : 18:03:45
|
| did you ever resolve this? If so, what fixed it? I am having the same problem. Thanks! |
|
|
|
AndreasMeyer
Starting Member
9 Posts |
Posted - 2007-11-29 : 05:08:29
|
| Hello,I have almost the same problem.A REstart of sqlserveragent does NOT work. Then I receive the same 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.Stopping it and then starting it DOES work, however.How come?Does anybody have an idea?Thank you |
|
|
|
Xgirl451
Starting Member
2 Posts |
Posted - 2009-10-01 : 16:00:52
|
| Because there wasn't an answer here, this is what worked for us.During the course of upgrade from windows server 2000 to window server 2003, the sqlagent.exe exhibited the behavior described.The agent was stopping because we used a domain acount as a connection to sql server had its priveleges changed. When I changed the SQL Server connection to a user with with SA priveleges, the agent started running again. This is changed in the SQL Server Agent Properties Dialog box on the Connection tabThe start and immediate stop can be caused by either the user in the connection tab losing permisions or, if SQL Server Authentication is used, a password being changed. |
|
|
|
|
|
|
|
|
Service Error