File Adapter FTP Error : 501

Hi All,
I am getting following error in the communication channel for File Adapter.
'com.sap.aii.adapter.file.ftp.FTPEx: 501 IP Address for data destination doesn't match client's.'
Communication channel details are as follows -
FTP protocol is used with Port 21.
Data connection - Active
File type : Binary.
The same interface is working fine in Development, Quality and Pre-Prod environments.
This issue is coming only for Production FTP server.
From the error text, it appears as a network issue.
Please to let me know if anyone has came across such issue earlier, and what the the possible reasons - solutions to resolve this.
Thanks a lot.
Regards,
Minal

>
Minal Vaidya wrote:
> Hi All,
>
> I am getting following error in the communication channel for File Adapter.
>
> 'com.sap.aii.adapter.file.ftp.FTPEx: 501 IP Address for data destination doesn't match client's.'
>
> Communication channel details are as follows -
> FTP protocol is used with Port 21.
> Data connection - Active
> File type : Binary.
>
> The same interface is working fine in Development, Quality and Pre-Prod environments.
> This issue is coming only for Production FTP server.
>
> From the error text, it appears as a network issue.
> Please to let me know if anyone has came across such issue earlier, and what the the possible reasons - solutions to resolve this.
>
> Thanks a lot.
>
> Regards,
> Minal
this seems to be something to do with your firewall... you can have your network team involved so that the can work a solution.
a good read: http://lists.opensuse.org/opensuse-security/1999-11/msg00099.html

Similar Messages

File Adapter - FTP Error

Hi,
I have a Sender File Adapter using FTP which polls a server every 60 seconds looking for a file. Intermittently the adapter will connect and pick up the waiting file. However, more often than not it gives an error:
An error occurred while connecting to the FTP server 'xx.xx.xx.xxx:21'. The FTP server returned the following error message: 'com.sap.aii.adapter.file.ftp.FTPEx: 426 Unexpected reply codeConnection closed; transfer aborted.'. For details, contact your FTP server vendor.
The connect mode is Permanently and the transfer mode is Binary.
Any ideas ?
PaulC.

Monica,
Can you explain the difference between ACTIVE and PASSIVE and why changing to ACTIVE may get rid of this issue ? Have looked at the help.sap.com and it doesn't give too much detail on these settings.
Thanks
PaulC.

SENDER FILE ADAPTER (FTP) ERROR

Hi,
Iam getting the following error in sender file adapter:
Could not process due to error: com.sap.aii.adapter.file.ftp.FTPEx: 550 *** ERROR *** NO BATCHES FOR TRANSMISSION
Could anyone help me in this.
Thanks &Regards,
Kiran

Hi Kiran,
This problem is not related to PI but rather related to FTP server settings.
Try changing the name of the file in your adapter settings to a string without any dots and ".
Try this and let me know if its successful.
Regards,
Divya

Receiver File Adapter: FTPS Error

On sending a text file to a trading partner the log in the communication channel shows the following:
Connecting to FTP server - success
Write to FTP server - success
Transfer: "TXT" mode - success
Exception caught by adapter framework:connection timed out - Error
The FTP connection Parameters have:
Data connection = Passive
Connection security = FTPS (FTP using SSL/TLS)
Command order AUTH TLS, USER, PASS, PBSZ, PROT
Use of X509 cert for Client Authentication is checked
Keystore = service_ssl
x.509 Cert and private key = *******.crt
When I look in the NWA logs for default trace I see several messages with the text "Rolling back transaction for message..." plus a FILE_ERR_211
What is a FILE_ERR_211?
Thanks
Mark

hi mark,
To configure a timeout for the FTP connection, please enable the "Advanced Mode" for the respective FTP communication channel in the Integration Directory and add an entry "ftp.timeout"=timeoutSecs
(without any quotation marks) to the "Additional Parameters" section, where timeoutSecs is the desired FTP timeout in seconds.
regards
kummari

File Adapter FTPS: Error - iaik.security.ssl.SSLException

I'm trying to use FTPS to communicate from XI ( SP 15 ) . FTPS system Admin provided CA Certificate and we installed same in key Storage as trusted CAs.
However when I try to send file It was throwing message " Error: Message processing failed: iaik.security.ssl.SSLException: Peer sent alert: Alert Fatal: illegal parameter " In the Adapter Monitoring .
However same Certificates installed on recent versions of XI ( PI 7.0) works just fine.
Any ideas will be appreciated.

Hi S T,
Check these..
Details for 'Is Web service security available?'
HTTPS Error
All the best!
cheers,
Prashanth
P.S Please mark helpful answers

