Why would a scheduled task stop working?

"childofthe1980s" <childofthe1980s@discussions.microsoft.com> wrote in
message news:2CAC7E39-07FE-413A-AE5C-7AAE01B007C8@microsoft.com...<!--coloro:blue--><span style="color:blue <!--/coloro-->
> OK, Adrian! There are three jobs. So, every job that is in that stupid
> log
> is a separate job that is in question. Each of them is experiencing the
> same
> issue.
>
> As I tried to indicate, you can disregard. No need for sarcasm, either.
><!--colorc--><!--/colorc-->

This is a strange thread. It started by you posting your problem and having
some preconceived ideas about its cause, based on no evidence whatsoever.
Respondents had to ask you repeatedly to supply full details. You asked
respondents to trust your technical expertise when at the same time posting
contradictory reports (the job didn't start / the job did start but it did
not finish).

Perhaps a small amount of sarcasm would be appropriate, mixed with a
recommendation to review your trouble shooting approach. Keep an open mind,
do not jump to conclusions and do not assume anything unless you are
completely sure of your facts.

 

There should be an entry either case success or failure for every task that
runs.


--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]



"childofthe1980s" wrote:<!--coloro:blue--><span style="color:blue <!--/coloro-->
> The log is not saying anything as to why. No Microsoft log is forthcoming
> on
> any platform (Windows, SQL, Sharepoint, etc.) <!--colorc--><!--/colorc-->

 

Monitor wrote:<!--coloro:blue--><span style="color:blue <!--/coloro-->
> "childofthe1980s" <childofthe1980s@discussions.microsoft.com> wrote in
> message news:2CAC7E39-07FE-413A-AE5C-7AAE01B007C8@microsoft.com...<!--coloro:green--><span style="color:green <!--/coloro-->
>> OK, Adrian! There are three jobs. So, every job that is in that stupid
>> log
>> is a separate job that is in question. Each of them is experiencing the
>> same
>> issue.
>>
>> As I tried to indicate, you can disregard. No need for sarcasm, either.
>><!--colorc--><!--/colorc-->
>
> This is a strange thread. It started by you posting your problem and having
> some preconceived ideas about its cause, based on no evidence whatsoever.
> Respondents had to ask you repeatedly to supply full details. You asked
> respondents to trust your technical expertise when at the same time posting
> contradictory reports (the job didn't start / the job did start but it did
> not finish).
>
> Perhaps a small amount of sarcasm would be appropriate, mixed with a
> recommendation to review your trouble shooting approach. Keep an open mind,
> do not jump to conclusions and do not assume anything unless you are
> completely sure of your facts.
>
> <!--colorc--><!--/colorc-->

Ahh... but a bit of sarcasm helps the work pass quicker ;-)

Ok, so now we know you have three jobs (new information). That log
shows that some are running and ending sucessfully (not new), and that
some arent on other runs.

Can I assume that the ones that complete OK, are jobs that you manually
started?

If thats the case, then as I tried to point out, the environment that
you run when you manually start a scheduled task, can be slightly
different to that that the scheduled task process runs the job itself
(even with Logon As rights set). This can be caused by logon scripts,
GPOs etc that get applied on a login, but not by a scheduled task.

So, then you need to go back to finding out more about that environment
that its running in as a scheduled job. The only way you can do that is
to log information from the job, AS it runs. So I'd suggest you put the
logging that myself and others have suggested into the .cmd script,
let it run by itself and see where in the cmd file it gets to, or what
the environment is between a manual run and an automatic run.