MS SQL Server - SQL Server job is not running on schedule

Author

SQL Server job is not running on schedule

Demian

2005-06-03, 1:23 pm

I have come accross a bit of a mystery with an SQL Server 2000 job schedule.

I have many jobs scheduled to run every night that run perfectly. However,
there is one job that does not run. As far as I can tell, the job is set up
exactly like the other ones. I would like the job to run a stored procedure
nightly at 10:30 pm.

Here is what I've checked so far:
1. The "Enabled" check box is selected on the General tab.
2. The "Enabled" check box is selected on the Edit Job Schedule tab.
3. There is no end date on the schedule.
4. SQL Server Agent is running properly because many other jobs are running
each night.

Does anyone have any other suggestions for how I can troubleshoot this?

Thanks.

Wojtek Garwol

2005-06-03, 8:23 pm

"Demian" <Demian@discussions.microsoft.com> wrote in message
news:90B512F8-6C8C-4D23-8FCB- EAE40CCCE3CB@microso
ft.com...
> Here is what I've checked so far:
> 1. The "Enabled" check box is selected on the General tab.
> 2. The "Enabled" check box is selected on the Edit Job Schedule tab.
> 3. There is no end date on the schedule.
> 4. SQL Server Agent is running properly because many other jobs are
> running
> each night.
>
> Does anyone have any other suggestions for how I can troubleshoot this?

Check "Next run date" in EM, hit "Refresh job" first - what does it say?

Regards
Wojtek

Demian

2005-06-03, 8:23 pm

Thanks for the reply.

It says (6/3/2005 22:30:00) in the Next Run Date column.

"Wojtek Garwol" wrote:

> "Demian" <Demian@discussions.microsoft.com> wrote in message
> news:90B512F8-6C8C-4D23-8FCB- EAE40CCCE3CB@microso
ft.com...
>
> Check "Next run date" in EM, hit "Refresh job" first - what does it say?
>
> Regards
> Wojtek
>
>
>

Wojtek Garwol

2005-06-04, 7:23 am

So it should run then. What does the "View job history" say?

Regards
Wojtek

"Demian" <Demian@discussions.microsoft.com> wrote in message
news:8FBBB9E8-5AA1-4086-9018- 9C02B98FA7FD@microso
ft.com...[color=darkred]
> Thanks for the reply.
>
> It says (6/3/2005 22:30:00) in the Next Run Date column.
>
> "Wojtek Garwol" wrote:
>

Edgardo Valdez, MCSD, MCDBA

2005-06-04, 11:23 am

Try right clicking on the job and selecting Job History. It will tell you if
the job ran , the result, notifications a duration. If the job is running, it
will show up there.

You could also try to add an Output File, which will tell the output of the
job step, in a text file, if the file is on the path you selected, that means
it woks. You can add an output file by opening the job, select the Steps tab,
double click on the first step (1) and select the Advanced output, the select
the box that have the Output File, you can even browse for the location.

"Demian" wrote:

> I have come accross a bit of a mystery with an SQL Server 2000 job schedule.
>
> I have many jobs scheduled to run every night that run perfectly. However,
> there is one job that does not run. As far as I can tell, the job is set up
> exactly like the other ones. I would like the job to run a stored procedure
> nightly at 10:30 pm.
>
> Here is what I've checked so far:
> 1. The "Enabled" check box is selected on the General tab.
> 2. The "Enabled" check box is selected on the Edit Job Schedule tab.
> 3. There is no end date on the schedule.
> 4. SQL Server Agent is running properly because many other jobs are running
> each night.
>
> Does anyone have any other suggestions for how I can troubleshoot this?
>
> Thanks.
>
>
>

Anthony Thomas

2005-06-05, 3:23 am

You should also check the Next Run datetime in SQLEM and make sure that SQL
Agent is actually scheduling it to run and that it seems reasonable.

You should also check both the SQL Agent and SQL Server error logs for
anything suspicious.

Sincerely,

Anthony Thomas

--

<Edgardo Valdez>; <MCSD>; "MCDBA"
< EdgardoValdezMCSDMCD
BA@discussions.microsoft.com> wrote in message
news:9FF1695C-4A7A-4A42-B825- 27F94FAF3F8F@microso
ft.com...
Try right clicking on the job and selecting Job History. It will tell you if
the job ran , the result, notifications a duration. If the job is running,
it
will show up there.

You could also try to add an Output File, which will tell the output of the
job step, in a text file, if the file is on the path you selected, that
means
it woks. You can add an output file by opening the job, select the Steps
tab,
double click on the first step (1) and select the Advanced output, the
select
the box that have the Output File, you can even browse for the location.

"Demian" wrote:

> I have come accross a bit of a mystery with an SQL Server 2000 job
schedule.
>
> I have many jobs scheduled to run every night that run perfectly.
However,
> there is one job that does not run. As far as I can tell, the job is set
up
> exactly like the other ones. I would like the job to run a stored
procedure
> nightly at 10:30 pm.
>
> Here is what I've checked so far:
> 1. The "Enabled" check box is selected on the General tab.
> 2. The "Enabled" check box is selected on the Edit Job Schedule tab.
> 3. There is no end date on the schedule.
> 4. SQL Server Agent is running properly because many other jobs are
running
> each night.
>
> Does anyone have any other suggestions for how I can troubleshoot this?
>
> Thanks.
>
>
>

Quentin Ran

2005-06-22, 8:23 pm

Demian,

you certainly can compare this job to another that is similar to it and runs
properly. Script both jobs and compare the script. See anything different.

It is possible that the data got corrupted. If it is not too complicated,
and your comparison does not yield anything new for you, you can just
recreate the job.

hth

Quentin

"Demian" <Demian@discussions.microsoft.com> wrote in message
news:90B512F8-6C8C-4D23-8FCB- EAE40CCCE3CB@microso
ft.com...
>I have come accross a bit of a mystery with an SQL Server 2000 job
>schedule.
>
> I have many jobs scheduled to run every night that run perfectly.
> However,
> there is one job that does not run. As far as I can tell, the job is set
> up
> exactly like the other ones. I would like the job to run a stored
> procedure
> nightly at 10:30 pm.
>
> Here is what I've checked so far:
> 1. The "Enabled" check box is selected on the General tab.
> 2. The "Enabled" check box is selected on the Edit Job Schedule tab.
> 3. There is no end date on the schedule.
> 4. SQL Server Agent is running properly because many other jobs are
> running
> each night.
>
> Does anyone have any other suggestions for how I can troubleshoot this?
>
> Thanks.
>
>
>

Sponsored Links