File Adapter: Initialization error: Conversion initialization failed

Hi all,
I'm trying to establish a file adapter (FTP, File Content Conversion).
In the adapter monitor I' ve got the following error:
Sender Adapter v1325 for Party '', Service 'BS_ACN_PCS_A':
Configured at 14:49:34 2005-08-29
Initialization error: Conversion initialization failed with java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found:
Format error in 'xml.recordset' argument: incomplete structure (name,number) pair
My content conversion parameters are:
BP_BusinessPartnerMasterData_IncomingData.fieldFixedLengths:
20,50,50,1,10,50,10,50,5,20,20,15,15
BP_BusinessPartnerMasterData_IncomingData.fieldNames: Number,Name2,Name1,Gender,Birthdate,City,Postcode,Street,
HouseNo,PhoneNumber,Fax,BankId,BankAccount
BP_BusinessPartnerMasterData_IncomingData.fieldContentFormating:
trim
BP_BusinessPartnerMasterData_IncomingData.keyFieldInStructure:
ignore
What could be the error or where I have to look for it?
Thanks,
Fabian

Yes,
Recordset name: BP_BusinessPartnerMasterData_IncomingData
Recordset structure: BP_BusinessPartnerMasterData_IncomingData
The corresponding Message Type:
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://pcs.acn.com/basicdata" targetNamespace="http://pcs.acn.com/basicdata">
     <xsd:element name="BP_MasterDataIncomingFil" type="BP_BusinessPartnerMasterData_IncomingData" />
     <xsd:complexType name="BP_BusinessPartnerMasterData_IncomingData">
          <xsd:annotation>
               <xsd:appinfo source="http://sap.com/xi/TextID">
               f323a4b018a911da9fd9000bcd69ce64
               </xsd:appinfo>
          </xsd:annotation>
          <xsd:sequence>
               <xsd:element name="Number">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e8500fe111da89f2d1210a87220d
                         </xsd:appinfo>
                         <xsd:documentation xml:lang="EN">
                         Id from Sender for BP
                         </xsd:documentation>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="20" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="Name2">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e8510fe111dacfd7d1210a87220d
                         </xsd:appinfo>
                         <xsd:documentation xml:lang="EN">
                         Last name or Company name
                         </xsd:documentation>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="50" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="Name1">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e8520fe111da94bad1210a87220d
                         </xsd:appinfo>
                         <xsd:documentation xml:lang="EN">
                         First name or Company name 2
                         </xsd:documentation>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="50" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="Gender">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e8530fe111da99add1210a87220d
                         </xsd:appinfo>
                         <xsd:documentation xml:lang="EN">
                         m or f or blank
                         </xsd:documentation>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="1" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="Birthdate">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e8540fe111dab156d1210a87220d
                         </xsd:appinfo>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="10" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="City">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e8550fe111daa58cd1210a87220d
                         </xsd:appinfo>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="50" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="Postcode">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e8560fe111dac0c2d1210a87220d
                         </xsd:appinfo>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="10" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="Street">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e8570fe111dabbd3d1210a87220d
                         </xsd:appinfo>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="50" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="HouseNo">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e8580fe111dab63fd1210a87220d
                         </xsd:appinfo>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="5" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="PhoneNumber">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e8590fe111dac782d1210a87220d
                         </xsd:appinfo>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="20" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="Fax">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e85a0fe111daa9ebd1210a87220d
                         </xsd:appinfo>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="20" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="BankId">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e85b0fe111dace1ed1210a87220d
                         </xsd:appinfo>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="15" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="BankAccount">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e85c0fe111da8801d1210a87220d
                         </xsd:appinfo>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="15" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
          </xsd:sequence>
     </xsd:complexType>
</xsd:schema>

Using wildcards (*) in sender file adapter - FTP type

Hi guys!
Dooes it work using wildcards in sender file adapter (FTP type(!) (filesystem obviously work))? I tried it and it failed. it works only for exact name..
I read some articles about FTP and the result is, that ftp work always only with 1 file, so I'm wondering, if this is possible.
Thanks for info!
Olian

Thanks for all replies..
I know of course, that * can be used, I use it in many scenarios too. But on a FileSystem. It is not working if the sender type is FTP.
*, ., *.dat, ... nothing like that works.. Just exact file name.
I am able to pick up file, if I specify it's exact name, so there should be no problem with permissions..
Please, I'd appreciate one reply with comfirmation: yes, we are using asterisk (*) , we access source files via FTP and they are processed.
Is there anybody with this experience, that it works?
Thank you!
Olian

Sender File Adapter - FTP

XI is picking up While File is being written in the Specified Directory. XI uses File adapter ( FTP transport Protocal ) . If file being written is very large ( It may take couple of minutes ) XI picks it up in parts for every 1 minute ( It was configured like that ) and try to send over Which is not correct. Is there any workaround to this issue. In PI 7.0, for NFS file system, SAP included modification check but it doesn't work for ftp file adpater. Basically XI should wait to pickup file until the file written completely in the Source System.
Anyone have any Idea how to overcome this issue ?

Hi,
You could use the Advanced mode checkbox in the file adapter, to specify the time the adapter has to wait, before it checks if the file has been modified.
In case, the file has been modified, after the adapter read the file, the data in the adapter cache is discarded and the updated/modified file is taken from the source path specified.
This would work, only if you have not specified "recordsets per message" during content conversion.
Regards,
Smitha.

Error on sender CC file adapter FTP

Hi
i have the scenario FILE-WS-FILE (synchronous) where im having problems in my sender CC, at the channel monitor servlet is showing the next errors while trying to get the message on the XML file.
MP: unexpected exception caught com.sap.aii.af.service.cpa.impl.exception.CPAObjectKeyException: Value of key must not be null: ObjectId
Error: java.lang.NullPointerException: while trying to invoke the method com.sap.engine.interfaces.messaging.api.Message.getMessageId() of an object loaded from local variable 'message1'
if anyone could help me, i appreciate.
Regards.

Check this ones,
Adapter Module error
http://xml.apache.org/xalan-j/apidocs/org/apache/xml/serializer/utils/MsgKey.html
http://help.sap.com/javadocs/pi/SP3/xpi/com/sap/engine/interfaces/messaging/api/MessageKey.html
Regards!

RECEIVER FILE ADAPTER FCC ERROR

Hi team
My scenario is a text file has to be picked up by PI, has to processe it and the receiver is Proxy and it has to get updated and sent back to FTP location.
i am using Sender File Adapter with FCC and Also receiver File Adapter with FCC.
Both the sender and receiver structures are same; i am using the same FCC parameters for both the sides.
in Receiver File Adapter i am getting the following errors
1) Conversion initialization failed: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found:
Parameter '.fieldFixedLengths' or '.fieldSeparator' is missing
2)Conversion initialization failed: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found:
Parameter '1.fieldFixedLengths' or '1.fieldSeparator' is missing
please help me out
thank you
Edited by: vemugantivn on Aug 16, 2010 12:19 PM

Hi,
> 1) Conversion initialization failed: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found:
> Parameter '.fieldFixedLengths' or '.fieldSeparator' is missing
> 2)Conversion initialization failed: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found:
> Parameter '1.fieldFixedLengths' or '1.fieldSeparator' is missing
It is saying that you are not using the fieldSeparator parqameter.
have you provided the field separator parameter? if not then give like below
order_row.fieldSeparator : , (give what ever the separater you are using)
or
order_row.fieldSeparator : 10,5,... (if you are using fixed length)
Regards
Ramesh

Sender File Adapter (FTP Protocol)

Hi Every Body,
I have a problem in using Sender File Adapter of (FTP Protocol Type)
I have given all required settings to get connected to the FTP Server.
When i give ( Source Directory and Exact File Name ex : MDMERP.xml)
File gets picked up.
But When i give (Source Directory and Exact File Name ex : *.xml)
it gives below exception
Error occurred while connecting to the FTP server "mdmerp6:21": java.net.ConnectException: Connection refused: connect
Strange any guess !! :(((
Regards
Srinivas

Hi,
If that is connection error then it should have not allowed to pick up when i have given the specifif file name ,
.xml is too not working
my problem all starts if i use other than file name declarartion it throws error
of below kind
Error occurred while connecting to the FTP server "mdxxxp6:21": java.net.ConnectException: Connection refused: connect
Can i use " Advanced Selection of Source File" and make it run\
With regards
Srini

File Adapter: FTP issue

Hello,
There is a problem with the file adapter of the XI30 SP14:
It is set to get a file from a server X using a FTP protocol.
INT_001_V01_COM_CTDCLNT600_FILE_SENDER
Sender Adapter v2300 for Party '', Service 'CTDCLNT600':
Configured at 2006-01-16 15:13:52 EST
History:
- 2006-01-16 15:23:54 EST: Polling interval started. Length: 60.000 s
- 2006-01-16 15:23:54 EST: Processing finished successfully
- 2006-01-16 15:23:52 EST: Processing started
- 2006-01-16 15:22:54 EST: Polling interval started. Length: 60.000 s
- 2006-01-16 15:22:54 EST: Processing finished successfully
It seems everything is working fine, but the in the SXMB_MONI transaction, no message appears.
I have accessed the FTP manually and I have downloaded the file, so the connectivity issue is descarted.
Any suggestion.
Jesus Barba Lobaton

Hello all,
The current configuration of the Sender file adapter is:
Transfer protocol: FTP
Message protocol: File Content Conversion
Adapter Engine: Integration Server
Source Directory: /out
File: D_P.DAT
In FTP: the file D_P.DAT is placed under /out directory
Server: Server Internal IP
Port: 21
Connection security: None
User: userX
Pass: FTPuserX
Quality of Service: Exactly once
Poll Intervals: 60
Processing mode: Delete
File Type: Binary
How can I verify a log of the processing process? as the SXMB_MONI transaction does not show anything.
The most frustrating of all, is no error message appears. I have verified the XI, APPS and default trace logs with log viewer but there is nothing.
I have also checked this thread but none of the solution provide solved the issue
Pbm in File adapter..Post Sp14
OS: Windows 2003
Any idea?
Jesus

File Adapter FCC Error

Hi team
i am getting the following errors in the File Adapter when i am using the FCC Parameters.
1)Conversion initialization failed: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Mandatory parameter 'xml.keyfieldName': no value found
2)Conversion initialization failed: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Mandatory parameter 'Detail.keyFieldValue': no value found
My FCC parameters are
Header.fieldNames,Header.fixedLengths,Detail.fieldNames,Detail.fixedLengths
i am receiving a file from the FTP server; the file structure has header and detail records.
Please help me out
tahnx a lot in advance

Hi,
Your header and details lines in the file will contain the first value which differentiates them.
That field becomes your Keyfiled.
Add the following to the configuration:
xml.keyfiledName - the 1st field name from the header and detail
header.keyFieldValue - vakue from the header line
detail.keyFieldValue - value from the detail line
Regards,
Pragati

File Adapter - FTP - Unable to Create new pooled resource

Hi Friends,
I am getting the following error while using file adapter with FTP protocol...
Attempt to process file failed with Error when getting an FTP connection from connection pool: com.sap.aii.af.service.util.concurrent.ResourcePoolException: Unable to create new pooled resource: FTPEx: PASS command failed
Error MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: Error when getting an FTP connection from connection pool: com.sap.aii.af.service.util.concurrent.ResourcePoolException: Unable to create new pooled resource: FTPEx: PASS command failed
Error Exception caught by adapter framework: Error when getting an FTP connection from connection pool: com.sap.aii.af.service.util.concurrent.ResourcePoolException: Unable to create new pooled resource: FTPEx: PASS command failed
Error Delivery of the message to the application using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Error when getting an FTP connection from connection pool: com.sap.aii.af.service.util.concurrent.ResourcePoolException: Unable to create new pooled resource: FTPEx: PASS command failed.
Can someone help me to solve this probelm..
Regards,
Shyam.

Hi,
Try to check the directory you have specified in the CC and also check whether you are able to connect to the FTP server with those login credential and access the directory specified.
Also let me know whether it is working fine for other scenario's or not.
Regards,
Nithiyanandam

Problem with file adapter (FTP) created under business service

Hi
I am using file adapter in my receiver communication channel. I dont know the physical existance of the system so i have created one business service. Under this business system i have created a file adapter with FTP protocol. I have given all the parameters. But when i am trying to execute my scenarion i am getting the following error in SXMB_MONI.
com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/_SQLMediaCodeToCRMCapaign_: RuntimeException in Message-Mapping transformatio~
In RWB i am getting the following error.
Mapping Error
Execption_During_Execution
In Communication Channel monitoring I am not getting any information regarding receiver file adapter. Its not showing any message either error or sucessful. How to find whether my receiver communication channel FTP parameters configured correctly or not.What is the error. Please help me.
Regards
Sowmya

Somya,
Error clearly indicates that issue is with mapping....so there is no point of checking receiver adapter..
BTW for checking whether the FTP site is working properly or not , you can use any ftp client softwares or command prompt of windows also.
---->In Communication Channel monitoring I am not getting any information regarding receiver file adapter. Its not showing any message either error or successful.
Message has not reached up to that level so no point of looking at receiver communication channel.
Regards,

File Adapter FTP Error : 501

Similar Messages

Maybe you are looking for