November 2, 2006 at 7:07 am
Hi, I have a situation on a w2k3 adv server cluster running 2 - sql2000 sp4 .2040 patched instances. Both instances have the exact same problem.
Basically the sql server agent scheduler is running but I cannot make any changes. If I go in and change the schedule say from 2 am to 3 am it will say the new schedule is 3 am but the next run date remains 2 am and sure enough the next day it runs at 2 am. Also when I right click a job and run it it gives no errors but it does not run ?? I also added a new job and it will not pick up as next run date and appears to not be scheduled.
This is occurring on both instances on the cluster. The sysjobs and sysjobhistory tables are getting updated and no where can I find an error??
Since we are in a production freeze stopping and starting the service is painful so hopefully it is something easy.
Any input would be helpful.
November 6, 2006 at 8:00 am
This was removed by the editor as SPAM
November 7, 2006 at 1:41 pm
I had exactly same experience as you have now.
It is most likely that you used a linked server. The SQL Server Agent had an invalid account or password. Although you might try to start the agent, it did not run in reality.
The way to check my guess is to use RDP or login the server locally. Start your SQL Server agent there. Reset the password accordingly if necessary. Then, modify your scheduled jobs.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply