«

I am trying Win7 x64 again, probably about the dozenth time.

Once again Task Scheduler is screwing up for me. It's run a batch file
every night for about 5 or 6 days but last night it decided not to.
Nothing in any logs/event viewers that I can find.

Anybody aware of any issues? It's set to run the task whether I am logged
on or not. hibernation is off, sleep is off.

This is usually the point at which XP goes back on as at least it works
(and it's a lot quicker too) but if anybody has any suggestions I'd be
interested.

--
Jeff Gaines Wiltshire UK
There are 10 types of people in the world, those who do binary and those
who don't.

The most common cause of task scheduler not completing is that the scheduled
task has requested input. This can be a dialog box, a y/n prompt, or some
other form of waiting for input. Unfortunately, since there is no console
associated with the task, the result is that the task hangs.

--
Charlie.
http://blogs.msmvps.com/Russel


"Jeff Gaines" <> wrote in message
news...
>
> I am trying Win7 x64 again, probably about the dozenth time.
>
> Once again Task Scheduler is screwing up for me. It's run a batch file
> every night for about 5 or 6 days but last night it decided not to.
> Nothing in any logs/event viewers that I can find.
>
> Anybody aware of any issues? It's set to run the task whether I am logged
> on or not. hibernation is off, sleep is off.
>
> This is usually the point at which XP goes back on as at least it works
> (and it's a lot quicker too) but if anybody has any suggestions I'd be
> interested.
>
> --
> Jeff Gaines Wiltshire UK
> There are 10 types of people in the world, those who do binary and those
> who don't.

On 17/04/2011 in message <iofas2$2fn$> Charlie Russel-MVP
wrote:

>The most common cause of task scheduler not completing is that the
>scheduled task has requested input. This can be a dialog box, a y/n
>prompt, or some other form of waiting for input. Unfortunately, since
>there is no console associated with the task, the result is that the task
>hangs.

In this case it's running a batch file which calls other applications. If
it always failed it would be easier to track but intermittent failure is
hard to track down.

--
Jeff Gaines Wiltshire UK
The facts, although interesting, are irrelevant

One thing to look for -- applications that do auto-updates? I've seen this
cause exactly what you're running into. The application wants to tell you
that it has an update available, but you, of course, aren't listening.

--
Charlie.
http://blogs.msmvps.com/Russel


"Jeff Gaines" <> wrote in message
news...
> On 17/04/2011 in message <iofas2$2fn$> Charlie Russel-MVP
> wrote:
>
>>The most common cause of task scheduler not completing is that the
>>scheduled task has requested input. This can be a dialog box, a y/n
>>prompt, or some other form of waiting for input. Unfortunately, since
>>there is no console associated with the task, the result is that the task
>>hangs.
>
> In this case it's running a batch file which calls other applications. If
> it always failed it would be easier to track but intermittent failure is
> hard to track down.
>
> --
> Jeff Gaines Wiltshire UK
> The facts, although interesting, are irrelevant

On 17/04/2011 in message <iofeon$bo6$> Charlie Russel-MVP
wrote:

>One thing to look for -- applications that do auto-updates? I've seen this
>cause exactly what you're running into. The application wants to tell you
>that it has an update available, but you, of course, aren't listening.

I'm definitely not listening at 1.30 a.m.

Thanks for the tip.

--
Jeff Gaines Wiltshire UK
640k ought to be enough for anyone.
(Bill Gates, 1981)

On 17/04/2011 in message <> Jeff
Gaines wrote:

[snipped]

Just a follow up, it ran fine last night...

--
Jeff Gaines Wiltshire UK
Tell me what you need, and I'll tell you how to get along without it.