File Adapter Error FTPEx:553

Hi
I have cnfigured a file adapter and tryng to FTP a XML file and I am getting this error.
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Could not create file.: com.sap.aii.adapter.file.ftp.FTPEx: 553 Could not create file. For Details, contact your FTP server vendor.
Please help.
Thanks
Pavan

Is the message is successfully processed in the SXMB_MONI ?
If Yes , U don't sufficient authorization to create the files in the FTP server.
If no, check your repository objects again whether you have configured correctly or not.
Thanks

Similar Messages

File adapter error after updating to SP19 (INBOUND_BINDING_ERROR)

File adapter error after updating to SP19 (INBOUND_BINDING_ERROR)
Hi all,
im having some troubles after the installation of SP19 (from SP16 in NW04) with File Adapter (File->Idoc scenario).
In message monitoring (Adapter Engine), I have several messages with status "System Error". The error text is :
<i>Received XI System Error. ErrorCode: INBOUND_BINDING_ERROR
ErrorText: ErrorStack: Error in sender agreement for party '', service 'LEGACY_DEV', interface namespace 'http://XXXXX.com/XXXXXX', interface 'INTERFACE_OB' No sender agreement found for , , , , ,</i>
Im sure that the Integration Directory settings have not been changed. So I tried the following, but the problem persists:
- Deactivation/Activation of File Adapter channel
- check that user XIISUSER is not locked
- checked SXI_CACHE (it seems ok)
- Many CPA full refresh
- Dummy modifications of File Adapter channels (a dummy modification of the description)
- Reboot J2EE
I've seen that someone else had problems after upgrading to SP19. I'd really appreciate any suggestion of how to solve my issue.
Thank you
Manuel

Hi Prabhu,
I've already tried to restart server, but nothing happened. (Before update to SP19, the interface worked well).
This is the error log from message monitoring:
<i> 2007-01-16 16:37:34 Success Channel cc_File_Snd_Bolle: Entire file content converted to XML format
2007-01-16 16:37:34 Success Send binary file "BOLLE_20061229142059.CSV" from FTP server "AS810T:/sapinbound", size 8733 bytes with QoS EOIO
2007-01-16 16:37:34 Success Application attempting to send an XI message asynchronously using connection AFW.
2007-01-16 16:37:34 Success Trying to put the message into the send queue.
2007-01-16 16:37:35 Success Message successfully put into the queue.
2007-01-16 16:37:35 Success The application sent the message asynchronously using connection AFW. Returning to application.
2007-01-16 16:37:35 Success The message was successfully retrieved from the send queue.
2007-01-16 16:37:35 Success File "BOLLE_20061229142059.CSV" successfully archived on FTP server "AS810T" as "/sapinbound/bolle/20070116-163735-245_BOLLE_20061229142059.CSV"
2007-01-16 16:37:35 Success The message status set to DLNG.
<b>2007-01-16 16:37:35 Error Received XI System Error. ErrorCode: INBOUND_BINDING_ERROR ErrorText: ErrorStack: Error in sender agreement for party '', service 'LEGACY_DEV', interface namespace http://XXXXX.com/XXXXXX', interface 'INTERFACE_OB' No sender agreement found for , , , , ,
2007-01-16 16:37:35 Error Transmitting the message to endpoint http://SERVERNAME:8000/sap/xi/engine?type=entry using connection AFW failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: INBOUND_BINDING_ERROR:. </b>
2007-01-16 16:37:35 Success The asynchronous message was successfully scheduled to be delivered at Tue Jan 16 16:42:35 CET 2007.
2007-01-16 16:37:35 Success The message status set to WAIT.
2007-01-16 16:42:35 Success Retrying to send message. Retry: 1</i>
After this, the system try to resend the message, and the same error appears several times.
Ty,
Manuel

FILE ADAPTER ERROR IN FTP

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,
Y.Raj

