Exception caught by adapter framework: RfcAdapter: receiver channel not in

Hi friends,
I am doing a file-RFC-file scenario. This is based on the blog: /people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit The company ID is sent to the RFC through a xml file. RFC will return the company details which will be written again into a xml file.
My source file is getting picked up. But while sending the company ID to the RFC, i am getting an error. It says: Exception caught by adapter framework: RfcAdapter: receiver channel not in list of running clientPools:. I have checked the RFC and is running perfectly.
Can anybody help me to solve this error?
Regards,
Divija.

Hi,
it is better to restart the RFC adapter engine.
Is this RFC adapter is active in the Adapter Monitoring ?
Also change the RFC adapter configuration and activate it. Then activate the Receiver Agreement.
Also refer SAP note -730870 ( question no 17 and 20)
Regards,
Moorthy

Similar Messages

Exception caught by adapter framework: No configuration / default adapter specified for EDISeparator

Hello Experts,
I am configuring the scenario ( AS2 to EDISeparator and EDISeparator to IDOC ).
Can you please help me with the error below which is from the either the EDISeparator Receiver channel or the EDISeparator Sender channle.
09.06.2014 17:52:18.709
Information
Message is encrypted with 1.3.14.3.2.7 algorithm
09.06.2014 17:52:18.778
Information
AS2 Message is signed with SHA1 (1.3.14.3.2.26) algorithm
09.06.2014 17:52:18.779
Information
AS2 Message message signature is validated, signer ID is X509CertSelector: [ Serial Number: 1624063516 Issuer: CN=Mendelson AS2 TEST,OU=Integration,O=Mendelson,L=Berlin,ST=Unknown,C=GE matchAllSubjectAltNames flag: true ]
09.06.2014 17:52:18.784
Information
AS2 document size is 350 Bytes
09.06.2014 17:52:18.784
Information
Payload charset converted from ISO-8859-15 to ISO-8859-15
09.06.2014 17:52:18.785
Information
B2B EdifactConverterModule : EDI format detected as EANCOM
09.06.2014 17:52:18.785
Information
B2B EdifactConverterModule: Message will be read as ISO-8859-1.
09.06.2014 17:52:18.785
Information
MP: processing local module localejbs/EdifactConverterModule
09.06.2014 17:52:18.785
Information
0}: The module-paramteter "eancom.subversion.prefix" is not set. Using default value "false"
09.06.2014 17:52:18.786
Information
0}: The module-paramteter "eancom..audit" is not set. Using default value "false"
09.06.2014 17:52:18.791
Information
MP: processing local module localejbs/CallSapAdapter
09.06.2014 17:52:18.791
Information
Application attempting to send an XI message asynchronously using connection AS2_http://sap.com/xi/XI/AS2
09.06.2014 17:52:18.792
Information
Trying to put the message into the send queue
09.06.2014 17:52:18.831
Information
Message successfully put into the queue
09.06.2014 17:52:18.831
Information
The application sent the message asynchronously using connection AS2_http://sap.com/xi/XI/AS2. Returning to application
09.06.2014 17:52:18.836
Information
MIC (DeJYUIusqQj6aaYRASdHhAo+4J0=) is calculated using SHA1 algorithm.
09.06.2014 17:52:18.838
Information
The message was successfully retrieved from the send queue
09.06.2014 17:52:18.843
Information
Message status set to DLNG
09.06.2014 17:52:18.845
Information
MDN is succcessfully signed with SHA1 (1.3.14.3.2.26) algorithm
09.06.2014 17:52:18.859
Information
Trying to put the message into the send queue
09.06.2014 17:52:18.912
Information
Message successfully put into the queue
09.06.2014 17:52:18.913
Information
The message was successfully retrieved from the send queue
09.06.2014 17:52:18.918
Information
Message status set to DLNG
09.06.2014 17:52:18.961
Information
Trying to put the message into the send queue
09.06.2014 17:52:19.001
Information
Message successfully put into the queue
09.06.2014 17:52:19.001
Information
The message was successfully retrieved from the send queue
09.06.2014 17:52:19.006
Error
MP: exception caught with message No configuration / default adapter specified for EDISeparator
09.06.2014 17:52:19.006
Information
Delivering to channel: B2BSE00002_O2C_ORDERS_VANS_PO_WRITE_EDISeparator
09.06.2014 17:52:19.006
Information
Message status set to DLNG
09.06.2014 17:52:19.009
Error
Exception caught by adapter framework: No configuration / default adapter specified for EDISeparator
09.06.2014 17:52:19.010
Error
Transmitting the message to endpoint <local> using connection AS2_http://sap.com/xi/XI/AS2 failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.Exception: No configuration / default adapter specified for EDISeparator
09.06.2014 17:52:19.015
Information
The asynchronous message was successfully scheduled to be delivered at Mon Jun 09 17:57:19 CEST 2014
09.06.2014 17:52:19.015
Information
Message status set to WAIT

