Hi, folks:
What I think is a [NF] Non-Fox question.
PROBLEM: I've taken over a legacy app's backup batch routine. It automatically worked on their old machine (Windows 2000!) but I'm having trouble duplicating it in "Schedule Tasks" on their replacement machine, a Win 7 Pro workstaton.
BACKGROUND: Once a day, the scheduled task launches a VFP executable that:
CD's to a local directory Opens a local DBF or recreates it if missing, with a single record containing a date Reads that DBF to get the date Does an ADIR to read a network file's last update date
If the local file date # the remote date,
It UPDATEs the table with the remote date It does a RUN /N to launch a .BAT which:
XCOPY's the network files to the c: drive 7-ZIPs the files into an archive invokes PuTTY's pscp to perform a secure copy to a "cloud" server. (PuTTY's pagent is running in the desktop tray, with the necessary private key loaded)
The scheduled task is configured to run this in the same context as the primary user of the machine.
EXPECTED: When I am logged in as that user via RDP and run the EXE, the app works as expected.
ACTUAL: When it runs from Scheduled Tasks, either automatically or manually invoked, there's no screen interaction, of course, but no file sent, either.
The EXE shows up in the Task Manager, initially using 3,456K of memory, then it slowly decreases down to 318K
WHAT I'VE TRIED: Running while logged in (remotely via RDP) works fine.
Changing the network locations (F:) to UNC (\fileserver\sharename\path) didn't make a difference.
Ticking the checkboxes in Scheduled Tasks for "Log in as" or "Run only when logged in" or "Use maximum permissions" made no difference.
Ideas? Is this a WinPro7 v. 2000 security "feature" I'm running into?
Ted,
I had a similar problem on SQL Server 2012. I figured out that I had to give full rights to whatever user it was scheduled to run under to both the program and folder it was running in. (I would assume also to any resources it uses as well). Once I did that, it ran like a charm. Before that, nothing, unless I was logged in.
On Thu, Mar 9, 2017 at 9:25 PM, Ted Roche tedroche@gmail.com wrote:
The scheduled task is configured to run this in the same context as the primary user of the machine.
EXPECTED: When I am logged in as that user via RDP and run the EXE, the app works as expected.
ACTUAL: When it runs from Scheduled Tasks, either automatically or manually invoked, there's no screen interaction, of course, but no file sent, either.
Password stored in Task Scheduler was incorrect? Wrong permission and ownership for all files and folders involved?
-
Man-wai Chang -
Ted Roche -
Vince Teachout