WinSCP, SSIS and SQL Job

Advertisement

jhong
Guest

WinSCP, SSIS and SQL Job

I have the the executing of WinSCP as a Execute Process task in my SSIS project. Works perfectly as I have the WinSCP executable executing commands from a script file. Again works perfectly. However when I run the SSIS package from a SQL job I get the below error. Has anyone experienced this before or know what the issue is? Thanks in advance.


Description: In Executing "C:\Program Files (x86)\WinSCP\WinSCP.exe" "/script=D:\Success_Factors\SCP_Script\myscript.txt" at "", The process exit code was "1" while the expected was "0". End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 5:00:02 AM Finished: 5:00:05 AM Elapsed: 2.746 seconds. The package execution failed. The step failed.

Reply with quote

Advertisement

twee
Guest

The process exit code was "1" while the expected was "0"

I still couldn't get it work please help.
Package works fine manually but failed in job scheduling with error The process exit code was "1" while the expected was "0"
So how do you export to INI file?
Thanks in advance.
TN

Reply with quote

shrikanaskar1
Guest

SQL server Agent->Job cant run SSIS package with WINSCP command

I am using WinSCP as a Execute Process task in my SSIS project. Works fine in Visual Studio,however, when I run the SSIS package from a SQL job (SQL server Agent->Job) I get the an error. Appreciate any help.
================================
option batch on
option confirm on

open sftp://user_name:password@ftp.xx.com:22 -hostkey = "ssh-rsa ....................."

cd /XYZ/TEST

close
exit
===============================================

I tried using INI file; It works in in Visual Studio but not in SQL Agent

Reply with quote

martin
Site Admin
martin avatar
Joined:
Posts:
27,227
Location:
Prague, Czechia

Re: SQL server Agent->Job cant run SSIS package with WINSCP command

What "error"?
Did you read this? https://winscp.net/eng/docs/faq_scheduler

If the FAQ does not help, please attach a full session log file showing the problem (using the latest version of WinSCP).

To generate the session log file, use /log=path_to_log_file command-line argument. Submit the log with your post as an attachment. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you can mark the attachment as private.

Reply with quote

Advertisement

You can post new topics in this forum