May 20, 2003 at 10:42 am
I searched the site and BOL for the answer I am seeking and found none. Probably it is so obvious that no one thought it needed to be written down.
In any case, I am trying to use the FTP Task. When I set it to use an internet site it always fails claiming a connection problem. When I use a directory it succeeds. Unfortunately, I need to connect to an FTP server not on our network.
Here are variations of what I have entered in the ftp site box:
//10.10.10.10/foldername/
//10.10.10.10/
\\10.10.10.10
\\10.10.10.10\\10.10.10.10\foldername
Am I not entering this properly? I have verified the username and password.
Must some port be open in a fire wall to allow this task to function? Or is it enough that since I can get the file using commands in a command window that this task should also work?
I have a batch file that currently gets the needed file from ftp servers (developed when the FTP Task didn't exist). I don't need alternate ways to get the file, I just want to know what I am doing wrong so that I can make the FTP task work.
Robert W. Marda
SQL Programmer
bigdough.com
The world’s leading capital markets contact database and software platform.
Robert W. Marda
Billing and OSS Specialist - SQL Programmer
MCL Systems
May 21, 2003 at 2:40 am
I decided to not to use the ftp task for this type of operation, can not remember the error I was getting. I Decided to create a script file with the ftp commands instead and have not looked back at the ftp task.
Simply create the file with all the ftp commands and execute a Process Task with Command: FTP And Parameters: -s:FTP Script File Path.
May 22, 2003 at 12:10 am
I fully agree - FTP task does not deliver, success is not proprly reported.
I abandoned the idea of using FTP Task and I have created whole system of DTS packages for generic FTP transfer build around - using execute process task.
I use something similar to:CMD /C D: && cd "pathToScriptFile" && C:\winnt\system32\ftp.exe -s:"scriptName.txt" > scriptLog.log
I dynamically change the script content and can examine the log for the session log.
May 27, 2003 at 4:01 am
I work with the FTP task and it work properly.
1) you should test if the server where you
sql server is hosted can connect to the ftp
site. (type in your browser ftp://login:password@yourftpsite)
2) if yes, then configure the ftp task
as following
description: xxxx
source: internet site
FTP: 192.168.0.1 (for example) no // and no \username: login
password: passw
destination
directory Path: \\servername\directory
on the file tab:
you can choose on the remote FTP the directory, the file you like
then
May 29, 2003 at 7:57 am
May be when you need to get one file which is already there it works fine.
In my project I had to get the certain number of files (differently named each day - although consistently eg xxxxxYYYYMMDDzzz.csv) and get them almost as they arrived and report appropriately if files did not arrived by the given time (polling end time) each day. So there were instances that I wanted to get the file which was not yet on the ftp site.
In this cases I have found FTP task not reporting at all failures (such as file not at the FTP location) and sometimes hanging.
That's why I do not used FTP task, and built my FTP dts project around http://FTP.EXE
Currently - my set of `FTP` packages run daily on 4 different set of incoming files ( from 3 to 35 files) driven by the data in parameters table - which describes polling period time, name of files to transfer , FTP site locations and file's destination locations, etc.
These are now running in production environment for 5 months now with no problems.
I have generic set of packages which do the proper work and only one calling package which is then scheduled and run as a job - is different for each set of files I need to transfer.
Tom
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply