This is an old revision of the document!
Reporting Bug or Asking for Support
Help Yourself
First, try to troubleshoot your issue yourself.
Advertisement
Hello
I created a package to do a sftp using winscp application. The package runs well when i do it manually. however if i schedule a job in MS SQL server it throws me the following error
Message Executed as user: NAROOT\svc_sql3_agent. Microsoft ® SQL Server Execute Package Utility Version 10.0.2531.0 for 32-bit Copyright © Microsoft Corp 1984-2005. All rights reserved. Started: 5:01:40 PM Error: 2009-12-02 17:01:41.24 Code: 0xC0029153 Source: Execute Process Task Execute Process Task Description: File/Process “WinSCP.com” does not exist in directory “I:\Metrics\Operating\VOTC\Fedex\WinSCP”. End Error Error: 2009-12-02 17:01:41.24 Code: 0xC0024107 Source: Execute Process Task Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 5:01:40 PM Finished: 5:01:41 PM Elapsed: 0.952 seconds. The package execution failed. The step failed.
The point is the application resides in that directory and i can still run the package by right clicking on it. Just that schedule job fails
Example of Bug Report
Subject: Open session in new window
While session is opened and the main window is shown, hold Shift and click on a saved session (in Session > Saved Sessions menu) in subfolder in order to open the session in new window. It does not work. Instead error message pops up saying: “Host does not exist”.
Using WinSCP 4.1.4 with “Commander” interface on Windows XP SP3. It happens for any stored session in subfolder, regardless of protocol or server. So I’m not posting session log file as it seems irrelevant.
Example of Support Request for Scripting
Subject: Trouble setting server timeout via command line
I have a client with a slow FTP server, it takes 25 seconds or so to connect. Whenever I attempt to add the -timeout=xxx
switch to the end of my open
command, WinSCP just bails out. No session log file is even created. If I remove the -timeout
switch, it connects.
Here is the command line:
winscp.exe /console /script=test.txt /log=log.txt
Here is the script:
option batch on
option confirm off
open user:pass@site -timeout=60
option transfer binary
get *05152008*
close
exit
After running the script I get following in console:
batch on
confirm off
Too many parameters for command ‘open’.
Using WinSCP 4.0.7 on Windows 2000.
Advertisement