Hi Raj,
1. Check whether the user you are using has access control i.e Read/Write Access from the folder in FTP server..
2. Check it at OS level by directly pasting or pick the files..
3. From SAP end check the user credientials provided in the file adapter i.e username of the FTP server and the Password of the FTP server it is case-sensitive.
4. Try to give the exact path from where the file is to be picked and reactivate the scenario.
5. what is the file size of the file that is going to be picked from the ftp server.
6. Then finally check in Communication channel monitoring detailed log what is the error it was coming and check the log in XI server you can clearly notice the error.
Even some times it will access at OS level but not through the server for this reactivate the adapter and provdie the user credentials and the path once again..
regards,
Kishore.

Sender File Adapter Error reading file

Hello!
I have a problem with reading a file using the FTP adapter.
I have configured everything according to the steps of weblog "FILE to JDBC Adapter using SAP XI 3.0" (/people/sap.user72/blog/2005/06/01/file-to-jdbc-adapter-using-sap-xi-30).
I know the sender FTP adapter can connect to the directory and file because:
1) it has complained about wrong format in the content conversion (has been fixed)
2) when there is no file for it there to pick up, the FTP flag in the adapter monitor is green
When I put a file in the specified directory I get the following error:
- 2006-06-21 09:52:23 CDT: Retry interval started. Length: 10.000 s
- 2006-06-21 09:52:23 CDT: Error: Retrieving file 'test_file.dat' failed unexpectedly: FTPEx: Public: The system cannot find the file specified.
- 2006-06-21 09:52:20 CDT: Processing started
- 2006-06-21 09:52:13 CDT: Error: Retrieving file 'test_file.dat' failed unexpectedly: FTPEx: Public: The system cannot find the file specified.
- 2006-06-21 09:52:10 CDT: Processing started
I also get the same error if I skip the content conversion and put a "ready" XML file there.
There should be no auth problems at all. Public server, and I can log on, get, put, delete etc. Also it can apparently read it since it can complain about the content format. Anyone seen this before?
Please advise. Thanks!
Nam

Hi Nam,
Is your User Id and User Id/Password is correct ?
Is connection mode is per file transfer in File Adapter configuration?
Also you can see the log from Visual Admin..
Regards,
Moorthy

Receiver File Adapter error

Hi all,
I am trying to convert the XML to Plain file in receiver file adapter. I am using module - StrictXml2PlainBean
My target structure is -
<MT_Name>
    <records>
        <Header>
        </Header>
        <Item>
        </Item>
    </records>
</MT_Name>
<Header> and <Item> are at same level.
When I use --
1. Header.fieldSeparator = ,
2. Item.fieldSeparator = ,
3. recordTypes = Header,Item
Then I get this error -
Message processing failed. Cause: com.sap.aii.af.app.modules.conversion.xml2plain.ConversionException: Invalid structure name encountered during conversion: records at XML element MT_Name,records
When I use --
1. records.fieldSeparator = ,
2. singleRecordType = records
Then I get this error -
Message processing failed. Cause: com.sap.aii.af.app.modules.conversion.xml2plain.ConversionException: The element nesting level for the structure MT_Name is too deep (reference: 3 levels, found: 4 levels) at XML element MT_Name,records,Header,Item
To add more details to the scenario, multiple records can be generated but one record will have only one Header, with multiple Items.
Any help in this regard will be highly appreciated.
Thanks,
Abhi

Hi Abhi,
Here you go....
For your target structure as:
<MT_Name>
<records>
<Header>
</Header>
<Item>
</Item>
</records>
</MT_Name>
Where I have assumed that <Header> and <Item> are at same level.
DO NOT use any Module just simply configure the receiver channel as below:
In the file Receiver Channel
Recordset Structure = Header,Item
Name                                                                    Value
Header.fieldSeparator                                             ,
Item.fieldSeparator                                                  ,
I have tried this and it works.
Let me know if you are facing any issues.
Cheers
Dhwani

Receiver file adapter error for special char.

I am using MTB in my receiver file adapter. I am getting a special character from source system at end of the string. How to resolve this type of error u2013 please advice.
This error is not coming for every message.
Error message:
Column value xxxx Â too long - must stop, probably configuration error in file adapter
Thanks
Vick

Hi,
Itu2019s basically IDOC to file scenario.
This error is coming for name field.
What I am thinking at this stage to do changes in MTB by define parameters like (NameA.enclosureConversion)

FTP connection error whil,e using flat file adapter error

while using file adapter in the reciever end for proxy to file
i am giving paranters like server IP address and the port , i dont know which port to give by default it is giving me 21 , anyway how to check whether the connection is correct
and more over
Message processing failed. 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: ConnectException: Connection timed out: connect
please help me in this thanks

HI Sridhar ,
First check wether server started or not and then check you are connecting to FTP server by
go to run -> cmd and write ping and ipaddress which is used and see whether u r getting reponse from teh FTP server.
Try to login to the ftp server which you have mentioned in CC using the user name and pwd, to chk whether you have the permissions to login to the server.
Also the check whether the folder you are trying to access is having permission for delete/read/write.
Restart the FTP server and try it again.
Regards
Sridhar Goli

File adapter error

Hi ,
While monitoring file adapter it is showing the error.
Processing Error: No suitable sender agreement found
In the integration directory i have defined Sender Agreement and also defined Sender communication channel.
The communication channel for file adapter is defined in the business sytems.
The file adapter is not picking the file from the file system.
Kindly suggest what could be the error
Thanks & Regards
Monzy

The sender agreement you have created may not be matching, you have to check your sender system/sender interface & sender namespace parameters again and see if your converted XML ouput by the adapter is matching these 3 parameters.
possible issue could be with ur sender namespace. are u reading XML file or CSV file. If CSV check the namespace definition in ur file content conversion config. it may not match the sender namespace definition in sender agreement. Hope it helps
-Saravana

Flat file with fixed lengths to XI 3.0 using a Central File Adapter---Error

Hi
According to the following link
/people/michal.krawczyk2/blog/2004/12/15/how-to-send-a-flat-file-with-fixed-lengths-to-xi-30-using-a-central-file-adapter
In Adapter Monitor I got the following error,
In sender Adapter,
Last message processing started 23:47:35 2008-10-25, Error: Conversion of complete file content to XML format failed around position 0 with java.lang.Exception: ERROR converting document line no. 1 according to structure 'Substr':java.lang.Exception: Consistency error: field(s) missing - specify 'lastFieldsOptional' parameter to allow this
last retry interval started 23:47:35 2008-10-25
length 15,000 secs
some one help me out ?
Thanks
Ram

from the blog you referenced -
<u> /people/michal.krawczyk2/blog/2004/12/15/how-to-send-a-flat-file-with-fixed-lengths-to-xi-30-using-a-central-file-adapter
<b>goto step 4</b>
<u>additional parameters</u>
add as the last entry
<recordset structure>.lastFieldsOptional Yes
e.g.,
Substr.lastFieldsOptional Yes

File Adapter Error Handling from Batch job

Dear all,
I'd like to handle error information by batch job process.
However I can't find out the error flag from the file adapter.
My XI setting is below.
1.FIle to File conversinn by using File adapter
2.Async setting
3.Not use BPM
Anyway,we only want to judge the status for XI process from Batch process like MS-DOS batch.
Kindly please tell me the detail explanation.
Regards,
Masayuki.

Hi Masayuki,
Please take a look at these..
http://help.sap.com/saphelp_nw2004s/helpdata/en/fa/09714d543b11d1898e0000e8322d00/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/fa/0971c2543b11d1898e0000e8322d00/frameset.htm
cheers,
Prashanth

File Adapter Error Handling

Hi All,
I am using File adapter to read the xml file and FTP it to another directory ( BPEL 10.1.3)
If i put any xml file in the input directory , it picks up the file and FTP it , but the as the xml file will not match the xsd, it out put some xml file which doesnt have any data. I
if the xml file not as per XSD then it should throw error or ?
If i put the correct xml file it FTP it to output directory with correct xml file.
My question is how do i handle the situation/error where xml file is not well formed or xml is not as per the xsd, so that it should stop the process and will log the error and put the file in some other directory.
Please help.
Thanks and Regards,
Vikram Singh

Hi,
Yes, i did checked in the folder.
Also did the following changes as per the Adapter dev guide, Now i am able to validate the file but its not writing the rejected file messgae to the specified director.
bpel.xml details -----
<BPELSuitcase>
<BPELProcess id="Airtricity_Credit" src="Airtricity_Credit.bpel">
<partnerLinkBindings>
<partnerLinkBinding name="Read_Credit_File">
<property name="wsdlLocation">Read_Credit_File.wsdl</property>
<property name="validateXML">true</property>
</partnerLinkBinding>
</partnerLinkBindings>
<activationAgents>
<activationAgent className="oracle.tip.adapter.fw.agent.jca.JCAActivationAgent" partnerLink="Read_Credit_File">
<property name="portType">Read_ptt</property>
<property name="rejectedMessageHandlers">
file://C:\product\10.1.3.1\OracleAS_1\bpel/samples/tutorials/124.AQAdapter/AQMessageRejectionHandler/rejected
</property>
</activationAgent>
</activationAgents>
</BPELProcess>
</BPELSuitcase>
++++++++++++++++++++++++++++++
Please help.
Thanks ,
vikram Singh

Receive File Adapter - Error in CallSAPAdapter Name not known

Using xml to File Adapter. Just want to store the xml file somewhere ie on XI Server in folder E:\usr\sap\interface\XMLfiles
Getting error in Adapter Engine - Exception caught by adapter framework: Object not found in lookup of CallSAPAdapter.
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: Object not found in lookup of CallSAPAdapter.: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of CallSAPAdapter..
Receiver Adapter configured to receive file write a .tmp version no conversion so set type to Binary.
I can see the Communication Channel in the monitor green.
Any ideas to find the problem
thanks,

I tried changing the communication channel as suggested with no further success. I have viewed the LogViewer on the server in cluster->server->logs defaultTrace.trc and com.sap.xi -> xi.log with no more information available.
So is it that I cannot do a simple XML send to file receiver and leave its content unchanged?
My test message payload was of the order
<?xml version="1.0"?><LIST><S_STX><C_STDS><D_STDS1>... with all the data in.
Adapter type = file
Receiver
Transport Protocol = File System (NFS)
Message Protocol = File
Adapter Engine = Integration Server
Target Directory = E:/usr/sap/Interfaces/XMLFiles (and tried it with /usr/sap/interface/XMLFiles)
Create filedirectory = ticked
Filename filename.xml
File Construction Mode = add timestamp
Write Mode = use temporary file
Temporary filename scheme = filename.tmp
Filetype = Binary
Module Tab
1 localejbs/CallSAPAdapter Local Enterprise Bean 0
and thats it.
On testing from the Integration Engine it reaches the Adapter Engine and reports the error as stated in my first post.
The message data is of the construct
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
- <SOAP:Header>
- <sap:Main xmlns:sap="http://sap.com/xi/XI/Message/30" versionMajor="3" versionMinor="0" SOAP:mustUnderstand="1" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
<sap:MessageClass>ApplicationMessage</sap:MessageClass>
<sap:ProcessingMode>asynchronous</sap:ProcessingMode>
<sap:MessageId>09c99665-f3cf-d247-993b-8cb46c37d820</sap:MessageId>
<sap:TimeSent>2007-09-19T16:42:31Z</sap:TimeSent>
- <sap:Sender>
<sap:Party agency="http://sap.com/xi/XI" scheme="XIParty">AS2</sap:Party>
<sap:Service>XMLFILE</sap:Service>
</sap:Sender>
- <sap:Receiver>
<sap:Party agency="http://sap.com/xi/XI" scheme="XIParty">MyCompany</sap:Party>
<sap:Service>XMLFILE</sap:Service>
</sap:Receiver>
<sap:Interface namespace="http://warburtons.com/genhdr">MI_XMLFILE_V3</sap:Interface>
</sap:Main>
- <sap:ReliableMessaging xmlns:sap="http://sap.com/xi/XI/Message/30" SOAP:mustUnderstand="1">
<sap:QualityOfService>ExactlyOnce</sap:QualityOfService>
</sap:ReliableMessaging>
- <sap:Diagnostic xmlns:sap="http://sap.com/xi/XI/Message/30" SOAP:mustUnderstand="1">
<sap:TraceLevel>Information</sap:TraceLevel>
<sap:Logging>Off</sap:Logging>
</sap:Diagnostic>
- <sap:HopList xmlns:sap="http://sap.com/xi/XI/Message/30" SOAP:mustUnderstand="1">
- <sap:Hop timeStamp="2007-09-19T16:42:31Z" wasRead="false">
<sap:Engine type="IS">is.00.srvsapxidev</sap:Engine>
<sap:Adapter namespace="http://sap.com/xi/XI/System">XI</sap:Adapter>
<sap:MessageId>09c99665-f3cf-d247-993b-8cb46c37d820</sap:MessageId>
- <sap:Branch>
<sap:MessageId>707ecbbd-a474-514d-b731-f4003c38c4df</sap:MessageId>
<sap:Party agency="http://sap.com/xi/XI" scheme="XIParty">ASD</sap:Party>
<sap:Service>IP_I_XMLFILE_Collect</sap:Service>
</sap:Branch>
- <sap:Branch>
<sap:MessageId>09c99665-f3cf-d247-993b-8cb46c37d820</sap:MessageId>
<sap:Party agency="http://sap.com/xi/XI" scheme="XIParty">MyCompany</sap:Party>
<sap:Service>XMLFILE</sap:Service>
</sap:Branch>
<sap:Info>3.0</sap:Info>
</sap:Hop>
- <sap:Hop timeStamp="2007-09-19T16:44:56Z" wasRead="false">
<sap:Engine type="AE">af.xid.srvsapxidev</sap:Engine>
<sap:Adapter namespace="http://sap.com/xi/XI/System">XIRA</sap:Adapter>
<sap:MessageId>09c99665-f3cf-d247-993b-8cb46c37d820</sap:MessageId>
</sap:Hop>
</sap:HopList>
</SOAP:Header>
- <SOAP:Body>
- <sap:Manifest xmlns:sap="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7">
- <sap:Payload xlink:type="simple" xlink:href="cid:[email protected]">
<sap:Name>PayloadName</sap:Name>
<sap:Description>PayloadDescription</sap:Description>
<sap:Type>Application</sap:Type>
</sap:Payload>
</sap:Manifest>
</SOAP:Body>
</SOAP:Envelope>
The Payload is
<?xml version="1.0" ?>
- <LIST>
etc
Message status
2007-09-19 17:44:56 Success Message successfully received by messaging system. Profile: XI URL: http://srvsapxidev:50000/MessagingSystem/receive/AFW/XI Credential (User): XIISUSER
2007-09-19 17:44:56 Success Using connection File_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2007-09-19 17:44:56 Success Message successfully put into the queue.
2007-09-19 17:44:56 Success The message was successfully retrieved from the receive queue.
2007-09-19 17:44:56 Success The message status set to DLNG.
2007-09-19 17:44:56 Success Delivering to channel: CC_toMyCompany_XMLFILE
2007-09-19 17:44:56 Error Exception caught by adapter framework: Object not found in lookup of CallSAPAdapter.
2007-09-19 17:44:56 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: Object not found in lookup of CallSAPAdapter.: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of CallSAPAdapter..
2007-09-19 17:44:56 Success The asynchronous message was successfully scheduled to be delivered at Wed Sep 19 17:49:56 BST 2007.
2007-09-19 17:44:56 Success The message status set to WAIT.
Now I have been reading all the documentation available and forum questions in this area but there is a lot of information but not quite for what I am currently trying to do. I need to preserve the xml file as xml for further processing. This is just a resting place for the file as I am trying to cut down a long running (over a day) collect BPM scenario by collecting the files in the directory then triggering the collect scenario to read in the files from this directory and perform all the processing and mapping in one chunk of short time. (But that is another story)
Any more suggestions appreciated could the SAPCallAdapter not be where I think it is? Does my directory and filename case have to be exact lower and upper case. (I will test this tomorrow)...and let you know if any difference and continue to read the links put on by the other person who answered.
thanks,

XI3.0 Inbound File Adapter Error on ModuleSLDAccessir.

Greeting,
I have just installed the technical Adapter for XI.3 I tried to use the Inbound File adapter, unfortunately I had two big issues:
1- I was able to execute run_adapter.bat but nothing was reaching the XI system.
When I checked the Log File: I found the following error:
Oct 13, 2004 1:22:08 PM ...aii.messaging.adapter.ModuleSLDaccess [Thread-9] Error: Initializing ModuleSLDaccessor failed with 'java.lang.NoClassDefFoundError: com/tssap/dtr/client/lib/protocol/HTTPException'
2- Second issue: when I try to access the adapter via the browser, the HTML page are not correct ! there is no text displayed. I just got code like : {!%5124_G_XMIT%!}
is there other setting to do ? I followed exactly the install book !
Thanks for your help.
Regards.
M. Zehana
Any help is more than welcome.

Check that you are using XI 3.0. You dont have to use the run_adapter.bat unless you are using the J2SE adapter ( which is 2.0 ) to communicate with an XI3.0 IS. If you have XI3.0 the adapters are configured in the integration directory which are now called communication channels. Therefore an inbound file adapter will be called a sender communication channel. You can create a communication channel either within a scenario or directly in the objects area for the Service ( business system etc ).
Mark

PI File Adapter Error.

Hi all,
I am facing one issue in the Production environment.My PI scenario is File to SAP R/3.At the source side file is being kept in one of the shared folder and PI file adapter is picking the file.When network goes down in the middle of processing a file form this shared folder PI file adpater is throwing some error as given below:
"Bean SMPP_CALL_JAVA_RUNTIME3not found on host XXX, ProgId =AI_RUNTIME_PRD"
Even though the network comes up after sometime we are getting the error as
"PERSIST">MESSAGE_NOT_FOUND"
If we try to reprocess the files it keeps on throwing the error until we remove the corresponding file (whose processing got interrupted) and refresh the cache.Once the corresponding file is removed PI will start processing the remaining files but the moment we keep the file which got stuck in PI it throws the error again "PERSIST">MESSAGE_NOT_FOUND".
Could someone throw some light on this as i have to remove the file from the source location everytime and reprocess it by renaming the file.
Thanks,
Lekshmi.

Hi all,
I have gone through the SAP note mentioned by Abhishek.Thanks for that,it will solve my issue.
But i want to clear my doubt regarding this error message.Whenever there is some network problem i.e. when the adapter fails to contact target system it gives some delievery exception and finally MESSAGE_NOT_FOUND.The same message can be found in the source location when this error is thrown in PI.Could someone provide any link which will explain why PI is throwing such error.I mean why is it unable to find an existing message in the source location???
In my case whenever it happens i will be informed by the source team that they are not receiving any response(so for the time being i can manage without configuring the alerts as it is not a frequent issue).But i wanted to know what is the root cause for this issue.
Regards,
Lekshmi.

Inbound File Adapter Error - NullPointerException

Hi,
We are on XI 3.0. We have a scenario of input file via inbound file adpater to R/3 using proxies.
When activating the communication channel (file adapter), an error is raised in the adapter monitor. The error states, "Error: Module Exception 'com.sap.aii.af.mp.processor.ModuleProcessorException' found, cause: java.lang.NullPointerException".
Does anyone have any ideas on this error?
Thanks in advance.
Best Regards,
Doo

Hi,
Can you check the communication channel - "Module" tab. A module processor has to be specified here. For the File Adapter the default value for the Module Processor should be "localejbs/CallSapAdapter" and the Type will be "Local Enterprise Bean".
Warm regards,
Venki.

File Adapter Error FTPEx:553

Similar Messages

Maybe you are looking for