Call Adapter failing in SXI_MONITOR

Hi Everyone,
We have a scenario = SAP HR ---> XI ---> Legacy systems designed.
proxies are used to send message from SAP HR and JDBC adapter is used in recevier side to update sql database.
And working in live but suddenly it failed and got below two errors.
1) <SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>
<SAP:P1>401</SAP:P1>
<SAP:P2>Unauthorized</SAP:P2>
<SAP:Stack>HTTP response contains status code 401 with the description Unauthorized Error while sending by HTTP (error code: 401, error text: Unauthorized)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
2) <SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">CLIENT_RECEIVE_FAILED</SAP:Code>
<SAP:P1>110</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error while receiving by HTTP (error code: 110, error text: )</
Its failling in Call Adapter after receiver grouping in SXI_MONITOR.
I have checked HTTP sevrvice in SMICM and its running fine.
I tried my best to search a fault but could'nt. Please suggest what will be possible cause of error !!!
Thanks IN advance
Swapnil
Message was edited by:
Swapnil Bhalerao

Hi Shabarish,
Same issue as Swapnil. We checked SU01. XIAPPLUSER has role "SAP_XI_APPL_SERV_USER" assigned.
As stated, the scenarios were working fine till day before yesterday. So, I suppose, the kernel patches and all are up-to-date. We started receiving these errors since yesterday.
Kindly advice.

Similar Messages

Xi 3.0: Mail adapter fails with "exception in method process"

Hi.
I configured the dynamic address for mail adapter following the fantastic-as-always weblog from michalgh.
Althou everything seems to work fine (that is, i send correctly the email message) the A.F. returns an error with "exception in method process".
I tried both async and sync case with the same result. In the sync case, the response contains:

<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="PARSING">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: Exception in method process.</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Any idea???

Yes. There is also a response message in the imported structure.. it seems it should work as a kind of application ack with some info on the server that processed the mail.
Anyway, in my server i get a 404 for the link you suggested.
In the async case i don't get any error on the SXMB_MONI but only on the A.F.
I attach the audit log for the async case:
Audit Log for Message: ffb28585-3c53-0f4b-b366-7dd7a00513fc
Time Stamp Status Thread ID Sequence No. Description
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_45 1118608026046 The message was successfully received by the messaging system. Profile: XI URL: http://CAPELAB010:50000/MessagingSystem/receive/AFW/XI
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_45 1118608026062 Using connection AFW. Trying to put the message into the receive queue.
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026093 The message was successfully retrieved from the receive queue.
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026375 The message status set to DLNG.
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026468 Delivering to channel: MAIL_RECV
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026468 Mail: message entering the adapter
2005-06-12 22:27:06 Error SAPEngine_Application_Thread[impl:3]_34 1118608026828 Exception caught by adapter framework: Failed to call the endpoint
2005-06-12 22:27:06 Error SAPEngine_Application_Thread[impl:3]_34 1118608026828 Delivery of the message to the application using connection AFW failed, due to: Failed to call the endpoint.
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026843 The asynchronous message was successfully scheduled to be delivered at Sun Jun 12 22:32:06 CEST 2005.
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026859 The message status set to WAIT.
2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327109 The message was successfully retrieved from the receive queue.
2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327125 The message status set to DLNG.
2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327156 Delivering to channel: MAIL_RECV
2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327171 Mail: message entering the adapter
2005-06-12 22:32:07 Error SAPEngine_Application_Thread[impl:3]_34 1118608327250 Exception caught by adapter framework: Failed to call the endpoint
2005-06-12 22:32:07 Error SAPEngine_Application_Thread[impl:3]_34 1118608327250 Delivery of the message to the application using connection AFW failed, due to: Failed to call the endpoint .
2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327281 The asynchronous message was successfully scheduled to be delivered at Sun Jun 12 22:37:07 CEST 2005.
2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327296 The message status set to WAIT.
2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627421 The message was successfully retrieved from the receive queue.
2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627437 The message status set to DLNG.
2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627546 Delivering to channel: MAIL_RECV
2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627562 Mail: message entering the adapter
2005-06-12 22:37:07 Error SAPEngine_Application_Thread[impl:3]_34 1118608627671 Exception caught by adapter framework: Failed to call the endpoint
2005-06-12 22:37:07 Error SAPEngine_Application_Thread[impl:3]_34 1118608627671 Delivery of the message to the application using connection AFW failed, due to: Failed to call the endpoint .
2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627703 The asynchronous message was successfully scheduled to be delivered at Sun Jun 12 22:42:07 CEST 2005.
2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627734 The message status set to WAIT.
2005-06-12 22:42:07 Success SAPEngine_Application_Thread[impl:3]_40 1118608927734 The message was successfully retrieved from the receive queue.
2005-06-12 22:42:07 Success SAPEngine_Application_Thread[impl:3]_40 1118608927734 The message status set to DLNG.
2005-06-12 22:42:07 Success SAPEngine_Application_Thread[impl:3]_40 1118608927750 Delivering to channel: MAIL_RECV
2005-06-12 22:42:07 Success SAPEngine_Application_Thread[impl:3]_40 1118608927750 Mail: message entering the adapter
2005-06-12 22:42:07 Error SAPEngine_Application_Thread[impl:3]_40 1118608927765 Exception caught by adapter framework: Failed to call the endpoint
2005-06-12 22:42:07 Error SAPEngine_Application_Thread[impl:3]_40 1118608927781 Delivery of the message to the application using connection AFW failed, due to: Failed to call the endpoint .
2005-06-12 22:42:07 Error SAPEngine_Application_Thread[impl:3]_40 1118608927796 The message status set to NDLV.
Total: 33 Entries 1020304050 messages displayed per page; this is page 1 of 1 page(s)