Hello Ruchir Sinha and Dimitri Sannen,
I think I have progressed a bit. Just unsure of the usage of the Module configuration .I now get a new error (see below) and the updated config details are :
Sender Interface :
Receiver Interface :
Sender AS2 config :
Receiver EDISeparator config :
Sender EDISeparator config :
Receiver IDOC config :
IDoc details configured but not added in this document
16.06.2014 11:52:35.414
Information
The message was successfully retrieved from the send queue
16.06.2014 11:52:35.420
Information
Delivering to channel: B2BSE00002_O2C_ORDERS_VANS_PO_WRITE_EDISeparator
16.06.2014 11:52:35.420
Information
MP: processing local module localejbs/ModuleProcessorExitBean
16.06.2014 11:52:35.420
Information
Message entered AF MP exit bean and will now be passed to the JCA adapter
16.06.2014 11:52:35.420
Information
Message status set to DLNG
16.06.2014 11:52:35.433
Information
UNA segment UNA found
16.06.2014 11:52:35.444
Information
Parsed UNB segment 333333333/014 to 111111111/014
16.06.2014 11:52:35.445
Information
Parsed UNH segment ORDERS D96A
16.06.2014 11:52:35.514
Information
Searching sender channel for Eancom message part message with Message type ORDERS, Message version number D, Message release number 96A, Interchange sender identification 333333333, Interchange sender identification code qualifier 014, Interchange recipient identification 111111111, Interchange recipient identification code qualifier 014, Message Subversion EAN008, Message Agency UN
16.06.2014 11:52:35.579
Information
Sender channel (Channel) keys: ObjectId=7abf551ddbb638268f91af80ec1c04c8 values: ToPartySchema= Attributes=(Attributes:Channel:EDISeparator:INBOUND) values: edisep.advanced=false snd.interchangeSenderId=.* snd.tradacommessagetype=.* snd.xpath= snd.xpath.value= snd.filterCondition=equal snd.edifactMessageReleaseNumTxt= snd.tradacomMessageTypeUsingFreeText=false snd.eancomMessageReleaseUsingFreeText=false snd.eancomMessageVersionFreeText= snd.odetteMessageType=.* snd.edifactMessageVersion=.* snd.xml.splitPath=null snd.eancomMessageVersion=.* snd.odetteMessageVersion=.* snd.edifactMessageRelNumUsingFreeText=false snd.otherVersionReleaseIndustryIdentifierCodeEnabled=false adapterStatus=active snd.vdaMessageType=.* snd.eancomCONTRLMessageRelease=3 snd.odetteMessageTypeTxt= snd.tradacommessageversion=.* snd.edifactMessageVerNumUsingFreeText=false snd.edifactMessageTypeUsingFreeText=false snd.xpathUsingFreeText=false snd.interchangeSenderIdCode=.* snd.otherVersionReleaseIndustryIdentifierCode=.* snd.odetteMessageTypeUsingFreeText=false snd.tradacomreccode=.* snd.edifactMessageVersionFreeText= snd.edifactInterchangeRecipientIdentification=.* eoio.sequenceId= snd.edifactMessageTypeTxt= snd.odetteMessageVerNumUsingFreeText=false snd.eancomMessageVerNumUsingFreeText=false snd.interchangeReceiverId=.* snd.eancomMessageRelease=.* snd.tradacomsendername=.* snd.tradacomMessageTypeTxt= snd.vdaLieferantenNummer=.* snd.interchangeReceiverIdCode=.* snd.edifactInterchangeSenderIdentificationCode=.* snd.odetteMessageVersionFreeText= snd.versionReleaseIndustryIdentifierCode=.* snd.edifactInterchangeSenderIdentification=.* snd.edifactMessageType=.* snd.eancomMessageType=.* snd.xpathTxt= snd.vdaMessageTypeTxt= deliverySemantics=eo snd.eancomMessageReleaseTxt= snd.plainmessagetype=.* snd.xml.split=false snd.edifactMessageRelease=.* snd.vdaMessageTypeUsingFreeText=false snd.tradacomrecname=.* edisep.addParameterParams=TableData: edisep.addParameterParams {} snd.encoding=iso885915 snd.vdaKundenNummer=.* snd.tradacomsendercode=.* snd.edifactCONTRLMessageRelease=3 snd.edifactInterchangeRecipientIdentificationCodeQualifier=.* snd.transactionSetIdentifierCode=.* Service=ASJAVA_DX5 Channel=B2BSE00002_O2C_ORDERS_PO_ECC_READ_EDISeparator EngineType=CA Party= TransProt=XI TransProtVers=1.0.0 FromPartySchema= FromPartyAgency= Direction=I MsgProt=EANCOM MsgProtVers=1.0.0 EngineName= AdapterType=EDISeparator AdapterSWCV=06c536e6fafe11e0bb1cea8f0a4290b1 ToPartyAgency= AdapterNamespace=http://sap.com/xi/XI/EDISeparator found. New message ID is f18894a8-f53b-11e3-a748-00001e96c7e2
16.06.2014 11:52:35.586
Error
MP: exception caught with cause javax.resource.ResourceException: com.sap.aii.adapter.ediseparator.ra.integration.DispatchException: Message cannot be dispatched: Message cannot be dispatched: Error during processing local class: localejbs/GenericConverterModule
16.06.2014 11:52:35.586
Error
Message could not be forwarded to the JCA adapter. Reason: com.sap.aii.adapter.ediseparator.ra.integration.DispatchException: Message cannot be dispatched: Message cannot be dispatched: Error during processing local class: localejbs/GenericConverterModule
16.06.2014 11:52:35.590
Error
Exception caught by adapter framework: com.sap.aii.adapter.ediseparator.ra.integration.DispatchException: Message cannot be dispatched: Message cannot be dispatched: Error during processing local class: localejbs/GenericConverterModule
16.06.2014 11:52:35.591
Error
Transmitting the message to endpoint <local> using connection AS2_http://sap.com/xi/XI/AS2 failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: javax.resource.ResourceException: com.sap.aii.adapter.ediseparator.ra.integration.DispatchException: Message cannot be dispatched: Message cannot be dispatched: Error during processing local class: localejbs/GenericConverterModule

Regarding error showing as exception caught by adapter framework

hi all.
here in my scenario iam doing a file to rfc.
but when iam sending a file to rfc and when i see in sxmb_moni its showing as sucess.
bue when i look at runtime workbench under message monitoring (tab) it was showing as
MP: exception caught with cause com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback.
Delivery of the message to the application using connection RFC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Exception thrown in method process. The transaction is marked for rollback.: com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback..
SO WHAT COULD BE THE ERROR IS THE EROR THAT WS SHOWING RELATED TO XI R SAP R3(system that was recieving)
waiting for the excellent answer.
cheers.
seeta ram.

HI Matias.
yes i did with the custom Rfc and the result is still the same
and to be more confident i was creates another xi scenario from file to Standerd Bapi BAPI_COMPANYCODE_GETDETAIL by creating a simple file with only one field and mappedwith only the request Message type of this Bapi and tested it.
and even this scenario is also showing the same in reciever rfc and under runtime work ench its showing the same as my old scenario and it is as follows
2007-10-15 10:47:51 Success Message successfully received by messaging system. Profile: XI URL: http://jssxid0:50000/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER
2007-10-15 10:47:51 Success Using connection RFC_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2007-10-15 10:47:51 Success Message successfully put into the queue.
2007-10-15 10:47:51 Success The message was successfully retrieved from the receive queue.
2007-10-15 10:47:51 Success The message status set to DLNG.
2007-10-15 10:47:51 Success Delivering to channel: ReceieverChannel_RFC
2007-10-15 10:47:51 Success MP: entering
2007-10-15 10:47:51 Success MP: processing local module localejbs/RfcAFBean
2007-10-15 10:47:51 Error MP: exception caught with cause com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback.
2007-10-15 10:47:51 Error Exception caught by adapter framework: Exception thrown in method process. The transaction is marked for rollback.
Time Stamp Status Description
2007-10-15 10:47:51 Error Delivery of the message to the application using connection RFC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Exception thrown in method process. The transaction is marked for rollback.: com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback..
2007-10-15 10:47:51 Success The asynchronous message was successfully scheduled to be delivered at Mon Oct 15 10:52:51 SAST 2007.
2007-10-15 10:47:52 Success The message status set to WAIT.
2007-10-15 10:52:52 Success Retrying to deliver message to the application. Retry: 1
2007-10-15 10:52:52 Success The message was successfully retrieved from the receive queue.
2007-10-15 10:52:52 Success The message status set to DLNG.
2007-10-15 10:52:52 Success Delivering to channel: ReceieverChannel_RFC
2007-10-15 10:52:52 Success MP: entering
2007-10-15 10:52:52 Success MP: processing local module localejbs/RfcAFBean
2007-10-15 10:52:52 Error MP: exception caught with cause com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback.
and the message in sxmb_moni shows as it is processed sucessfully and
at reciever rfc as
Receiver channel 'ReceieverChannel_RFC' for party '', service 'CD103' (internal name 'RfcClient[ReceieverChannel_RFC]')
Client data: {jco.client.lang=en, jco.client.snc_mode=0, jco.client.client=103, jco.client.passwd=******, jco.webas.ignore_jdsr_error=1, jco.client.user=mandapativ, jco.client.sysnr=00, jco.client.ashost=168.89.182.33}
Repository data: {jco.client.lang=en, jco.client.snc_mode=0, jco.client.client=103, jco.client.passwd=******, jco.webas.ignore_jdsr_error=1, jco.client.user=mandapativ, jco.client.sysnr=00, jco.client.ashost=168.89.182.33}
Current pool size: 0, maximum pool size : 1
waiting for your great answer.
cheers.
seeta ram.

