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

Similar Messages

  • Error:iaik.security.ssl.SSLCertificateException: Peer certificate rejected

    Hi,
    I am getting error com.sap.engine.interfaces.messaging.api.exception.MessagingException:
    iaik.security.ssl.SSLCertificateException: Peer certificate rejected by ChainVerifier
    When i test for digital signing and encryption using soap receiver CC
    we passed all the values for soap CC
    Created key store view and in that view I have generated private certificate and generated CSR using SAP CA(test ssl for 8 weeks) for the private key and also imported public key for encryption given by reciver
    When i test i get the error message
    I check certificates validity dates
    I restarted java engine and ICM
    I added the public key in trusted CA in NWA
    I re created the view and added the certifcates
    still the same error
    how and where to check to check IAIK in NWA and how to deploy it in java engine using NWA, we are using PI7.11 (no VA)
    any suggestions?

    Hi,
    The main causes for this kind of problem are:
    1. The correct server certificate could not be present in the TrustedCA keystore view of NWA. Please ensure you have done all the steps described in the URL below:
    Security Configuration at Message Level
    http://help.sap.com/saphelp_nwpi71/helpdata/EN/ea/c91141e109ef6fe1000000
    0a1550b0/frameset.htm
    2. The server certificate chain contains expired certificate. Check for it and if it's the case renew it or extend the validation.
    3. The certificate chain was not in correct order. Basically the server certificate chain should be in order
    Own->Intermedite->Root. To explain in detail, if your server certificate is A which is issued by an intermediate CA B and then B's certificate is issued by the C which is the root CA (having a self signed certificate).
    Then your certificate chain contains 3 elements A->B->C. So you need to have the right order of certificate in the chain. If the order is B first followed by A followed by C, then the IAIK library used by PI cannot verify the server as trusted. Generate the certificate in the right order and then import this certificate in the TrustedCA keystore view and try again.
    4. If the end point of the SOAP Call(Server) is configured to accept a client certificate(mandatory), then make sure that it is configured correctly in the SOAP channel and it is also within validity period.
    (This certificate is the one which is sent to Server for Client authentication)
    As a resource, you may need to create a new SSL Server key.
    The requirement from SAP SSL client side is that the requested site has to have certificate with CN equal to the requested site.  I mean if I request URL X then the CN must be CN=X.
    In other words, the CN of the certificate has to be equal to the URL in the ftp request. This can be the IP address or the full name of the host.
    Request the url with the IP of the SSL Server and the certificate to be with CN = IP of the server.
    In any other case the SSL communication will not work.
    Regards,
    Caio Cagnani

  • 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

  • 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 FTP SSL SSL Certificate Exception

    After reviewing the results of searching on this error, I do not find anything that fits my situation:
    SAP File Adapter (PI 7.1) using FTP with FTPS connection security.
    I am not using X.509 certificate for client authentication.
    My connection is using a non-public certificate.
    I have added the SSL certificate to TrustedCAs and DEFAULT keystores.
    I am getting the following error:
    Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error when getting an FTP connection from connection pool: com.sap.aii.af.lib.util.concurrent.ResourcePoolException: Unable to create new pooled resource: iaik.security.ssl.SSLCertificateException: Peer certificate rejected by ChainVerifier
    Since I am using an non-public certificate, it will not validate. Even adding to the TrustedCAs and DEFAULT keystore it seems the configuration is still attempting to validate the certificate.
    Any recommendations?

    Hi,
    The main reasons for this error are:
    1. The correct server certificate could not be present in the TrustedCA
    keystore view of NWA. Please ensure you have done all the steps
    described in these two URLs:
    Security Configuration at Message Level
    http://help.sap.com/saphelp_nwpi71/helpdata/EN/ea/c91141e109ef6fe1000000
    0a1550b0/frameset.htm
    2. The server certificate chain contains expired certificate. Check for
    it (that was the cause for other customers as well) and if it's the case
    renew it or extend the validation.
    3. Some other people have reported similar problem and mainly the
    problem was that the certificate chain was not in correct
    order. Basically the server certificate chain should be in order
    Own->Intermedite->Root. To explain in detail, if your server certificate
    is A which is issued by an intermediate CA B and then B's certificate is
    issued by the C which is the root CA (having a self signed certificate).
    Then your certificate chain contains 3 elements A->B->C. So you need to
    have the right order of certificate in the chain. If the order is B
    first followed by A followed by C, then the IAIK library used by PI
    cannot verify the server as trusted. Please generate the certificate in
    the right order and then import this certificate in the TrustedCA
    keystore view and try again. Please take this third steps as the
    principal one.
    Hope it solves your querie.
    Regards,
    Caio Cagnani

  • Iaik.security.ssl.SSLCertificateException - the mother of all errors

    Hi,
    We're experiencing this error:
    Error occurred while connecting to the FTP server "whatever:whichever": iaik.security.ssl.SSLCertificateException: Peer certificate rejected by ChainVerifier
    when connecting to the FTPS server.
    What was done by the teams:
    1) Every single certification was checked, there is pretty much no way this is a certificate problem
    2) Nothing was changed in the systems, this is an overnight error than kept persisting
    3) We restarted both involved servers, this keeps on bugging us
    4) No relevant traces are in SMICM, ST11, ST22, SM21, anywhere
    5) NOTHING was changed on any of the two servers.
    6) In addition, also the development PI server tries to connect to the same FTPS server and the same error appears.
    This is an overnight problem that just didn't disappear whatever we did.
    From my experience with this precise error which I can say it is now of more than a year is that it kept popping up in our system and it was triggered from causes as vast as some FTPs processes hanging on the FTPS server requiring restart, to filling the space on the server, not updated DNS cache on the PI server, you name it.
    I'm really amazed the amount of times this error pops up in the CC monitor and the cause is everything else BUT a certification issue.
    Do you have any idea worth sharing on why this might happen out of the blue?
    Best regards,
    George

    Hi George,
    I have a similar issue here and have tried out all the possible options.
    1) Imported certificate into Trusted CA's from a server where the connectivity is working fine.
    2)Restarted the Java stack.
    You Mentioned about FTPS server. Can you please confirm where else do  we need to import the certificate?

  • 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!

  • 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

  • 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

Maybe you are looking for

  • MacBook Pro 13" Magsafe issues

    Hey guys I have a late 2011 mbp 13" I7 2.8 ghz. Issues faced are related with the magsafe port/battery I feel. What ussually happens is that i use the laptop on battery as well as charger at times, If the battery charge drops below 50% at times it wo

  • The problem in the thread pool implemented by myself

    Hello, I need to a thread pool in J2ME CDC 1.0 + FP 1.0, so I implemented a simple one by myself that also meets my own requirement. Here is the main idea: The thread pool creates a fixed number of threads in advance. When a task comes, it is put in

  • Verizon connectivity almost never works on my new iPad

    I'm wondering if others are seeing this. Here's what's happening: - this past Tuesday I signed up from my iPad for the $30/mo Verizon plan. I tested web browsing and it worked - subsequent attempts to use it failed. I see "Verizon LTE" and full bars

  • Problem in Custom function in I_TH_REF_DATA

    Hi All, I have a custom function where I have implemented interfaces IF_RSPLFA_SRVTYPE_IMP_CHECK & IF_RSPLFA_SRVTYPE_IMP_EXEC_REF. In method GET_REF_DATA_SEL I could specify the selection criteria to read reference data and system does read the refer

  • Drag and drop acting strangely after 10.8.5 upgrade

    Just yesterday I upgraded to 10.8.5 form 10.8.4 so I could use my new iPhone 5c with iTunes (got message I had to upgrade)> Since then I have had trouble dragging and dropping files into folders, folders into folders. E.g., when dragging a .jpeg out