Error in Call Adapter

Hello,
We have RFC --> HTTPS scenario.
The RFC Destination of type G is created in XI and the connection test is working fine.
When I run this scenario, sometimes I get following error:
com.sap.aii.af.ra.ms.api.DeliveryException: XIAdapter:ATTRIBUTE_CLIENT:.
Error in sxmb_moni in Call Adapter Step:
SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_CLIENT</SAP:Code>
<SAP:P1>110</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP client code 110 reason</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
However sometimes it works fine.
Please help to resolve this.
Thanks in advance,
Beena.

Thanks Swarup.
The HTTPS connection is used from XI to third party. XI is not receiving HTTPS request.
Still do I need to enable HTTPS on web dispatcher?
The runtime workbench has following error:
Received XI System Error. ErrorCode: ATTRIBUTE_CLIENT ErrorText: ErrorStack: HTTP client code 110 reason
Transmitting the message using connection http://<dispatcher host>:<http port>/sap/xi/engine?type=entry failed, due to: com.sap.aii.af.ra.ms.api.DeliveryException: XIAdapter:ATTRIBUTE_CLIENT:.
Thanks,
Beena.

Call Adapter Error - 401 Unauthorized

Hi,
We are using Multi Mapping where it splits 1 message into n messages. The n messages split by this scenario in trun calls another scenario configured in the same PI server using SOAP Adapter.
The called scenario is SOAP --> Siebel using iWay Adapter.
When the number of messages split are huge in order of thousands, the server is going for a toss and the called scenaio is failing at Call Adapter Step in IE with HTTP Error 401 Unauthorized. Few of the messages manage to pass successfully.
Anticipating your valuable inputs.
Thanks.
Regards,
Sudharshan N A

Hi Sudharshan,
There can be different reasons for getting HTTP 401: Unauthorized error. As you said, few of the messages are being passed to the called application, I would request you to check the scalability of the Seibel Server.
Also if you are using a connections from a connection pool, then it may be that the pool itself is getting exhausted, though mostly we get Socket exception/Connection Exception/IO Errors in these cases.
The other reasons can be that the user you are using to connect Seibel dont have enough permissions. But it is ruled out as you said some messages have been processed.
If the Seibel server is SSL enabled, and your PI doesn't have any certificate configured, then also you may get such errors.
Regards,
Sugata

Two "Call Adapter" step in SXMB_MONI