Exception caught by adapter framework: unable to create a socket

Hi All,
I am using Idoc to XI To SOAP scinario. I got a alert asying that some messsage id is error. When i am trying to monitor that massage by taking help of the messgae id in the alert the message was successful in the SXMB_MONI,. Then i Went to message monitoring There the message statu was syetem error. Errror log is *Exception caught by adapter framework: unable to create a socket*. The communication channel was inactive wehere as the statsu of the channel was active in the directory... what is the reasonm for this error. and how to resilev this.

As pointed already, a socket exception occurs when then message cannot pass the Firewall settings....there will be a port configured to send message to the SOAP receiver.....ask network guys to make relevant settings so that the port is free from Firewall restrictions.
@Supriya --> Active/ Inactive status of the channel in ID and in CC monitoring are different things.
To change the status of your CC in RWB --> Stop & Start your SOAP CC....the channel will remain inactive till no message is passed through it....once a message is passed the status will change to success/ error.
You can also change the CC status to Automatic.
Regards,
Abhishek.

Exception caught by adapter framework

Hi
My scenario is based file -->RFC with BPM (parforEach) and multimapping.
File adapter is picking data according to input file, but RFC couldn't able to process each split data. I am gettign following error.
2006-09-11 10:39:07 Error Exception caught by adapter framework: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: functiontemplate from repository was <null>
2006-09-11 10:39:07 Error Delivery of the message to the application using connection AFW failed, due to: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: functiontemplate from repository was <null>.
Any idea how to resolve this issue..!
Regards
Sankar!

Hi..
Does this way i mapped file to BAPI, is this correct way ?
does we change the BAPi structure like this in target side?
Source Structure: TargetStructure
Messages (1:1) Message(1:1)
Message1(1:1) Message1(1:1)
MT_Request(1:1)
Recordset(0:U) --> BAPI_INCOMINGINVOICE(0:U)
HDR (0:1) HeaderData(1:1)
LINEITEM(0:U)
 field1(0:1) ---> filed1(0:1)
 field2(0:2)
 HDR--->GLACCOUNTDATA(0:1)
LINEITEM(0:U)---> item(0:U)
field3(0:1) ---> field(0:1)
field4(0:1) ---> field2(0:1)
and my BPM is :
Receive>Transfromation->Block with asyncSEND--->
Receiver : File_MI
Trasformation: IM, sorec: File_AI and tar: BApi_AI
Block -->parForeach, multi: BAPI_AI, curr: BAPI_AI
asyncSend-->BAPi_AI
Note: My input file should have various headers with associated line items...!
Thanks,
Sankar!

Debugging for exceptions caught by adapter framework

I am getting an error ' Exception caught by adapter framework while processing message to remote system..'
Is there any way to debug in such cases.
while executing sxmb_moni i am getting status processed successfully but getting an error in the runtime workbench of XI in message monitoring for component adapter engine.

Tamoghna,
This error comes when the adapter is not able to communicate with the target system. eg, if it is a JMS scenario, and the host is not reachable then you get this error. If you are in a domain, try to give fully qualified system name or ip address.
regards,
Felix

Exception caught by adapter framework: error while processing message to ..

URGENT:
Legacy >XI>R3 interface
SAP XI (file_adapter --> RFC_adapter)
Friends.
 I need your help for next problem above:
Delivery of the message to the application using connection RFC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: functiontemplate from repository was <null>: com.sap.aii.af.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: functiontemplate from repository was <null>.
Thanks very much for your helps
Nota: This error is XIPRO environment.
Message was edited by:
 Cristian Alejandro Toro Salazar
Message was edited by:
 Cristian Alejandro Toro Salazar

Hi Cristian,
>>>>functiontemplate from repository was
this SAP note 730870 - describes your issue
let me know if it helped
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

ICH :Exception thrown by adapter framework

i am working on a scenario for Supplier Managed Inventory
Process flow for initial data transfer is from R/3 (IDoc)>XI(XML)>SCM(XML)
We are using sap standard mappings to perform the conversion to XML. SXMB_MONI in XI shows "processed successfully" but getting error in runtime workbench in message monitoring of component 'adapter engine'. the error log is showing:
Error Exception caught by adapter framework:
error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: functiontemplate from repository was.
Error Delivery of the message to the application using connection AFW failed, due to: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: functiontemplate from repository was .
I am sending Product Activity Notification Idoc PROACT01. what adapter should i use. I tried using HTTP and XI adapter and it is not working. now i am trying RFC adapter and standard mappings from SCM Content , but getting this error. How can I troubleshoot this?

Hello Tamoghna,
If I've understood your scenario well, you should be using the IDoc Adapter. Assuming that you have an IDoc from the sending system, you need not do any XML conversion. This will avoid any XML related errors.
The error appears to be connection related. Please check that your Target system connection properties are defined in XI (TCode SM59). Also make sure the ALE name in the SLD is correct.
Let me know.
Regards,
Homiar.

RfcAdapter: receiver channel has static errors: can not instantiate RfcPool

