>We have a scheduled job that has been in place for several years (using the Windows Task Scheduler) on my computer (originally XP, more recently Win7/64). Now we're trying to run it from a Win Server 2012 machine, and so far we haven't been able to get it to work.
>
>It's a very simple VFP executable that simply clears out time & attendance records at the end of every two-week period. It copies two tables into a backup folder, then zaps the table for the prior period before appending the current records into the prior period table and then zapping the current table.
>
>If I log on to the server and navigate to the location of this program it will run, but there's something about setting it up in the Task Scheduler that I must be missing. It's apparently trying to launch it when the scheduled time arrives - the History tab shows the following:
>- Task triggered on scheduler
>- Created Task Process
>- Task Started
>- Action Started
>
>But none of the files have been updated, so it clearly is not executing. I've tried running it under my user account (which has full privileges) as well as the administrator account. It's set up the same as on my Win7 box, where it has never failed. I tried setting up two scheduled jobs that each consist of batch files that copy files into another folder, and those work consistently - it's just the VFP executable that doesn't want to run (it has no UI).
>
>Any suggestions appreciated!

Check the location where it should run. The location of the executable is NOT the default, it's somewhere in the user's appdata or wherever. Also watch out, there's an incredibly stupid bug about that textbox, whereby it will allow you to put quotation marks around a path which contains spaces, and later when you start looking for the reason it won't run, somewhere among other text it will say that the quotation marks shouldn't be there. Somebody should tell them that validation was invented already, or that they should be capable of stripping the quotes if they don't like them.

In one case I wasn't able to run as scheduled at all, because the account didn't have the rights to execute cmd.exe.

The third common cause for this silent failure is the expiration of the password on the account used to run the task, which is obviously not the case now, you're starting fresh.

Check the system event log, the errors from scheduled tasks should be there.