Adapter Framework Archiving Failed

Hi!
We are running XI 3.0 SP14, the J2EE WAS 6.40 Adapter Framework archiving is not working.
Table XI_AF_MSG that is accessed via JDBC as a Resource on WAS is oversized and can´t get archived, so it keeps growing.
As it is SP14, archiving should be handled by the DAS or Data Archiving Service available as a J2EE Container Destination (service) (this is an assumption, based on online documentation).
Deletes are completed OK and state is green, however, archiving jobs are not executed and are displayed with a red circle, job log says error is UNKNOWN.
Looking at the J2EE server logs I found an exception involving the J2EE_GUEST user, and a 401 response. I have no clue as about what is going on. Is there something that has been misconfigured? Maybe an authorization profile missing? I would really appreciate your help, there is no information available on logs or http responses so any clue will help me a lot.
Exception comes out as follows:
#1.5#0011435BCF03006100001E2500001ED0000414A34A212A74#
1148591462750#com.sap.engine.services.httpserver##com.
sap.engine.services.httpserver#J2EE_GUEST#0####f8cc27e0e
c3211da90870011435bcf03#output##0#0#Error#1#/System/Server
#Plain###User J2EE_GUEST, IP address HTTP request processing failed. HTTP error will be returned. The error is Access Denied.No details available.#
#1.5#0011435BCF03001E0000000500001ED0000414A354F6F268#
1148591644531#com.sap.aii.af.ra.ms.impl.core.archiving.
ArchivingJobExecutor##com.sap.aii.af.ra.ms.impl.core.
archiving.ArchivingJobExecutor.executeArchivingJob()
####cimdesxi_CXD_107111450#Guest#
ba8ff880ec0511da9fe40011435bcf03#SAPEngine_System_Thread
impl:5_58##0#0#Error##Plain###Could not cancel archiving
session.#
Thanks in advance,
Regards,
Juan M.

Hello,
If you find a solution for this, could you provide it ?
I have the same problem.
Regards,
Chris

Similar Messages

Adapter framework selftest fails

Hi all,
I currently experiencing a problem with our XI installation. Since I've upgraded the installation to SP11 the component monitoring shows an error in the Adapter Engine. In the result of the selftest it says that : "Is a user defined for component AF?" fails. However the XIAFUSER is defined and also configured correctly.
Does anyone here has an idea how to solve this problem?
Thanks
Christian

Hi,
Adapter Framework
Adapter Engine is based on the adapter framework(AFWK). AFWK is based on SAP J2EE engine and the JCA. AFWK provides interfaces for configuration. This also provides common func to AE and PCK.It has his own queuing and logging service. In other words AFEK is the core of AE which provides common funtianality to all kind of adapters like monitoring, queuing and security.
 what is the differet between central adapter engine and
Central AE is installed by automatically by default along with the Integration server
There can be any number local AE's installed. The main reason for local AE is optmization/performance/ network/ OS security/ Firewall etc.. But the monitoring takes place centerally though the AE's are local. One more adv of Local AE is load is distributed.
Check out this link
http://help.sap.com/saphelp_nw04/helpdata/en/0d/5ab43b274a960de10000000a114084/content.htm
Thanks,
Prakash

Adapter framework failing to send message

Hi,
I am facing an issue in XI, where the adapter framework is getting failed to send the message. The message is also not getting reflected in SXMB_MONI,
"Transmitting the message to endpoint http://server:8080/sap/xi/engine?type=entry using connection AFW failed, due to: Received HTTP response code 404 : Not found."
No service using the ICM port 8080 is working though active. No XI service, even the ping service in sap/bc/ping is not working.
I have checked the following:
1) SLDCHECK (browser opening properly). In ABAP part i am getting error
Use transaction SLDAPICUST if you wish to maintain
Launching the SLD GUI in a separate browser window.
=> Verify in the browser GUI that the SLD is in a healthy running state!
Calling function LCR_LIST_BUSINESS_SYSTEMS
Retrieving data from the SLD server...
Function call returned exception code 3
=> Check whether the SLD is running!
Summary: Connection to SLD does not work
=> Check SLD function and configurations
for troubleshooting the above error i have gone through the link
http://help.sap.com/saphelp_nw04/helpdata/en/78/20244134a56532e10000000a1550b0/content.htm
Still the problem persists while calling function LCR_LIST_BUSINESS_SYSTEM
2) Then i checked the ping (path - http://server:8080/sap/xi/engine?type=entry ) -- its also not running and showing error :
Service cannot be reached with error code 404 not found.
3) The RFC XIINTEGRATION_SERVER is showing also showing error 404.
4) Checked ICM port - its 8080
Inspite of working hard over this issue, still unable to resolve this issue.
Please help me. Awaiting for your helping suggestions
Thanks in advance..

> Still the problem persists while calling function LCR_LIST_BUSINESS_SYSTEM
> 2) Then i checked the ping (path - http://server:8080/sap/xi/engine?type=entry ) -- its also not running and showing error :
> Service cannot be reached with error code 404 not found.
>
> 3) The RFC XIINTEGRATION_SERVER is showing also showing error 404.
> 4) Checked ICM port - its 8080
>
have a look for LCR_LIST_BUSINESS_SYSTEM in the below link
http://help.sap.com/saphelp_nw04/helpdata/en/78/20244134a56532e10000000a1550b0/content.htm
Regards,
Sarvesh

PI 7.11: Adapter Framework caught exception: null

Hi,
I've a ABAP Proxy - to - SOAP scenario.
Message mapping works.
In the communication channel monitor I get the following error:
MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException
Adapter Framework caught exception: null
In the log viewer in NWA I see the following two messages:
Marked transaction for rollback for meesage 516e304f-b083-8e3e-e100-00000a01095f(INBOUND). Reason: <null>
Caught exception com.sap.engine.interfaces.messaging.api.exception.MessagingException from application code with msgKey: 516e304f-b083-8e3e-e100-00000a01095f(INBOUND)
The payload for calling SOAP receiver looks like that:
<m:setEmployee xmlns:m="http://test.com" xmlns:fo="http://www.w3.org/1999/XSL/Format">
 <ns1:e xmlns:ns1="http://test.com">
 <address_Mail_Incoming_Type>
 <email>test.com</email>
 <phone>7890</phone>
 </address_Mail_Incoming_Type>
 <badge_ID>123</badge_ID>
 <cost_Center>321</cost_Center>
 <date_Hired>1980-01-01T00:00:00.000Z</date_Hired>
 <date_Of_Birth>1950-01-01T00:00:00.000Z</date_Of_Birth>
 <department>123</department>
 <division>ABC</division>
 <employee_Category>A</employee_Category>
 <employee_Code>1000</employee_Code>
 <employee_Id>1000</employee_Id>
 <employee_Status>ACTIVE</employee_Status>
 <first_Name>A</first_Name>
 <last_Name>B</last_Name>
 <letter_code_3>FRI</letter_code_3>
 <location>123</location>
 <position>123</position>
 </ns1:e>
 </m:setEmployee>
When I copy this payload into SOAP UI (surrounded by <soapenv:Envelope>, <soapenv:Header> and <soapenv:Body>), the WS call works.
The URL for the receiving CC should be ok (same as in SOAP UI), the "Do not use SOAP Envelope" checkbox is not flagged.
What can be the reason for that error message?
Thanks in advance!

I've now changed the setting of the external definition to "Using RPC style", but I'm still running into the same error than before:
10.02.2012 14:51:03 Information SOAP: sending a delivery error ack ...
10.02.2012 14:51:03 Error Adapter Framework caught exception: null
10.02.2012 14:51:03 Error MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException
10.02.2012 14:51:03 Information SOAP: sent a delivery error ack
10.02.2012 14:51:03 Error Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException.
The payload of the CC looks exactly the same than before:
<?xml version="1.0" encoding="UTF-8"?>
<m:setEmployee xmlns:m="http://test.com" xmlns:fo="http://www.w3.org/1999/XSL/Format">
 <ns1:e xmlns:ns1="http://test.com">
 <address_Mail_Incoming_Type>
 <email>test.com</email>
 <phone>123</phone>
 </address_Mail_Incoming_Type>
 <badge_ID>123</badge_ID>
 <cost_Center>123</cost_Center>
 <date_Hired>1990-01-01T00:00:00.000Z</date_Hired>
 <date_Of_Birth>1950-01-01T00:00:00.000Z</date_Of_Birth>
 <department>123</department>
 <division>ABC</division>
 <employee_Category>PERM</employee_Category>
 <employee_Code>1000</employee_Code>
 <employee_Id>1000</employee_Id>
 <employee_Status>ACTIVE</employee_Status>
 <first_Name>A</first_Name>
 <last_Name>B</last_Name>
 <location>ABC</location>
 <position>123</position>
 </ns1:e>
</m:setEmployee>
If I copy that payload (without <?xml version="1.0" encoding="UTF-8"?>) into SOAPUI (surrounded by SOAP envelope), the WS call works without any problem.
Why doesn't it work from PI?
Another question:
Why is it putting <ns1:e> into the payload of the new interface and <ns0:e> for the existing interface (which is working, see Re: PI 7.11: Adapter Framework caught exception: null)?
Could that be the reason why data is not sent properly to the SOAP receiver?

Problem with Adapter Framework

Hello All,
Our env. is XI 3.0 and for our development system all the interfaces which are connecting to R3service are getting failed .
And the audit log for one of the interface is shows
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..
MP: exception caught with cause com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback.
Can any one help me out to resolve this issue..
Best Regards
Raki

Hello Barry,
Thanks for the update.
The issue has been resolved by applying two more patches of SPS19.
Problem Resolution:
When we apply only one patch Adapter Frame Work Core (SAPXIAFC19P_19-20000272.SCA (Adapter Framework Core 19)), there is chance for some sort of inconsistences in the system and the interfaces relating to Adapter Frame work gets failed from reciever end(R3services).
To avoid such problems (inconsistences) we need to apply the patches which are related to that.And those are .
SAPXIAF19P_9-20000273.SCA Adapter Framework for SP19.
SAPXITOOL19P_10-20000274.SCA) Cumulative Patch tool for SP19
Thanks for all helping me out to resolve the problem earliest.
Best Regards
Raki

Error on Adapter Framework with Seeburger component

Hi,
I have the Generic EDI component from Seeburger Adapter, and I have a communication channel using the FTP Adapter from Seeburger with the module localejbs/Seeburger/solution/generic-edi, and when execute the communication channel, I have an error with the solution, the error is:
"Exception caught by adapter framework: Path to object does not exist at solution, the whole lookup name is localejbs/Seeburger/solution/generic-edi.".
I see the Seeburger documentation about installation and configuration from FTP Adapter, but I don´t find information about this error, somebody help me please with information about this error, what configuration I need review or where find documentation about this problem?.
We post a note about this problem on the OSS, the content of the note is:
We have installed the Seeburger's FTP adapter in SAP XI.
A communication Channel is calling this adapter nd executing a module called localejbs/Seeburger/solution/generic-edi. When the adapter is called the next error is shown;
Exception caught by adapter framework: Path to object does not exist at
solution, the whole lookup name is localejbs/Seeburger/solution/generic-edi.
Delivery of the message to the application using connection
FTP_http://seeburger.com/xi failed, due to:
com.sap.aii.af.ra.ms.api.RecoverableException: Path to object does not
exist at solution, the whole lookup name is
localejbs/Seeburger/solution/generic-edi.:
com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at solution, the whole lookup name is
localejbs/Seeburger/solution/generic-edi..
Also, the host-ftp solution was used instead of the generic-edi with the same result.
The system we have is SAP PI 7.0 SPS09 with Seeburger 1.6.
Thanks and greetings,
Hervey.

Hi,
I have the same problem. What was the solution?
Regards
Kristian

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

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!

Adapter Framework caught exception - 401

Hi,
I am trying to use NTLM authentication using Axis adapter in PI 7.1 SP7 but getting 401 error.
Axis adapter works for Basic auth.
SAP Note 856597 talks about giving PI user security role xi_adapter_soap_message. Haven't found the equivalent navigation of visual admin in NWA.
Details from message monitoring
Information Axis: getting handler trp of java:com.sap.aii.adapter.axis.ra.transport.http.HTTPSender
Error Axis: error in invocation: (401)Unauthorized
Error Adapter Framework caught exception: (401)Unauthorized
Error Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: (401)Unauthorized.
Any help is appreciated.
Thanks
Kiran Gollapudi

Hi guys,
Even the message being old, there are some of you that may want a hint on how to solve this problem.
First of all, please refer to the generic description of the error that may help one of you:
401 Unauthorized
Description: The request requires user authentication
Possible Tips:
u2022 Check XIAPPLUSER is having this Role -SAP_XI_APPL_SERV_USER
u2022 If the error is in XI Adapter, then your port entry should J2EE port 5<System no>
u2022 If the error is in Adapter Engine
u2013then have a look into SAP note- 821026, Delete the Adapter Engine cache in transaction SXI_CACHE Goto --> Cache.
u2022 May be wrong password for user XIISUSER
u2022 May be wrong password for user XIAFUSER
u2013 for this Check the Exchange Profile and transaction SU01, try to reset the password -Restart the J2EE Engine to activate changes in the Exchange Profile After doing this, you can restart the message
Alternatively, ensure you maintain the correct password for all the service users according to one of the notes
below, taking into account your system version:
PI 7.1:
#999962 - PI 7.10: Change passwords of PI service users
XI 7.0
#936093 - XI 7.0: Changing the passwords of XI service users
XI 3.0
#721548 - XI 3.0: Changing the passwords of the XI service users
Hope I could helped.
Regards,
Caio Cagnani

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.

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.

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.

Adapter Framework unable to create outbound JCA connection

Hi All,
I have a requirement in which I have to send a request from Siebel to SAP & get a response from it.
I have deployed my process on Oracle AS BPEL console.
When I try to initiate my deployed process I get below mentioned error.
<summary>
http://127.0.0.1:8888/orainfra/wsil/adapters/applications/GetDetail_invoke.wsdl?wsdl [ GetDetailPortType::GetDetail(input_GetDetail,output_GetDetail) ] - WSIF JCA Execute of operation 'GetDetail' failed due to: Adapter Framework unable to create outbound JCA connection.
http://127.0.0.1:8888/orainfra/wsil/adapters/applications/GetDetail_invoke.wsdl?wsdl [ GetDetailPortType::GetDetail(input_GetDetail,output_GetDetail) ] - : The Adapter Framework was unable to establish an outbound JCA connection due to the following issue: javax.resource.spi.EISSystemException: IWAFManagedConnectionFactory:Exception javax.resource.ResourceException: Problem activating adapter. (JCO.classInitialize(): Could not load middleware layer 'com.sap.mw.jco.rfc.MiddlewareRFC'
JCO.nativeInit(): Could not initialize dynamic link library sapjcorfc [no sapjcorfc in java.library.path]. java.library.path [D:\product\10.1.3.1\OracleAS_1\jdk\bin;.;C:\WINDOWS\system32;C:\WINDOWS;D:\product\10.1.3.1\OracleAS_1\opmn\bin;D:\product\10.1.3.1\OracleAS_1\opmn\lib;D:\product\10.1.3.1\OracleAS_1\bin;C:\WINDOWS;C:\WINDOWS\system32]). Check logs for more information
; nested exception is:
ORABPEL-12511
Adapter Framework unable to create outbound JCA connection.
http://127.0.0.1:8888/orainfra/wsil/adapters/applications/GetDetail_invoke.wsdl?wsdl [ GetDetailPortType::GetDetail(input_GetDetail,output_GetDetail) ] - : The Adapter Framework was unable to establish an outbound JCA connection due to the following issue: javax.resource.spi.EISSystemException: IWAFManagedConnectionFactory:Exception javax.resource.ResourceException: Problem activating adapter. (JCO.classInitialize(): Could not load middleware layer 'com.sap.mw.jco.rfc.MiddlewareRFC'
JCO.nativeInit(): Could not initialize dynamic link library sapjcorfc [no sapjcorfc in java.library.path]. java.library.path [D:\product\10.1.3.1\OracleAS_1\jdk\bin;.;C:\WINDOWS\system32;C:\WINDOWS;D:\product\10.1.3.1\OracleAS_1\opmn\bin;D:\product\10.1.3.1\OracleAS_1\opmn\lib;D:\product\10.1.3.1\OracleAS_1\bin;C:\WINDOWS;C:\WINDOWS\system32]). Check logs for more information
Please examine the log file for any reasons. Enable DEBUG logging in the BPEL Console.
</summary>
I have installed Oracle Adapter 10.1.3.1 on Oracle SOA Suite 10.1.3.1 & then upgraded my SOA Suite to 10.1.3.3.
Its a very critical issue.
Please help me out of it.
Thanks & Regards,
Shanty

I have resolved this error.
If you are facing the same error then follow the following steps:
1. Shutdown the Oracle SOA Suite.
2. Copy sapjcorfc.dll into C:\WINDOWS\system32
3.Edit oc4j-ra.xml located at below locations
a. OracleHome\j2ee\home\application-deployments\default\jca-app-adapter
b. OracleHome\j2ee\home\connectors\jca-app-adapter\jca-app-adapter\META-INF
by editing the values
<config-property name="AdapterName" value="SAP"/>
<config-property name="Config" value="SAP_Target_You_Have_Created_in_iaexplorer"/>
Cheers,
Shanty

Adapter Framework Problem

Hi all,
I currently have a problem with the adapter framework (AF) of the exchange
infrastructure. After having configured a scenario including an inbound and an
outbound SOAP adapter I'm not able to send SOAP messages to XI via the AF. The
AF seems to be not running as i always get an internal server error when
sending a SOAP message.
When I view the AF in the component monitoring area of the runtime workbench
I see that the self-test of the AF fails. I the detailed list of the self-test
the test for the existence of a user fails. However the user "XIAFUSER" that is
set in the configuration of the AF exists on the Web AS.
Does anyone of you have an idea why the AF self-test fails and why the AF seems
to be not running?
Thanks for you help
Christian

Hi Bill,
I tried to logon to ABAP with XIAFUSER. Everything works fine. I haven't tried any other scenario yet.
What I just noticed is, that when I view the list of services running on the J2EE engine is see the following list:
SAP XI Adapter: BC
SAP XI Adapter: File
SAP XI Adapter: JDBC
SAP XI Adapter: JMS
SAP XI Adapter: Mail
SAP XI Adapter: Marketplace
SAP XI Adapter: RFC
SAP XI Adapter: XI
There is no SOAP adapter listed. Maybe this is the reason for the problems I experience...
Christian

Messages from Adapter framework to IS disappear

During processing of interfaces, it happens some times that the sending of messages from Adapter Framework to Integration Server is broken but no status message is traced. Before this break, the messages state is correctly visible on integration server (SXMB_MONI), after that, messages are no more contained in persistence layer of the adapter framework or of the integration server. So its very difficult to know which messages have been processed, and for this reason there is a great effort for application/functional team to reprocess interfaces file.
After the last succesfully processed message, there are a lot of log messages on application and default trace of this type:
for location com.sap.aii.adapter.file.File2XI.processFileList():
Module Exception 'com.sap.aii.af.mp.module.ModuleException: senderChannel 'd902100e953f3e15b0e04b3caf9dc415': Catching exception calling messaging system' found, cause: com.sap.aii.af.ra.ms.api.ConfigException: Some of the IS access information is not available. SLDAcess property may be set to true, but SLD is not available.
Channel CC_File_OUT02_1058: Sending file failed with com.sap.aii.af.ra.ms.api.ConfigException: Some of the IS access information is not available. SLDAcess property may be set to true, but SLD is not available. - continue processing
Delivery Exception for guid'87b54890-ae37-11da-c751-001125a5fff4' - non recoverable error, retry anyway
For location com.sap.aii.adapter.file.File2XI.addAuditLog( ... ssageKey, AuditLogStatus, String, String,Object[]):
FILE_ERR_211
This behavior is independent of interface type and happens randomly (about 2-3 times a week).
We try, without success, to implement a workaround setting SLDaccess parameter to false for AF CPA cache service and specifying the xiadapter.isconfig.<parameters> for adapter service. With this configuration File Adapter didnt work and CPA cache didnt contain any comunicaton channels. Maybe we have to set the correct value of parameter directoryURL (which it is?).
Thank a lot in advance
Danilo Vaccarella

Thank you for your suggestion, but nothing seems to be wrong in configuration (however I'm contuining my checks). In the meantime, are there other suggestions?
Hi
Danilo

Adapter Framework Archiving Failed

Similar Messages

Maybe you are looking for