October 29, 2010 at 3:33 pm
We need to rebuild some drives, so I moved the system databases and error logs etc from 1 drive to another. Everything seemed ok, but I think I must have made some mistake , perhaps with log or error files (SQLAGENT.OUT ...), because SQL SERVER AGENT won't start now. I can't see anything wrong. What's the most likely "oops" that I might have done ?
SQL itself seems fine as far as system & user databases.
2005, SP3
October 29, 2010 at 4:31 pm
presume the old agent log location no longer exists? Did you change the location for the agent errorlog?
USE msdb
GO
EXEC msdb.dbo.sp_set_sqlagent_properties @errorlog_file=N'<New_Errorlog_Location>\SQLAGENT.OUT'
GO
---------------------------------------------------------------------
October 29, 2010 at 6:03 pm
Perfect ! Thanks !
Is that what I should have done earlier, or would there have been a better process at the time ?
October 30, 2010 at 3:22 am
glad that fixed it.
Its the prescribed way to move agent log and yes should have been part of your migration plan. You would have had to time it to be done when the old location was no more and before the next sqlagent start.
---------------------------------------------------------------------
November 3, 2010 at 9:00 am
Wow, this is priceless, I've just reset the agent error log in two of our servers on which the sql server agent services misteriously refused to start. And now both worked!
Thanks very much to george sibbald!
Bazinga!
November 3, 2010 at 9:24 am
bills in the post 🙂
---------------------------------------------------------------------
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply