Using Windows "scheduled tasks" to launch a .bat file

I have a .bat file which I'd like to have run automatically every night.

I tried using Windows "scheduled tasks" and referenced the .bat file. I then
tried manually running it to test it. A command window briefly flashes on
the screen but the .bat file does not appear to be invoked.

I verified that the .bat file isn't getting called by creating a simple test
..bat file which did nothing more than create a file on disk. Sure enough the
..bat file isn't getting called. The test .bat file contents are shown below.


echo hello >> c:\test_log.txt


I also tried referencing cmd.exe /c "c:\test.bat" in the scheduled task and
this didn't work either.

The annoying part about all this is that I successfully did this a long time
ago and I recall having similar issues and eventually figuring it out If
only I could recall what the magic was which made it work.

Any ideas?

I found the problem. Someone else suggested using cmd.exe /k "the .bat
file" so that the window would stay open, allowing viewing of any errors.

As it turns out, the problem was caused by one of the directories in the
path to the .bat file containing spaces. Using dir /x to obtain the 8.3
abbreviated name and using that instead fixed the problem.


"Dave Calkins" <david.calkins@noemail.noemail> wrote in message
news:%23lSue1lcIHA.748@TK2MSFTNGP04.phx.gbl...
>I have a .bat file which I'd like to have run automatically every night.
>
> I tried using Windows "scheduled tasks" and referenced the .bat file. I
> then tried manually running it to test it. A command window briefly
> flashes on the screen but the .bat file does not appear to be invoked.
>
> I verified that the .bat file isn't getting called by creating a simple
> test .bat file which did nothing more than create a file on disk. Sure
> enough the .bat file isn't getting called. The test .bat file contents are
> shown below.
>
>
> echo hello >> c:\test_log.txt
>
>
> I also tried referencing cmd.exe /c "c:\test.bat" in the scheduled task
> and this didn't work either.
>
> The annoying part about all this is that I successfully did this a long
> time ago and I recall having similar issues and eventually figuring it out
> If only I could recall what the magic was which made it work.
>
> Any ideas?
>
>
>