Hello Experts,
I have developed Sync interface WebService - PI - BAPI.
However when message is failing due to error in mapping at response side, there are 2 "Call Adapter" steps in sxmb_moni got that message.
First Call Adapter step is not in error status, however 2nd Call Adapter is in Error status (System Error- Restart not possible).
Could you please explain me why there are 2 "Call Adapter" steps? Actually there has to be only one step.
Best Regards,
Manisha

First Call Adapter step, there is no error
but in 2nd call adapter error is
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_MM_Z_BAPI_VL10_DLVY_CREATE_resp_2_~</SAP:P1>
<SAP:P2>com.sap.aii.mappingtool.tf7.IllegalInstanceExcepti</SAP:P2>
<SAP:P3>on: Cannot create target element /ns1:Order/OrderD</SAP:P3>
<SAP:P4>etail/ListOfItemDetail/ItemDetail. Values missing~</SAP:P4>
<SAP:AdditionalText />
<SAP:Stack>Runtime exception occurred during application mapping com/sap/xi/tf/_MM_Z_BAPI_VL10_DLVY_CREATE_resp_2_; com.sap.aii.mappingtool.tf7.IllegalInstanceException: Cannot create target element /ns1:Order/OrderDetail/ListOfItemDetail/ItemDetail. Values missing</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
both call adapter steps are under "Central client" step. why 2 call adapter in one?

Error at Call Adapter stage

Hi.
We are experiencing an error at the 'Call Adapter' stage of the pipeline. It seems as if the message is unable to move from the integration engine to the adapter engine with this error -
<?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="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">CLIENT_SEND_FAILED</SAP:Code>
<SAP:P1>500</SAP:P1>
<SAP:P2>Internal Server Error</SAP:P2>
<SAP:P3>(See attachment HTMLError for details)</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error while sending by HTTP (error code: 500, error text: Internal Server Error) (See attachment HTMLError for details)</SAP:Stack>
<SAP:Retry>A</SAP:Retry>
</SAP:Error>
The HTML dump says u2013
java.lang.NullPointerException:
 at com.sap.engine.interfaces.messaging.spi.transport.TransportHeaders.setHeader(TransportHeaders.java:169)
 at com.sap.aii.adapter.xi.ms.XIMessage.prepareToReceive(XIMessage.java:1437)
 at com.sap.aii.adapter.xi.ms.XIMessage.prepareToReceive(XIMessage.java:1122)
 at com.sap.aii.adapter.xi.ms.XIEventHandler.onRequest(XIEventHandler.java:791)
 at com.sap.engine.messaging.impl.spi.ServerConnectionImpl.request(ServerConnectionImpl.java:237)
 at com.sap.engine.messaging.impl.core.transport.http.MessagingServlet.doPost(MessagingServlet.java:417)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
 at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:163)
 at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:82)
 at com.sap.engine.services.servlets_jsp.server.servlet.AuthenticationFilter.doFilter(AuthenticationFilter.java:124)
 at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:74)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:425)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:289)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:376)
 at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:160)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)
 at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
 at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
 at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
 at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:309)
 at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:222)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:152)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)
This occurred after an SLD update. Does anyone know how to fix this issue?
Thanks
Regards
Riaz

Hi guys
1. Sender - Backend ERP (ECC) calling enterprise service, Receiver - SOAP Web service. Both are business systems internal to the network
2. Both sender and receiver are Business systems which are registered in the SLD.
3. This interface was previously working, until the LSD was updated, then it began.
4. PI 7.10
5. All the scenarios which use this type of communication (Proxy to SOAP) are failing at the same stage
I have also logged an OSS call with SAP and they are currently looking at the issue.
Regards
Riaz

No Payload in the soap receiver call adapter ?

Hi Guys,
configured Proxy-SOAP Asynchronus process and in the sxmb_moni, i am unable to see the payload under call adapter in sxmb_moni, but i am able to see the payload under RWB in MDT. The message is checked successful in monitor.
I am not understanding why i am unable to see the payload under call adapter in sxmb_moni. I am not getting the data into my receiver system.
Do i need to mention the QOS as EO in the soap url in the soap receiver adapter configuration ?
any help would be really appreciated
Thanks,
srini

Hi,
You can only see the Payload(both with and without transformation) in MONI. message that is handling by adapter can only seen in Adapter Framework using RWB-Message Monitoring or using Communication Channel Monitoring.
Regards,
Farooq.

Rewards points if you find it usefull.

The Cluster Service function call 'ClusterResourceControl' failed with error code '1008(An attempt was made to reference a token that does not exist.)' while verifying the file path. Verify that your failover cluster is configured properly.

I am experiencing this error with one of our cluster environment. Can anyone help me in this issue.
The Cluster Service function call 'ClusterResourceControl' failed with error code '1008(An attempt was made to reference a token that does not exist.)' while verifying the file path. Verify that your failover cluster is configured properly.
Thanks,
Venu S.
Venugopal S ----------------------------------------------------------- Please click the Mark as Answer button if a post solves your problem!

Hi Venu S,
Based on my research, you might encounter a known issue, please try the hotfix in this KB:
http://support.microsoft.com/kb/928385
Meanwhile since there is less information about this issue, before further investigation, please provide us the following information:
The version of Windows Server you are using
The result of SELECT @@VERSION
The scenario when you get this error
If anything is unclear, please let me know.
Regards,
Tom Li

HP Officejet Pro 8500A Plus AC Power adapter failed. Where to buy?

My AC power adapter failed. Where can I purchase a new one in Doha?

There should be an electronics store near there. Go into google maps, bring up Doha, then search nearby and put in 'hp printers' which should be up some sort of electronics retailer.
If that doesn't work, then go to HP.com, put in your printer model, and follow the links, and you should be able to order one online. Just make sure you specify your region in your search, so that it doesn't think you are in Ireland, when you are actually in Qatar.
007OHMSS
I was a support engineer for HP.
If the advice resolved the situation, please mark it as a solution. Thank you.

File-IDoc scnario : Error in call adapter

Hi Experts,
I have developed File to IDoc scenario. And getting the following error in "Call Adapter" pipeline step. I have mapped the control record values in IDoc like Sender Partner, no, port and same for receiver.
Have created:
In XI: RFC destination to connect to ECC (sm59)
Port for the above RFC sestination (idx1)
In ECC: New logical system for source file system (BD54)
Partner Profile for Source (we20)
Also in Receiver_IDoc_CC, checked options for 1. Apply control record values from payload 2. Take Sender and Receiver from Payload
<?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="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
<SAP:P1>Transaction IDX1: Port SAPEAQ_100, client , RFC destination contain errors</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: Transaction IDX1: Port SAPEAQ_100, client , RFC destination contain errors</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Please tell me if i am doing any mistake.
Br,
Nilz

Hi,
Adding to Björn
Check the Port ( Tcode - idx1 ) Port SAPEAQ_100 & Select the Business System where you declared IDOC adapter -go to - Service and check whether you have mentioned the right Logic System,System ID & Client.
Cheers
Agasthuri Doss

Error in Call Adapter (IDOC- XI- FILE)

Hello,
i have got the following error message in the integration engine monitoring in the "call adapter" part:
td {font-family : Arial, Tahoma, Helvetica, sans-serif; font-size : 14px;} A:link A:visited A:active HTTP response contains status code 503 with the description Service Unavailable XML element Envelope missing in SOAP message header (SAP XI Extension)
What is the AFW application?????

Hi Christian,
Have a look at the following thread, it might be useful
XI Server Malfunction:Error in Receiver Adapter
Regards
Suraj

Error in Call Adapter step

Hello,
We have RFC --> HTTPS scenario.
The RFC Destination of type G is created in XI and the connection test is working fine.
When I run this scenario, sometimes I get following error:
com.sap.aii.af.ra.ms.api.DeliveryException: XIAdapter:ATTRIBUTE_CLIENT:.
Error in sxmb_moni in Call Adapter Step:
<?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>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_CLIENT</SAP:Code>
<SAP:P1>400</SAP:P1>
<SAP:P2>ICM_HTTP_CONNECTION_FAILED</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP client code 400 reason ICM_HTTP_CONNECTION_FAILED</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
However sometimes it works fine.
Please help to resolve this.
Thanks in advance,
Hetal

Hello Hetal,
Can you please elaborate more on the scenario. if it is a RFC -> PI -> SOAP scenario please check if you are using the correct target URL in your Receiver Comm. Channel. Also check if the backend service could be unstable due to network load.
Thanks.
Kiran

No Payload in sxmb_moni call adapter

I did soap to soap asynchronous scenario....
my requirement is to send one systems soap request as it is to other systems soap response...
i.e., sending soap message asynchronously...
its often saying that queue is stopped... i am deleting that queue and manually checking for message tracing.....
upto technical routing my payload is there, there is no payload in call adapter...
i checked in adapter monitoring, message monitoring and sxi_cache.. there is no error atall...
Please guide me in resolving this problem...
Regrads,
Pushparaju.B

Hi,
my requirement is to send one systems soap request as it is to other systems soap response...
Your reqirement is not very clear. Could you please elaborate?
Is it that you want to send a soap request, and donot expect any response back?
Have you called an mapping in your interface determination?
If so, maybe the mapping is not successful and hence you are not able to see the message after technical routing.
I suggest that you check the mapping in the repository, with the payload that you are using as the request.
Regards,
Smitha.

Error in SXMB_MONI in SOAP Header -- Call Adapter

Hi ALL,
Got a problem with monitoring activity.
In SXMB_MONI, iam getting errors with Call Adapter section in SOAP HEADER section of the message.
The Error part shows the following error:
<?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: Problem inserting 4657f861-f853-60e8-e100-00000a80314d(INBOUND) into the database: java.sql.SQLException: ORA-25153: Temporary Tablespace is Empty</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Can anybody give me a clear picture of the exact error and what could be the diagnosis for this particular problem.
cheers,
Santosh

Hi Santhosh
1.Check your authorization settings in XI and R/3. Whether the user has sufficient rights to execute the Function Module etc. This is the most common reason for this error.
2.If the XI system was brought online even before the R/3 system then re-activate the communication channels from the Integration directory.
Cheers..
Vasu
** Reward Points if found useful **

First call attempt fails with 12000; reason="Routes available for this request but no available gateway at this point"

We've installed a new Audiocodes Mediant 1000B gateway for our customer. They only have about 6 users enabled for Enterprise voice and using Lync for all calls. They have an intermittent problem whereby the first call attempt to a number on the
PSTN fails with 12000; reason="Routes available for this request but no available gateway at this point". There is only one PSTN gateway installed. All routes point to this gateway. What I found initially is that the calls
were failing after 10 seconds which is the default "failovertimeout" in the OutboundRouting.exe.config. I found this post http://voipnorm.blogspot.co.uk/2012/06/lync-2010-gateway-timeout-call-failures.html and
changed the value to 20 seconds. Subsequent failures failed after 20 seconds (the new value). The interesting thing is that the second attempt even a couple of seconds later succeeds. My Lync server event log has 46046 "A call to a PSTN
number failed due to non availability of gateways." for the failed call and 46047 "A PBX gateway is now responding to requests after some failures." for the successful call moments later.
My environment is Lync 2010. A single enterprise edition Front End with collocated mediation. The server is virtual and in a different physical location to the gateway. The two sites are connected via a LES1000. The RTT between the
sites is very low so it isn't necessarily networking.
In the Syslog output on the Audiocodes we don't see the call even reach the gateway. It's likely that Lync has simply marked the gateway as down and doesn't route the first call. Then it wakes up and marks it as up and routes the next call.
Update wise I'm on 4.0.7577.183, 199 and 217 for those that are up to date and the only components that are behind say that 223 is available. Those being Core Components, Lync Server, Conferencing Server and Web Components.
As I said, this is intermittent, apparently doesn't happen for every user (which I don't buy), but is easily replicated on request.
I definitely think changing the failovertimeout value has reduced the number of failures. But realistically I don't want users sitting there for 20 seconds before their call fails. Or 19 seconds for the call to route.
I've found a few posts on this and similar issues. I don't get the 25051 or 25052 errors.
Any help gratefully appreciated.
Regards
Randy Chapman
Best Regards Randy Chapman

Try to change the value of Failovertimeout to 1000.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Call Adapter failing in SXI_MONITOR

Similar Messages

Maybe you are looking for