SCHTask.exe returns "Failed to start" from SVR 2008

Hi,
We have a number of 2003 servers which run lots of scheduled tasks around
the clock. We also have some 2008 servers which do the same.

We use SCHTask.exe from the 2008 servers, to query the scheduled tasks on
the 2003 servers, and then look through the output of this query for errors,
which is then used elsewhere to alert us that a scheduled task has failed on
a given machine, and what the task is called.

The problem we are having is that if a scheduled task runs sucessfully on a
2003 server, but has a NON ZERO return code, when SCHTask is run from a 2008
server and queries that 2003 server, the output contains FAILED TO START for
that tasks status.

Examining the task on the 2003 server from the task scheduler shows that the
task completed successfully.. and checking the tasks logs also indicate that
everything was fine.

This APPEARS to be a bug when SCHTASK is run from 2008 server against a 2003
server which has non zero return code tasks that have run.

Has anyone else had this problem? Its annoying because it keeps reporting
false job failures from our monitoring system.

Thanks!!

"Luke" <> wrote in message
news:327605C0-F8EA-4BD1-9A43-...
> Hi,
> We have a number of 2003 servers which run lots of scheduled tasks around
> the clock. We also have some 2008 servers which do the same.
>
> We use SCHTask.exe from the 2008 servers, to query the scheduled tasks on
> the 2003 servers, and then look through the output of this query for
> errors,
> which is then used elsewhere to alert us that a scheduled task has failed
> on
> a given machine, and what the task is called.
>
> The problem we are having is that if a scheduled task runs sucessfully on
> a
> 2003 server, but has a NON ZERO return code, when SCHTask is run from a
> 2008
> server and queries that 2003 server, the output contains FAILED TO START
> for
> that tasks status.
>
> Examining the task on the 2003 server from the task scheduler shows that
> the
> task completed successfully.. and checking the tasks logs also indicate
> that
> everything was fine.
>
> This APPEARS to be a bug when SCHTASK is run from 2008 server against a
> 2003
> server which has non zero return code tasks that have run.
>
> Has anyone else had this problem? Its annoying because it keeps reporting
> false job failures from our monitoring system.
>
> Thanks!!

A non-zero return code usually indicates a problem with the command(s)
you're trying to run. What are they?

>
> A non-zero return code usually indicates a problem with the command(s)
> you're trying to run. What are they?
>

Its a batch file which calls a script.. but its all custom stuff.. but like
I say, from 2003 server it says everything is OK.. just 2008 comes up with
the problem.

This means that some of this custom stuff causes a problem under Windows
2008.

"Luke" <> wrote in message
news:EAAE5ACB-64D9-4035-9CAF-...
>>
>> A non-zero return code usually indicates a problem with the command(s)
>> you're trying to run. What are they?
>>
>
> Its a batch file which calls a script.. but its all custom stuff.. but
> like
> I say, from 2003 server it says everything is OK.. just 2008 comes up with
> the problem.
>
>