SQL Agent Warning

Question

_{Friday, February 24, 2012 7:18 PM}

Can anyone help me with this warning message in the SQL server agent error logs?

[162] Internal request (from SetJobNextRunDate [reason: schedule will not run again]) to deactivate schedule 765

All replies (4)

_{Monday, February 27, 2012 6:25 AM ✅Answered}

Hi Amydom,

Please ensure you have updated the latest service pack in SQL Server. If you have configured End Date for this schedule, check if it is past due, extend the date will solve the problem.

This problem could also be caused by that you have created more than one Schedule with the same name from within the job step schedules New button. That seemed to confuse the Server Agent. After correcting it, the problem will be solved.

If it not helps, please provide more information such as provide the entire error log, how you got this error, is it running correct before and also the environment of your SQL Server(like version, edition).

Best Regards,
Iric
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

---

_{Friday, February 24, 2012 7:50 PM | 1 vote}

I suspect that the job schedule with a schedule_id of 765 is scheduled to run in the past.

You can check this via

SELECT q1.name AS job_name_to_check
FROM msdb.dbo.sysjobs q1, msdb.dbo.sysjobschedules q2
WHERE 1=1
AND q1.job_id=q2.job_id
AND q2.schedule_id = 765 

---

_{Friday, February 24, 2012 8:14 PM}

Thanks for the reply Kevin.  I am getting a jobname and it runs successfully. what should I do with it?

---

_{Friday, February 24, 2012 8:47 PM | 1 vote}

I'd suggest opening the job properties and having a look at its schedule(s).

As per the message, it is suggesting that you review the schedule as it doesn't look like it will run again. If this is the case, you can either do nothing, schedule the job to an appropriate time in the future, disable the schedule, or delete the schedule.

However before making changes to the schedule, it would be recommended to understand what/who created the schedule and why it was scheduled as it was. Not much else you can do.