Link to home
Start Free TrialLog in
Avatar of SaxChick
SaxChick

asked on

ws_ftp upload weirdness

I have 2 very simple ws_ftp scripts.  Both scripts upload to the same remote site.  Both scripts are scheduled via Windows Scheduler.  They use the same connection site, the same remote user ID and password, and run under the same local server administrator account. 1 script works and 1 script doesn't. I am stumped and looking for help!

WS_FTP 12 Pro, installed on Windows 2003 server.

Script #1 works correctly, regardless of whether I run it from the WS_FTP scripting utility or run it via the Windows scheduler.

Script #2 works correctly and transfers files if I run it from within the WS_FTP scripting utility.  But when I run it via the Windows Scheduler, the scheduled task starts and the status changes to "Running".  The script file actually opens up in Notepad (why?).  The status continues to say "Running" until I manually close the Notepad windows.  No files are transferred.  Nothing is written to any of the ws_ftp logs.  Windows Event Logs show nothing interesting other than a successful login by the account that runs the scheduled task for ws_ftp.

Script #1 (works correctly)
; Upload script for Axle JPG files, sent to RSS

LOG \\YRKAPP001\APPS\WS_FTP_Files\TransferLog_RSS_Upload.txt

; PROD files MOVES
CONNECT RSS-AxlePics-Upload
ONERROR CONTINUE

LCD \\YRKFPS002\APPS\AxleData\Camera-Rear\ZIPfiles\
POSTXFER PXMOVE \\YRKFPS002\APPS\AxleData\Camera-Rear\ZIPfiles\2015
MPUT HubPics-Rear*.zip
POSTXFER PXOFF

CLOSE

Script #2, does not work correctly
; Upload script for Axle JPG files, sent to RSS

LOG \\YRKAPP001\APPS\WS_FTP_Files\TransferLog_RSS_AQAR_Upload.txt

; PROD files MOVES
CONNECT RSS-AxlePics-Upload
ONERROR CONTINUE

LCD \\YRKAPP001\APPS\AxleReportsAQAR\SQLDB\
MPUT Cleveland*.*

CLOSE
ASKER CERTIFIED SOLUTION
Avatar of Kimputer
Kimputer

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of SaxChick
SaxChick

ASKER

Ahhh... That was, indeed, the problem.  I had a simple error in the command line for the scheduled task that was failing.  Thanks for the quick response and the right answer!