HI,
While transferring the project from SAP system to PRIMVERA (third party system) system, iam getting the following error:
com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: RfcAdapter: receiver channel has static errors: can not instantiate RfcPool caused by: com.sap.aii.adapter.rfc.RfcAdapterException: error initializing RfcClientPool:com.sap.aii.adapter.rfc.core.repository.RfcRepositoryException: can not connect to destination system due to: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=192.168.215.138 SYSNR=02 GWHOST=192.168.215.138 GWSERV=sapgw02 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '192.168.215.138apgw02' not reached TIME Sun May 01 06:10:03 2011 RELEASE 710 COMPONENT NI (network interface) VERSION 39 RC -10 MODULE nixxi.cpp LINE 3133 DETAIL NiPConnect2: 192.168.215.138:3302 SYSTEM CALL connect ERRNO 10060 ERRNO TEXT WSAETIMEDOUT: Connection timed out COUNTER
experts, kindly help me out in resolving this issue.
Regards,
Sai

partner '192.168.215.138apgw02' not reached
Well if you ask me, theres something seriuosly wrong with above "partner", review the config of the RFC/JCO,
also you could add more details as above info on its own is not enough to give you and objective answer
Regards
Juan

XMBWS.Timeout in soap receiver channel not working

Hello
I have a requirement where my soap receiver channel should time out in 20 sec from the time it had shot a webservice request.
I tried setting the module parameter XMBWS.Timeout to 20000 but it didnt work. I assume this parameter should be set for the standard module i.e. sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean.
Currently my receiver channel is timing out after every 3 min and that might be because the parameter xiadapter.inbound.timeout.default in SAP NWA is set to 180000.
Any other parameter to be set so that channel takes time out duration from module parameter.
Note: we are working on PI 7.1 EHP1
Regards
Shailesh

>
Shailesh Kunjiraman wrote:
> i doubt if this can be reduced to value lower than a minute.
i agree. A minute is usually the minimum value for lot many parameters.

JMS Adapter Fail - Receiver channel. Details: Receive timed out

Its an IDOC to JMS scenario. IDOC gets processed through the pipeline in XI successfully, can see the checkered flag.
However in Adapter monitoring, JMS adapter is in red.
The error text against the Communication Channel is "Receiver channel. Details: Receive timed out".
I am trying to connect to the JMS queue provided by a third party on port 1100 ( as configured in JMS adapter).My initial analysis is to check if the port is open on the third party's firewall( Need to get the response back from them yet).
However i would like to know, if there is something else that i should look into?

Following are the error messages in RWB audit log for the message sent.
Exception caught by adapter framework: The JMS channel with channel ID 3f307d6854683859b39f978a43e88872 is errornous. Details:Receive timed out
Error Delivery of the message to the application using connection AFW failed, due to: The JMS channel with channel ID 3f307d6854683859b39f978a43e88872 is errornous. Details:Receive timed out.
what might be the problem?

File adapter receiver channel is not initialized.

Hi
iam wrking idoc-file scenario, as per the requirement i have created 4datatypes 4 mapping in IR with 4 communaction chanles in ID. the scenarios is working fine with 3 mappings.but in 4 the scenario
the file genaraing properly , i have cheked in SXMB_moni payload but it is not creating in destination system
in runtimeworkbench->message-monitaring-> adpater
i have find the below issues
1) File adapter receiver channel CC_DDPWCS_US_TO_101 is not initialized. Unable to proceed: null Error 2) Exception caught by adapter framework: File Adapter configuration not initialized:
3) Error Delivery of the message to the application using connection AFW failed, due to: File Adapter configuration not initialized:.
please tell me how can i reslove the issue
thanks
niru

Hi
i have checked the content convertion and changed as below
the structure is
Row.fieldNamesTrans_Id,Order,Item,Product_Id,Product_desc,Lot_nr,Ship_via,Exp_qty,Carousel_loc,compart,Destination,Label
Row.fieldSeparator     ,
Row.fieldFixedType     char
Row.endSeparator     'nl'
Row.addHeaderLine     4
Row.headerlineTrans_Id,Order,Item,Product_Id,Product_desc,Lot_nr,Ship_via,Exp_qty,Carousel_loc,compart,Destination,Label
even though iam facing the issue. iam wondering "_i have used in the similar structure for other 3 mappings in same scenario those are working perfect "_ but based on condition if 4 th mapping is executed iam facing the problem
error message in RWB/Adapeters
File adapter receiver channel CC_DDPWCS_US_TO_101 is not initialized. Unable to proceed: null
Error Exception caught by adapter framework: File Adapter configuration not initialized:
Error Delivery of the message to the application using connection AFW failed, due to: File Adapter configuration not initialized:.
please help if any of you face the similar situation , i struck-up long ago here
regards
niru

