October 15, 2014 at 11:38 am
We are facing few issues running the batch command to initiate the ws_ftp process .I am using execute process task to trigger the batch file.
We are executing below batch command
"C:\Program Files (x86)\Ipswitch\WS_FTP 12\wsftppro.exe" -s local:\\ftp001\*.csv -d My_Supply:/usr/local/
Above command works fine when I call it using a sql job (Using management studio) and ssis proxy user is remotely connected to the server.
Once the proxy user is logedoff of the serve the command would return process exit code 3 and fail. Job fails basically.
I would like to know if you are aware of any special privileges the account that executes this command should have so that it can execute without being physically logged in to the machine.
Can anyone please let me know if I am doing anything wrong.
Any help is greatly appreciated.
October 17, 2014 at 7:49 am
Why are you using an external ftp client when you can use the SSIS ftp task?
-- Gianluca Sartori
October 17, 2014 at 8:00 am
As I recall WSFTP uses a lot of the standard DOS errors (exit code 3 which means "Path not found"). You'd have to make sure that the paths you're using are correct from the server viewpoint, and that the proxy user executing the process can in fact access those paths.
----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?
October 17, 2014 at 8:29 am
Thanks for taking time to reply back. The process would run fine when that proxy user is just signed on to RDP of that sql server and if I start the job process through management studio on my local machine .But once I log off it fails. So I assume when it works fine it is able to copy the files to the paths and it can access the paths .
Any thoughts ?
October 17, 2014 at 8:50 am
If you remote desktop into the server without opening up SSMS, then try to issue the WSFTP command FROM WITHIN THE REMOTE DESKTOP, on the server - what happens?
Also - is your SSIS instance colocated with the database instance you're logging into, or is SSIS on a dedicated machine? as far as I know - WSFTP would have to be installed on the SSIS box (not the DB server one).
----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?
October 17, 2014 at 9:04 am
If you remote desktop into the server without opening up SSMS, then try to issue the WSFTP command FROM WITHIN THE REMOTE DESKTOP, on the server - what happens?
Answer : If I Run the same command by REMOTE DESKTOP to the server and using command prompt it works perfectly .
Also - is your SSIS instance colocated with the database instance you're logging into, or is SSIS on a dedicated machine? as far as I know - WSFTP would have to be installed on the SSIS box (not the DB server one).
Answer: SSIS and sql server are on the same machine . WSftp is installed on this machine it self.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply