SSIS & Winscp jobs failed to run - fixed with reboot

Advertisement

ted
Guest

SSIS & Winscp jobs failed to run - fixed with reboot

I have WinScp encapsulated in a SSIS package using Execute Task Process to run. It runs flawlessly majority of the time. But twice all FTP jobs will fail to run with the following error. No logs are generated.

To resolve the issue, the server has to be rebooted.

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

WinSCP version 5.1.4 (Build 3020)
Operating System Windows Server 2008 R2
SQL Server 2008 with latest Service pack.

Reply with quote

Advertisement

Shiiv Sot
Guest

Winscp jobs failed to run with SSIS - fixed with reboot.

Hi,

I am using WinSCP (v. 5.6.2). I am having the same problem. it runs correctly for some time and then it start giving the error:


Message
Executed as user: OMS\Administrator. ... 11.0.2100.60 for 64-bit Copyright (C) Microsoft Corporation. All rights reserved. Started: 11:20:00 PM Error: 2014-12-27 23:20:01.79 Code: 0x00000000 Source: FTP File Transfer Script Task for Description: Error when connecting to ftp: WinSCP.SessionLocalException: WinSCP process terminated with exit code 3 and output "", without responding (response log file C:\Users\Administrator.OMS\AppData\Local\Temp\wscp5CAC.03CE0BB8.tmp was not created). This could indicate lack of write permissions to the log folder or problems starting WinSCP itself. at WinSCP.Session.Open(SessionOptions sessionOptions) at ST_736288e11118423e85bffc826cb0c430.ScriptMain.Main() End Error Error: 2014-12-27 23:20:01.92 Code: 0x00000000


every time we restart the system it works correctly.
The SSIS job is installed in SQL-Server 2012.
The OS is Windows 2012 server.
The WinSCPNet.dll version is 1.2.2.4756


Please suggest the solution for this.

Reply with quote

Advertisement

You can post new topics in this forum