Exception in Adapter Framework

Hi,
I'm receiving the following error from my Adapter Framework:
Exception caught by Adapter Framework: Cannot lookup the ra connectionfactory. Reason: Path to object does not exist at XXXXX, the whole lookup name is deployedAdapters/XXXXXX
This error occurs in the 'delivering' step from Integration Engine to Adapter Enging: messages continue staying in that status. When I restart the Adapter Engine, the message are set to System Error, so I can work around it, but I'm more interested in why this error occurs.
I'm using a XI 3.0 system, SP 17.

Hi
the adapter has to register in JNDI with the name "deployedAdapters/sample_ra/shareable/sample_ra" as you have specified in ra.xml.
check whether the SPIManagedConnectionFactory,java file and the SampleRA.xml file, the JNDI name in both the files is deployedAdapters/sample_ra/shareable/sample_ra.
The JNDI name should be:
deployedAdapters/com.sap.aii.adapter.sample.ra/shareable/com.sap.aii.adapter.sample.ra
Check the name in NWA: Problem Management -> JNDI Browser.
Adjust your adapter metadata accordingly.
Thanks

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,

Xi adapter framework

hello
I have a scenario RFC 2 WS sync and the message does not leave the XI to the WS.
the message that I see in the sxmb is
<?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: Missing faultcode; HTTP 200 OK</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
any suggestions?
Kfir

this is what I see there and it doesnt lead me anywhere.
am I right by saying that the message did not leave the XI? becuase I am not sure about it.
2009-03-02 10:23:23 Success Message successfully received by messaging system. Profile: XI URL: http://mgnt371:50000/MessagingSystem/receive/AFW/XI Credential (User): XIISUSER
2009-03-02 10:23:23 Success Using connection SOAP_http://sap.com/xi/XI/System. Trying to put the message into the request queue.
2009-03-02 10:23:23 Success Message successfully put into the queue.
2009-03-02 10:23:23 Success The message was successfully retrieved from the request queue.
2009-03-02 10:23:23 Success The message status set to DLNG.
2009-03-02 10:23:23 Success Delivering to channel: AdobeMailService_SOAP_RCV
2009-03-02 10:23:23 Success MP: Entering module processor
2009-03-02 10:23:23 Success MP: Processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
2009-03-02 10:23:23 Success SOAP: request message entering the adapter with user J2EE_GUEST
2009-03-02 10:23:23 Success SOAP: Web Services Security processing...
2009-03-02 10:23:23 Success SOAP: apply Web Services Security...
2009-03-02 10:23:23 Success SOAP: Web Services Security applied.
2009-03-02 10:23:24 Error SOAP: call failed: java.io.IOException: Missing faultcode; HTTP 200 OK
2009-03-02 10:23:24 Error SOAP: error occured: com.sap.aii.af.ra.ms.api.RecoverableException: Missing faultcode; HTTP 200 OK: java.io.IOException: Missing faultcode; HTTP 200 OK
2009-03-02 10:23:24 Error MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: Missing faultcode; HTTP 200 OK: java.io.IOException: Missing faultcode; HTTP 200 OK
2009-03-02 10:23:24 Error Exception caught by adapter framework: Missing faultcode; HTTP 200 OK
2009-03-02 10:23:24 Error Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Missing faultcode; HTTP 200 OK: java.io.IOException: Missing faultcode; HTTP 200 OK. Setting message to status failed.
2009-03-02 10:23:24 Error The message status set to FAIL.
2009-03-02 10:23:24 Error Returning synchronous error message to calling application: com.sap.aii.af.ra.ms.api.RecoverableException: Missing faultcode; HTTP 200 OK: java.io.IOException: Missing faultcode; HTTP 200 OK.

Exception caught by adapter framework: RfcAdapter: receiver channel not in

Similar Messages

Maybe you are looking for