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 |
|
BjornSamuels
Starting Member
2 Posts |
 Posted - 2004-12-28 : 16:44:05
|
| Although things to be set up fine and working swiftly and without hitch, the SQL Server Agent shuts off and won't start back up, and doens't seem to be leaving errors of any type to help narrow down what the problem is. This happens once every month or so.We're running SQL 2000 on Server 2003. SQL Server Agent is being run off of the System account. We have the option "Auto restart SQL Server Agent if it stops unexpectedly" checked.Has anyone else seen behavior similar to this? I seem to recall this happening periodically on our former SQL 2000/Server 2000 setup. |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2004-12-28 : 16:47:36
|
| >> doens't seem to be leaving errors Have you looked in nt event log and sql serever log?==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
|
BjornSamuels
Starting Member
2 Posts |
Posted - 2004-12-28 : 16:59:46
|
| Correct; no errors in the NT logs aside from one warning from the last day it was running: "SuperSocket info: (SpnRegister) : Error 1355", but from what I've read that's nothing to get worked up over. Nothing in the alerts or logs in SQL either that raises an eyebrow. Unless there's somewhere else that I should be looking, then it seems fairly kosher. |
|
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2004-12-28 : 17:50:26
|
| Is SQL Server also running as the System account, or as an AD user? If it's running as an AD user, try setting up the Agent service to use the same service.MeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
|
|
|
Wanderer
Master Smack Fu Yak Hacker
1168 Posts |
Posted - 2004-12-29 : 04:09:12
|
| As Derrick says - it sounds like an account the might need to be set to never expire? Alternatively, does this happen after a reboot? I've seen some cases where the user seems to "lose" the "run as service" rights, which means that the service will not start. Simply re-apply the userid and password in the services, on the properties tab, seems to resolve that - I am still trying to find the proper resolution for this, but since it only happens on my Sandbox, it doesn't have any priority. Our server guy seems to think he has a link as to why this might be happeneing (in our case).*##* *##* *##* *##* Chaos, Disorder and Panic ... my work is done here! |
|
|
|
|
|
|
|
|
SQL Server Agent beef