SQL Server Agent Problem

26 Apr 2007 12:21 PM

Amos Soma

I have a number of scheduled jobs running on a server that normally run
without any problem. However, on occassion, like yesterday, they simply stop
running. The SQL Server agent is running and no errors are occuring anywhere
but the jobs simply don't fire off. For example, I have a job that contains
the following entry in msdb..sysjobschedules:

schedule_id      job_id
next_run_date   next_run_time
525                  FFA5089D-48EB-4A71-8269-0BF19DF59FC1     20070425
153000

You can see the job should have next fired yesterday at 3:30 pm, but it
never did. Also, it isn't just one job affected by this. It seems that most
jobs on the server have been affected. Yet, the SQL Server agent is running,
and, if I manually execute the jobs, they run fine.

Thanks for your help.

29 Apr 2007 11:26 PM

Sue Hoegemeier

What version of SQL Server and what service pack are you
running? If you are on 2000 and not up to date with service
packs, you should try applying the latest service pack.
Is there anything in the SQLAgent out file?

-Sue

On Thu, 26 Apr 2007 08:21:05 -0400, "Amos Soma"
<amos_j_s***@yahoo.com> wrote:

Show quote

>I have a number of scheduled jobs running on a server that normally run
>without any problem. However, on occassion, like yesterday, they simply stop
>running. The SQL Server agent is running and no errors are occuring anywhere
>but the jobs simply don't fire off. For example, I have a job that contains
>the following entry in msdb..sysjobschedules:
>
>schedule_id      job_id
>next_run_date   next_run_time
>525                  FFA5089D-48EB-4A71-8269-0BF19DF59FC1     20070425
>153000
>
>You can see the job should have next fired yesterday at 3:30 pm, but it
>never did. Also, it isn't just one job affected by this. It seems that most
>jobs on the server have been affected. Yet, the SQL Server agent is running,
>and, if I manually execute the jobs, they run fine.
>
>Thanks for your help.
>