job result cancelled

I have a sql job that has recently started cancelling, on its own. I didn't
know this was possible. Under what conditions would the sql agent cancel a
job. I have no errors in the sql log, or event log, and an evening watching
memory counters in perfmon showed no problems there.
If the status of a job shows cancelled, that means the job was stopped
manually. What is that job executing? What is the job history saying?
"amill1" wrote:

> I have a sql job that has recently started cancelling, on its own. I didn't
> know this was possible. Under what conditions would the sql agent cancel a
> job. I have no errors in the sql log, or event log, and an evening watching
> memory counters in perfmon showed no problems there.
|||Yea, that's what I thought, but I know I am not getting up at 2 in the
morning and cancelling it in my sleep . The job is running multiple steps
to load summary tables for reporting. There are five steps total and most
nights it cancels somewhere around step 3. The job history says
"The step was cancelled (stopped) as the result of a stop job request. "
If I was answering this post I would say someone stopped it also, but no one
has the permission to do that other than myself.
"Jack" wrote:
[vbcol=seagreen]
> If the status of a job shows cancelled, that means the job was stopped
> manually. What is that job executing? What is the job history saying?
> "amill1" wrote:
|||There are 2 possibilities:
1> Someone is issuing sp_stop_job to that job from another schueduled job.
You probably need to use Profiler (use sp_trace_create if you don't want to
get up at 2 am to run it manually) to find out that information.
2> The SQLServerAgent service is being restarted every morning around that
time. Check Scheduled Tasks on that server.
"amill1" wrote:
[vbcol=seagreen]
> Yea, that's what I thought, but I know I am not getting up at 2 in the
> morning and cancelling it in my sleep . The job is running multiple steps
> to load summary tables for reporting. There are five steps total and most
> nights it cancels somewhere around step 3. The job history says
> "The step was cancelled (stopped) as the result of a stop job request. "
> If I was answering this post I would say someone stopped it also, but no one
> has the permission to do that other than myself.
>
> "Jack" wrote:
|||Thanks for the reply. I know that the SQL Agent is not getting restarted
because I have other jobs that run and complete during the time this job is
getting cancelled. I'll look for the sp_stop_job, but since I wrote all the
jobs and don't remember putting it there I don't think I'll find it. I
appreciate the suggestions.
"Jack" wrote:
[vbcol=seagreen]
> There are 2 possibilities:
> 1> Someone is issuing sp_stop_job to that job from another schueduled job.
> You probably need to use Profiler (use sp_trace_create if you don't want to
> get up at 2 am to run it manually) to find out that information.
> 2> The SQLServerAgent service is being restarted every morning around that
> time. Check Scheduled Tasks on that server.
> "amill1" wrote:
|||Go to the Advanced tab for the job steps and make sure you are fully logging
the execution. Also, in the job history, it will say who kicked the job
off. It will also tell you who cancelled the job.
Also take a look at the SQLAgent Error Log.
Sincerely,
Anthony Thomas

"amill1" <amill1@.discussions.microsoft.com> wrote in message
news:915304CB-882E-4168-BB24-BAF8F62F4CBA@.microsoft.com...
Thanks for the reply. I know that the SQL Agent is not getting restarted
because I have other jobs that run and complete during the time this job is
getting cancelled. I'll look for the sp_stop_job, but since I wrote all the
jobs and don't remember putting it there I don't think I'll find it. I
appreciate the suggestions.
"Jack" wrote:

> There are 2 possibilities:
> 1> Someone is issuing sp_stop_job to that job from another schueduled
job.
> You probably need to use Profiler (use sp_trace_create if you don't want
to
> get up at 2 am to run it manually) to find out that information.
> 2> The SQLServerAgent service is being restarted every morning around
that[vbcol=seagreen]
> time. Check Scheduled Tasks on that server.
> "amill1" wrote:
steps[vbcol=seagreen]
most[vbcol=seagreen]
"[vbcol=seagreen]
one[vbcol=seagreen]
saying?[vbcol=seagreen]
I didn't[vbcol=seagreen]
cancel a[vbcol=seagreen]
watching[vbcol=seagreen]