Job Failure

From the job history, we find that a scheduled job has failed after we have
updated the structure of some tables.
We would like to know what is the best way to find out what causes the
failure ? Is there any built-in error log ?
ThanksJason,
In SQLAgent, right click the job and select View Job History..., tick
the show step details checkbox at the top right. Navigate to the step
that failed and the error message should present itself in the bottom pane.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Jason wrote:
> From the job history, we find that a scheduled job has failed after we have
> updated the structure of some tables.
> We would like to know what is the best way to find out what causes the
> failure ? Is there any built-in error log ?
> Thanks
>|||The job is written by consultant. From memory, the message is something
like "It takes xx second to finish Task 1. It takes yy seconds to finish
Task 2. ...... Job failed".
Jason
"Mark Allison" <mark@.no.tinned.meat.mvps.org> wrote in message
news:eMd$pWqYFHA.580@.TK2MSFTNGP15.phx.gbl...
> Jason,
> In SQLAgent, right click the job and select View Job History..., tick the
> show step details checkbox at the top right. Navigate to the step that
> failed and the error message should present itself in the bottom pane.
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602m.html
>
>
> Jason wrote:
>> From the job history, we find that a scheduled job has failed after we
>> have updated the structure of some tables.
>> We would like to know what is the best way to find out what causes the
>> failure ? Is there any built-in error log ?
>> Thanks|||"Show step details" checkbox. This is essential!
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Jason" <anonymous@.discussions.microsoft.com> wrote in message
news:OtaCYYqYFHA.1028@.TK2MSFTNGP10.phx.gbl...
> The job is written by consultant. From memory, the message is something like "It takes xx second
> to finish Task 1. It takes yy seconds to finish Task 2. ...... Job failed".
> Jason
> "Mark Allison" <mark@.no.tinned.meat.mvps.org> wrote in message
> news:eMd$pWqYFHA.580@.TK2MSFTNGP15.phx.gbl...
>> Jason,
>> In SQLAgent, right click the job and select View Job History..., tick the show step details
>> checkbox at the top right. Navigate to the step that failed and the error message should present
>> itself in the bottom pane.
>> --
>> Mark Allison, SQL Server MVP
>> http://www.markallison.co.uk
>> Looking for a SQL Server replication book?
>> http://www.nwsu.com/0974973602m.html
>>
>>
>> Jason wrote:
>> From the job history, we find that a scheduled job has failed after we have updated the
>> structure of some tables.
>> We would like to know what is the best way to find out what causes the failure ? Is there any
>> built-in error log ?
>> Thanks
>|||Dear Tibor and Mark,
Thank you for your advice.
There is only 1 step. It seems that the contractor has written the message
out after finishing each step. In this way, it says "It takes xxx seconds
to finish Task 1 .. etc". However, since there are too many Tasks (around
150), in this way, at the last row, it shows "dot dot dot Job Failed" but I
am not able to see clearly which Task fails.
Thanking you in anticipation.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:uEvUcdqYFHA.2588@.TK2MSFTNGP14.phx.gbl...
> "Show step details" checkbox. This is essential!
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Jason" <anonymous@.discussions.microsoft.com> wrote in message
> news:OtaCYYqYFHA.1028@.TK2MSFTNGP10.phx.gbl...
>> The job is written by consultant. From memory, the message is something
>> like "It takes xx second to finish Task 1. It takes yy seconds to finish
>> Task 2. ...... Job failed".
>> Jason
>> "Mark Allison" <mark@.no.tinned.meat.mvps.org> wrote in message
>> news:eMd$pWqYFHA.580@.TK2MSFTNGP15.phx.gbl...
>> Jason,
>> In SQLAgent, right click the job and select View Job History..., tick
>> the show step details checkbox at the top right. Navigate to the step
>> that failed and the error message should present itself in the bottom
>> pane.
>> --
>> Mark Allison, SQL Server MVP
>> http://www.markallison.co.uk
>> Looking for a SQL Server replication book?
>> http://www.nwsu.com/0974973602m.html
>>
>>
>> Jason wrote:
>> From the job history, we find that a scheduled job has failed after we
>> have updated the structure of some tables.
>> We would like to know what is the best way to find out what causes the
>> failure ? Is there any built-in error log ?
>> Thanks
>>
>|||Hi,
Try to look if external log has been turned on or not.
Go to the job's properties, choose the step, click 'Edit'
then choose 'Advanced' tab.
There would be 'Output file' field.
Check if it is set and if it is, then look at the file.
Regards.
"Jason" wrote:
> Dear Tibor and Mark,
> Thank you for your advice.
> There is only 1 step. It seems that the contractor has written the message
> out after finishing each step. In this way, it says "It takes xxx seconds
> to finish Task 1 .. etc". However, since there are too many Tasks (around
> 150), in this way, at the last row, it shows "dot dot dot Job Failed" but I
> am not able to see clearly which Task fails.
> Thanking you in anticipation.
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
> message news:uEvUcdqYFHA.2588@.TK2MSFTNGP14.phx.gbl...
> > "Show step details" checkbox. This is essential!
> >
> > --
> > Tibor Karaszi, SQL Server MVP
> > http://www.karaszi.com/sqlserver/default.asp
> > http://www.solidqualitylearning.com/
> >
> >
> > "Jason" <anonymous@.discussions.microsoft.com> wrote in message
> > news:OtaCYYqYFHA.1028@.TK2MSFTNGP10.phx.gbl...
> >> The job is written by consultant. From memory, the message is something
> >> like "It takes xx second to finish Task 1. It takes yy seconds to finish
> >> Task 2. ...... Job failed".
> >>
> >> Jason
> >>
> >> "Mark Allison" <mark@.no.tinned.meat.mvps.org> wrote in message
> >> news:eMd$pWqYFHA.580@.TK2MSFTNGP15.phx.gbl...
> >> Jason,
> >>
> >> In SQLAgent, right click the job and select View Job History..., tick
> >> the show step details checkbox at the top right. Navigate to the step
> >> that failed and the error message should present itself in the bottom
> >> pane.
> >>
> >> --
> >> Mark Allison, SQL Server MVP
> >> http://www.markallison.co.uk
> >>
> >> Looking for a SQL Server replication book?
> >> http://www.nwsu.com/0974973602m.html
> >>
> >>
> >>
> >>
> >>
> >> Jason wrote:
> >> From the job history, we find that a scheduled job has failed after we
> >> have updated the structure of some tables.
> >>
> >> We would like to know what is the best way to find out what causes the
> >> failure ? Is there any built-in error log ?
> >>
> >> Thanks
> >>
> >>
> >
> >
>
>|||How about setting *in the job step* to output to a file? You can then open the file and see where
you get error messages etc.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Jason" <anonymous@.discussions.microsoft.com> wrote in message
news:%23apBohqYFHA.3032@.TK2MSFTNGP10.phx.gbl...
> Dear Tibor and Mark,
> Thank you for your advice.
> There is only 1 step. It seems that the contractor has written the message out after finishing
> each step. In this way, it says "It takes xxx seconds to finish Task 1 .. etc". However, since
> there are too many Tasks (around 150), in this way, at the last row, it shows "dot dot dot Job
> Failed" but I am not able to see clearly which Task fails.
> Thanking you in anticipation.
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:uEvUcdqYFHA.2588@.TK2MSFTNGP14.phx.gbl...
>> "Show step details" checkbox. This is essential!
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "Jason" <anonymous@.discussions.microsoft.com> wrote in message
>> news:OtaCYYqYFHA.1028@.TK2MSFTNGP10.phx.gbl...
>> The job is written by consultant. From memory, the message is something like "It takes xx
>> second to finish Task 1. It takes yy seconds to finish Task 2. ...... Job failed".
>> Jason
>> "Mark Allison" <mark@.no.tinned.meat.mvps.org> wrote in message
>> news:eMd$pWqYFHA.580@.TK2MSFTNGP15.phx.gbl...
>> Jason,
>> In SQLAgent, right click the job and select View Job History..., tick the show step details
>> checkbox at the top right. Navigate to the step that failed and the error message should
>> present itself in the bottom pane.
>> --
>> Mark Allison, SQL Server MVP
>> http://www.markallison.co.uk
>> Looking for a SQL Server replication book?
>> http://www.nwsu.com/0974973602m.html
>>
>>
>> Jason wrote:
>> From the job history, we find that a scheduled job has failed after we have updated the
>> structure of some tables.
>> We would like to know what is the best way to find out what causes the failure ? Is there any
>> built-in error log ?
>> Thanks
>>
>>
>|||Hi,
I find that there is no external log is enabled. I would like to follow
your suggestion. Where is the best place to put the external log ? I don't
want to mix it with other logs.
Thanks
"SkyWalker" <SkyWalker@.discussions.microsoft.com> wrote in message
news:DEA5C8F3-F87E-4707-8F2D-5406C86A7F19@.microsoft.com...
> Hi,
> Try to look if external log has been turned on or not.
> Go to the job's properties, choose the step, click 'Edit'
> then choose 'Advanced' tab.
> There would be 'Output file' field.
> Check if it is set and if it is, then look at the file.
> Regards.
> "Jason" wrote:
>> Dear Tibor and Mark,
>> Thank you for your advice.
>> There is only 1 step. It seems that the contractor has written the
>> message
>> out after finishing each step. In this way, it says "It takes xxx
>> seconds
>> to finish Task 1 .. etc". However, since there are too many Tasks
>> (around
>> 150), in this way, at the last row, it shows "dot dot dot Job Failed" but
>> I
>> am not able to see clearly which Task fails.
>> Thanking you in anticipation.
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
>> in
>> message news:uEvUcdqYFHA.2588@.TK2MSFTNGP14.phx.gbl...
>> > "Show step details" checkbox. This is essential!
>> >
>> > --
>> > Tibor Karaszi, SQL Server MVP
>> > http://www.karaszi.com/sqlserver/default.asp
>> > http://www.solidqualitylearning.com/
>> >
>> >
>> > "Jason" <anonymous@.discussions.microsoft.com> wrote in message
>> > news:OtaCYYqYFHA.1028@.TK2MSFTNGP10.phx.gbl...
>> >> The job is written by consultant. From memory, the message is
>> >> something
>> >> like "It takes xx second to finish Task 1. It takes yy seconds to
>> >> finish
>> >> Task 2. ...... Job failed".
>> >>
>> >> Jason
>> >>
>> >> "Mark Allison" <mark@.no.tinned.meat.mvps.org> wrote in message
>> >> news:eMd$pWqYFHA.580@.TK2MSFTNGP15.phx.gbl...
>> >> Jason,
>> >>
>> >> In SQLAgent, right click the job and select View Job History..., tick
>> >> the show step details checkbox at the top right. Navigate to the step
>> >> that failed and the error message should present itself in the bottom
>> >> pane.
>> >>
>> >> --
>> >> Mark Allison, SQL Server MVP
>> >> http://www.markallison.co.uk
>> >>
>> >> Looking for a SQL Server replication book?
>> >> http://www.nwsu.com/0974973602m.html
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> Jason wrote:
>> >> From the job history, we find that a scheduled job has failed after
>> >> we
>> >> have updated the structure of some tables.
>> >>
>> >> We would like to know what is the best way to find out what causes
>> >> the
>> >> failure ? Is there any built-in error log ?
>> >>
>> >> Thanks
>> >>
>> >>
>> >
>> >
>>