Originally posted by: Con-Way

I am trying to determine why I am encountering an error using the ftp adapter. The trace file shows a socket error 79, then socket error 32, then the connection is closing.

FTP Adapter, Version 8.0(124)
Copyright © 2004, Ascential Software Corporation. All rights reserved
Built for AIX on Nov 17 2006 at 01:08:34.
Retry Count is 3. Retry Interval is 5. OnFailure is Rollback.
Fetch Unit is 0. Card Mode is Integral.
Will process 33537 bytes of data.
Run Started at 07:10:33.673 on 04/10/08.
Options used: audit,append,trace,verbose,name,stage,url
URL ftp://username:*****@address/./in/HD1000277646.rdy;type=I will be used.
WSAStart: Entering
WSAStart: bWSStarted = 0, nWSClients = 0
WSAStart: SSL library load succeeded.
Sockets Client ID 1 enabled.
WSAStart: Exiting (rc = 1)
URL user: 'username'.
URL pass: '********'.
URL host: 'address'.
URL port: '21'.
URL path: './in/HD1000277646.rdy'.
URL type: 'I'.
Using ftp: protocol.
Server host is 'address'.
Using port '21' for the connection.
Connecting to 'address'.
Checking user port 21.
Service: 'ftp'.
Port: 21.
Protocol: 'tcp'.
Socket Opened.
Connected.
WSARecv: Socket error 79 occurred.
Warning! This server did not send a proper greeting.
WSASend: Socket error 32 occurred.
WSASend: Socket error 32 occurred.
WSASend: Socket error 32 occurred.
Socket Closed.
Connection closed.

I have replaced the username and servername to protect the innocent. I have the following settings specified in ini:

IdleFTP=20
;SLimFTP=0
;HLimFTP=0
;MinFTP=0

Any insight as to why this is happening would be good.
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender

Originally posted by: TarunB

A quick google reveals:

32 = Broken pipe
79 = Cannot access a needed shared library
What platform are you running this from?
Are you able to FTP from the command line?
Does your TX user have the required permissions/access?
Is the port (21) available for FTP use?
Are you using the correct method of FTP (port/passive)?

The .ini file settings you specify will have no bearing on the initial connection attempt.
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender

Originally posted by: Con-Way

This is being run from AIX. I have proven I can ftp from the command line, from the same TX user. Passive is allowed. I will have to check on port 21, good point.
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender

Originally posted by: Con-Way

Port 21 is a valid port. Anyone else have some thoughts on this one?
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender

Originally posted by: Con-Way

After doing more testing, it was determined that there is some sort of limitation in the ftp adapter. I have opened a case with IBM on this. The issue is that the dns address contains "ftp" in it. For whatever reason, this seems to be causing the error. When we change the address to the IP Address and not a dns name, the ftp works just fine.
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange