Sender File adapter - Error after upgrade to SP16 !!

Hi ,
After upgrade from SP14 to SP16 , i see this error in Adapter monitor in rwb. The file does not get picked up. Any ideas on how to troubleshoot this ?
Configured at 2006-04-20 06:50:27 GMT
History:
- 2006-04-20 09:55:00 GMT: Retry interval started. Length: 30.000 s
- 2006-04-20 09:55:00 GMT: Error: BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback.
- 2006-04-20 09:55:00 GMT: Processing started
- 2006-04-20 09:54:36 GMT: Error: BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback.
- 2006-04-20 09:54:33 GMT: Processing started
Is there a patch that will fix this issue ?
Regards
matthias isenburg

thanks for yours tipps...
here the output of the defaultTrace.trc:
[EXCEPTION]
com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback.
     at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl0.process(ModuleLocalLocalObjectImpl0.java:118)
     at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java(Compiled Code))
     at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0.process(ModuleProcessorLocalLocalObjectImpl0.java(Compiled Code))
     at com.sap.aii.adapter.file.File2XI.send(File2XI.java(Compiled Code))
     at com.sap.aii.adapter.file.File2XI.processFtpList(File2XI.java(Compiled Code))
     at com.sap.aii.adapter.file.File2XI.invoke(File2XI.java(Compiled Code))
     at com.sap.aii.af.service.scheduler.JobBroker$Worker.run(JobBroker.java(Compiled Code))
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java(Compiled Code))
     at java.security.AccessController.doPrivileged1(Native Method)
     at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code))
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code))
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code))
Caused by: javax.xml.transform.TransformerFactoryConfigurationError: Provider com.sap.engine.lib.jaxp.TransformerFactoryImpl not found
     at javax.xml.transform.TransformerFactory.newInstance(Unknown Source)
     at com.euh.FileModule.GetFileNameBean.process(GetFileNameBean.java:76)
     at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl0.process(ModuleLocalLocalObjectImpl0.java:103)
     ... 11 more
Error during processing local bean localejbs/sap.com/com.euh.FileModule/GetFileNameBean
Module Exception 'com.sap.aii.af.mp.processor.ModuleProcessorException: Processing Error caused by: com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback.' found, cause: com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback.
Channel Orders_ftp_sender: Sending file failed with com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback. - continue processing
Should this traces give me more information?
mfg,
matthias

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 :
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 , , , , ,
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:
 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.
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:. 
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
After this, the system try to resend the message, and the same error appears several times.
Ty,
Manuel

Sender file adapter error

Hi,
The sender file adapter is reading a fixed width file . The file is not to be seen in the sxmb_moni. In the adapter monitoring is showing processed and green in color.
How do i resolve this issue.
In my recordset contains multiple substructures
<Recordset>
 <Header>
 type
 code
 id
 </Header>
 <Item>
 type
 qty
 price
 </Item>
</Recordset>
Header.fieldFixedLengths = 1,5,10
Header.endSeparator = 'nl'
Header.fieldNames = TYPE,CODE,ID
Header.keyFieldValue = 01
Item.fieldFixedLengths = 4,5
Item.endSeparator = 'nl'
Item.fieldNames = QTY,PRICE
Item.keyFieldValue = 02
What should i give in keyFieldValue . Is the above configuration correct.
Kindly suggest
Thanks
Varghese

Hi,
The key field value is normally a record type identifier. For example, a header record may always start with '1' or 'HD', and an item record may always start with '2' or 'IT' in your file. The 'type' field, which appears in both header and item records in your example, fits in as the identifier.
So, your parameters should be:
Header.fieldFixedLengths = 1,5,10 (or maybe 2,5,10)
Header.endSeparator = 'nl'
Header.fieldNames = TYPE,CODE,ID
Header.keyFieldValue = 1 (or maybe HD)
Item.fieldFixedLengths = 1,4,5 (or maybe 2,4,5)
Item.endSeparator = 'nl'
Item.fieldNames = TYPE,QTY,PRICE
Item.keyFieldValue = 2 (or maybe IT)
If your file has varying values of TYPE instead of 1,2 (or HD or IT), the File Adapter will not be able to handle the structured file. You may have to choose the option 'File without content conversion'.
Hope this helps,
Bhanu

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

Win7 Offline Files sync error after upgrade to Lion Server 10.7.2

Symptom: client is a Win7 laptop, the server is Mac OS X 10.7.3 Lion Server with SMB and AFP shares. Win7 Offline Files stopped working after I upgraded Snow Leopard (non-server version) to Lion Server 10.7.2. After updating to 10.7.3, the problem persists. When syncing, it gives thounsands of error like this: The process cannot access the file because it is being used by another process. WinXP clients are fine with the Offline Files function though.
I Googled and studied online for several days now and it might be related to the "Oppurtunistic Locking", or "Oplocks" for short, in the SMB protocol. Since Apple has re-written Samba, there's no "smb.conf" anymore to change the Oplocks setting. Maybe it's possible to change the setting in "com.apple.smb.server.plist"?
From the Internet:
1. Oplocks should be DISABLED on the server if there is any other file sharing protocol (AFP, etc.) other than SMB.
2. Offline Files will NOT work properly if Oplocks is disabled on the server side.
3. It was possible to config oplocks setting in smb.conf in Mac OS X versions prior to Lion but now there's no such config file.
My Question:
1. Does anyone else have similar problems?
2. Is it related to the Oppurtunistic Locking thing?
3. Is Oppurtunistic Locking enabled or disabled in Lion Server by default?
4. If it's related to Oplocks, how can I change the setting on the server?
5. I've noticed that the authentication from Windows PCs to the SMB share on the Lion Server is much slower then in SL. Could this somehow be related to my problem?
Thanks for your time! :-D

Any luck getting the info on SMBX parameters like OPLOCKS ? This is apparently causing an issue with Autodesk Revit. I am resorting to installing SMBUP.
There is an article that describes this method for altering the Lion smbd configuration parameters for honoring ACLs:
sudo defaults write /Library/Preferences/SystemConfiguration/com.apple.smb.server AclsEnabled -bool NO
from this article
http://support.apple.com/kb/TS4149
and this:
http://www.stanford.edu/group/macosxsig/blog/2011/08/enable-logging-with-107-smb x-w.html

File Upload error after upgrade to 1.6

After upgrade to HTML version 1.6 from 1.5 it's impossible to upload files to the Database.
The same effect apears during application import or when i try to uploaad an file inside of an application.
Does anyone know this? How to solve it?
Thanks
Thorsten

Scott said:
"You should probably revoke those grants, unless the user was HTMLDB_PUBLIC_USER. The DAD user should always be HTMLDB_PUBLIC_USER, unless you are using a dedicated DAD for database authentication, in which case that DAD should use a private document table. HTMLDB_PUBLIC_USER should already have access to the wwv_flow_file_objects$ unless something went wrong during installation."
I am facing a very similar problem since we upgraded to 1.6. File uploads do not work unless privileges on wwv_flow_file_objects$ are granted to the user (we use database authentication). By default, NO users or roles have access to this table. Does this mean that something went wrong during installation?
I am confused by this: "...unless you are using a dedicated DAD for database authentication, in which case that DAD should use a private document table." Does that mean that whenever database authentication is used, wwv_flow_file_objects$ is no longer the repository for uploaded files? How should it work then?

Seeburger As2 adapter error after upgrade

Hello,
After an upgrade from PI 7.01 to PI 7.11 we have problems with our AS2 seeburger adapter. We installed the compatible version of seeburger but got stuck on the following error:
Message could not be forwarded to the JCA adapter. Reason: Fatal exception: javax.resource.ResourceException: SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: java.io.IOException: org.bouncycastle.cms.CMSException: key inappropriate for algorithm., SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: java.io.IOException: org.bouncycastle.cms.CMSException: key inappropriate for algorithm.
Thanks a lot for any advice,
Regards,
Erik

Hi
Pls chk the security jar files. you can download the latest version of these from java portal. This might fix the issues related to Key.
Srikanth Srinivasan

Sender File adapter : Alert are possible.

Dear All
i had a Scenario of file to jdbc.I am using FCC(content conversion ) at sender file adapter.
if the file is not having proper text field,or if its's blank file...
i want to generate an alert..
while testing with a blank file , my file sender adapter is giving the error but their are no alert...
even in alert rule , i had specified file adapter ,Sender/Receive interface also
Rsalerttest : working properly.
Rsalertdisp : no dump for sender file adapter error
for mapping error my other alert rule are woking and generating the alert sucessfully.. for the same interface
any guess where could be the error..
Regards
Ajay Pant
null
Message was edited by:
 ajay pant

HI,
For alert configuration see the belowlinks,.But in your case if the send message having the empty fields, we can handle this in FCC parameters
xml.fieldoptional = yes
Parameter NameA.fieldFixedLengths defined.
○ If the inbound structure contains more fields than in NameA.fieldNames or NameA.fieldFixedLengths the conversion is executed.
Additional fields in the structure are ignored.
○ If the inbound structure contains less fields than specified in NameA.fieldNames, conversion is terminated with an error message.
If the last field only is shorter than defined or is missing completely, the conversion is executed. The contents of the last field are then applied to the XML element as found. Consequently, the value can be incomplete or empty.
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--step-by-step
for CCMS
/people/aravindh.prasanna/blog/2005/12/23/configuring-scenario-specific-e-mail-alerts-in-xi-ccms-part--1 -- ccms alerts - 1
/people/aravindh.prasanna/blog/2005/12/24/configuring-scenario-specific-e-mail-alerts-in-xi-ccms-part-2 -- ccms alerts -- 2
/people/aravindh.prasanna/blog/2006/02/20/configuring-scenario-specific-e-mail-alerts-in-xi-ccms-part-3 -- ccms alerts --- 3
Chilla

Sender File Adapter - No error, but not generating any message

I am working on a file to RFC scenario. The sender file adapter is using content conversion to read a comma delimited file. The file is being picked up and archived correctly, and the adapter monitor does not show any errors. However, the process disappears at this point. I don't see any messages in SXMB_MONI, and there is no sign that the process is reaching the RFC adapter. Has anyone ever had this happen before?
I have four line types for Buildings, Additions, Floors, and Rooms.
I list all four in the recordset structure, and I identify a key for each with the keyFieldValue parameter. I list a fieldSeparator of ',' and an endSeparator of 'nl' for each row. And i have a list of the fieldnames in the fieldnames parameter.
The only thing i'm not sure about is the keyFieldinStructure parameter. I have specified ignore there, because I don't want that field in my XML. Do I still need that field in my sender datatype, even if I'm ignoring it, or can I leave it out?
Thanks for any help. Please don't just list blogs unless they have something you think is helpful with my specific problem. I have already read all of the blogs that deal generally with the sender file adapter and file content conversion, and I need more specific help at this point.

I made one error before, it IS showing up in the Recovered Adapter Audit Log (it took that log about 10 minutes to open that particular tab so I didn't notice them there).
Here is what it says there:
2006-06-12 11:22:59 Success Channel CC_S_File_FIPM_Buildings: Entire file content converted to XML format
2006-06-12 11:22:59 Warning Channel CC_S_File_FIPM_Buildings: Empty document found. Proceed without sending message
2006-06-12 11:22:59 Success File "/interfaces/one line building.txt" archived after processing
Here are my parameters in the file content conversion:
Buildings.fieldNames RecordType,PLTXT,STORT,STREET,POST_CODE1,CITY1,REGION,PARNR,X_COORD,Y_COORD,ASSIGN_SQ_FT,BLDG_NUM,CAMPUS,GR_SQ_FT,NET_SQ_FT
Buildings.keyFieldValue 'B'
Buildings.fieldSeparator ','
Buildings.endSeparator 'nl'
Buildings.keyFieldInStructure ignore
Additions.fieldNames RecordType,ASSIGN_SQ_FT,BLDG_ABBR,CAMPUS,ADDITION,BLDG_USE,BLDG__NUMBER
Additions.keyFieldValue 'A'
Additions.fieldSeparator ','
Additions.endSeparator 'nl'
Additions.keyFieldInStructure ignore
Floors.fieldNames RecordType,BLDG_ABBR,CAMPUS,ADDITION,FLOOR,ASSIGNABLE_SQUARE_FOOT,BLDG_NUMBER
Floors.keyFieldValue 'F'
Floors.fieldSeparator ','
Floors.endSeparator 'nl'
Floors.keyFieldInStrucutre ignore
Rooms.fieldNames RecordType,SHTXT,MSGRP,ADDITION,ASSIGNED_DEPT,BLDG_ABBV,FLOOR_CAMPUS,AREA,RCD_CODE,DEPT_CODE,BUILDING_NUMBER,ROOM_COMMON_KEY
Rooms.keyFieldValue 'R'
Rooms.fieldSeparator ','
Rooms.endSeparator 'nl'
Rooms.keyFieldInStructure ignore
And here is my data type:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_FIPM_BuildingUpdate xmlns:ns0="urn:XXXXXX:FIPM:Buildings:SYS">
 <Buildings>
 <PLTXT/>
 <STORT/>
 <STREET/>
 <POST_CODE1/>
 <CITY1/>
 <REGION/>
 <PARNR/>
 <X_COORD/>
 <Y_COORD/>
 <ASSIGN_SQ_FT/>
 <BLDG_NUM/>
 <CAMPUS/>
 <GR_SQ_FT/>
 <NET_SQ_FT/>
 </Buildings>
 <Additions>
 <ASSIGN_SQ_FT/>
 <BLDG_ABBR/>
 <CAMPUS/>
 <ADDITION/>
 <BLDG_USE/>
 <BLDG_NUMBER/>
 </Additions>
 <Floors>
 <BLDG_ABBR/>
 <CAMPUS/>
 <ADDITION/>
 <FLOOR/>
 <ASSIGNABLE_SQUARE_FOOT/>
 <BLDG_NUMBER/>
 </Floors>
 <Rooms>
 <SHTXT/>
 <MSGRP/>
 <ADDITION/>
 <ASSIGNED_DEPT/>
 <BLDG_ABBV/>
 <FLOOR/>
 <CAMPUS/>
 <AREA/>
 <RCD_CODE/>
 <DEPT_CODE/>
 <BUILDING_NUMBER/>
 <ROOM_COMMON_KEY/>
 </Rooms>
</ns0:MT_FIPM_BuildingUpdate>
I'm going to recheck everything again, but maybe you guys will see something? I don't.
Vanda

Error when configuring Sender File Adapter (XI 7.0)

Hi all,
After i had configured my Sender File Adapter of Communication Channel 'CC_SEND_MATERIAL_FILE', an error message for this Communication Channel (in Runtime WorkBench/Component Monitoring/Adapter Engine/Communication Channel Monitoring) occurred as below:
Error: com.sap.aii.af.ra.ms.api.DeliveryException: java.net.MalformedURLException: unknown protocol: dest
I think that all configurations for this Sender File Adapter are correct. But i don't know where is protocol "dest" and how can i correct this protocol.
Could anyone please help me to resolve this problem?
Thanks for all in advance,
Vinh Vo

Hi Sarvesh,
Yes, i have configured the source file with the path in the AL11. I think all an other configurations are also OK. But i don't know what is protocol 'dest'.
Anybody can explain and help me, please!
Vinh Vo

System error when send file with Sender File Adapter

Hi all,
I have configured a "File To ABAP Proxy" scenario. After configuring, i executed a "Test Configuration" in Integration Directory and it's all OK. But this file unable to reach into ABAP Proxy Target. In the Runtime WorkBench\Message Monitoring, I get an error message in below:
Engine: Adapter Engine
Status: *System Error *
Start: 15.08.2008 14:04:01
End: 15.08.2008 14:19:01
Sender Service: BS_XI_SERVER
Interface Servic: urn://FILE_TO_PROXY
MI_EMPLOYEE_OB
In this case, I don't know why my Sender File Adapter is error and why status is "System Error" and why it can't reach into Target System. Can it concern a role user?
( For more clearly: I configured the source file and the path correctly. And i used the xml file with the content and the document name correctly. In general, the Sender Adapter File don't convert the sender file and its content is same as the Payload in the "Test Configuration", i think it is all OK.)
Could anyone please help me to resolve this problem, anyone can explain this error, how can i resolve this error?
Thanks a lot in advance,
Vinh Vo

Hi Chirag,
1.I source structure is very simple as below:
<ns0:MT_MATERIAL xmlns:ns0="urn://FILE_TO_PROXY">
 <MATERIAL>
 <WERKS>1000</WERKS>
 <MATNR>MAT00001</MATNR>
 <MAKTX>Chemical Material</MAKTX>
 </MATERIAL>
</ns0:MT_MATERIAL>
2. the Communication Channel Monitoring in Runtim WorkBench\Adapter Engine is OK for my Sender File Communication Channel, it's in Blue Light.
However, i don't know what's FCC?
Thanks and best regards,
Vinh Vo

Archive file with errors in sender file adapter not working! please help!

Hi Experts,
I have a file to RFC scenario. the input is a XML file. I have setup the flag in sender file adapter channel for archiving the input files with errors. But it is not working.
For testing I have used an invalid xML file for example without the main XML tag. I have also tested with a MSWORD file saved with.xml extension. But in both the cases the files are not getting archived.
My archive location permissions are fine and in fact normal archive operation is happening. That is, if I select the processing mode as "Archive" and gave the Archive directory then files are getting archived. The problem is only with the "Archive faulty source files" option.
What am I missing? DO I need to do some more configurations?
What are the prerequisites if any for this option?
How to test this?
Please help me! I will be greatfull to you all!
Thanks & Regards
Gopal

and go thru this links
Creating a Single Archive of the Version Files
http://help.sap.com/saphelp_nw04/helpdata/en/79/1e7aecc315004fb4966d1548447675/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/31/8aed3ea86d3d67e10000000a114084/frameset.htm
Note: reward points if solution found helpfull
Regards
Chandrakanth.k

Error in sender file adapter: source directory does not exist

Hi,
The PI system is 7.11
I've created sender file adapter with following details:
Transport Protocol : File System
Source directory: /interfaces/In
I checked in AL11 that this path really exists and it does. (I can even see the .txt file that should be processed.)
But still i get in Communication Channel Monitoring the following error:
"Configured Source directory "/interfaces/In" does not exist.
(i also tried to give the source directory as "interfaces/In" and as "//interfaces/In" but still the same error.
Any suggestions as to what is wrong?
kr
Robert

Actually, Need to use forward slash (/) to separate directory names in accordance with the Java specification.
But wanted to try if that works..
Also check directory name , path again as this is case sensitive...
--Divyesh

File to SOAP,error in sender file adapter

Hi,
I am doing a scenario FILE to SOAP where In file adapter I am using Quality od service as Exactly once in order.I am getting the below error.It works fine when I use QOS=Exactly once.Not sure why,can you guys please help me.Can we really use QOS-EOIO for sender file adapter,where exacly do we use it.
Thanks
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: invalid content type for SOAP: TEXT/HTML</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Edited by: guest xi on Apr 16, 2008 11:55 AM

Hi,
Thanks for your replies guys.I diid give the queue name ,I dont know what is causing the error.Now even QOS=EO which was working fine before is throwing an error.I am using the same file name for both
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: invalid content type for SOAP: TEXT/HTML</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>

Is Sender File Adapter always throws error when there is no file?

Hi,
I have a simple question but can't find a straight answer to it. I have a Sender File adapter that configured to pick up file XXX* from FTP server every 1 hour. But a file can come every 2, 3, or 7 hours- no certain time.When there is no file I got "File not found " error. As we use alerts, this behaviour is not acceptable.
Does this error comes always if there is no file? Any possible way to avoid this error ?
Thanks for help.
Nataliya

Hi Ravi,
I can see the error in Runtime Workbench under CC monitoring. To be precise it says:
An error occurred while connecting to the FTP server '1X.1XX.XX.XX:21'. The FTP server returned the following error message: 'com.sap.aii.adapter.file.ftp.FTPEx: 552 RMS-E-FNF, file not found, ES4_SAP*'. For details, contact your FTP server vendor.
My ftp server has the following set up:
Server: xx.xxx.xx.xx
Port:21
Dataconnection:Active
Timeout:120
Connection secuirity: None
User name .... etc set up.
Connect mode: Per file transfer
Transfer mode:Text
QoS:EO
Pollinterval: 120 (for test purposes)
Processing Mode: delete
Can it be that its a ftp server generates error and sends back to XI?
Thanks,
Nataliya

Sender File adapter - Error after upgrade to SP16 !!

Similar Messages

Maybe you are looking for