6
1
I have identical scheduled tasks running in Windows XP Pro and Windows 7. The XP Pro one runs fine, the Windows 7 one always returns 0x2 (which means, "The system cannot find the file specified"; however, executing from the command line is no problem) in the Last Run Result column of the Task Scheduler UI.
The scheduled task executes a .bat file daily. The .bat file contains a call to execute a Perl script. As I stated in the previous paragraph, it executes under XP without any trouble but under Windows 7, no dice.
The task under Windows 7 is set to "run whether the user is logged on or not." In this case it is me, I am the only user of the system. It is also set to "Run with highest privileges." And it is not hidden. The .bat file executes perfectly well from the command line - it calls the Perl script as expected and the Perl script does its thing.
I have searched far and wide looking for an appropriate answer to this issue. So far I have found nothing. What the devil is going on with this Win7 scheduled task? I am ready to pull my hair out.
Does your script access anything over the network, e.g. shared folders, or does it run entirely locally? – Chris W. Rea – 2010-12-03T19:37:18.617
2Did you target the file with an absolute name? Example: C:\Storage\batchfile.bat – Doltknuckle – 2010-12-03T19:44:23.540
1Have you set the working/current directory correctly? When you say that it works from the command-line, what directory do you run it from? Does it work from any directory? – Synetech – 2011-08-15T04:23:54.800