XI - XIServer:ID_SA_MAX_CALLS_EXCEEDED problem

Dear all,
I implement a scenario that it will pass the message from the file adapter to SAP R/3 with BPM.
But the large volume messages cause that the sync. call exceeded the limitaion.
Would I have some solution to handle this problem? Thanks for your kindly help!!!
Red

ID_SA_MAX_CALLS_EXCEEDED
But the large volume messages cause that the sync. call exceeded the limitaion.
Check this note...the problem is mentioned and probable solution is provided:
https://service.sap.com/sap/support/notes/1353343
Regards,
Abhishek.

Similar Messages

Sender Adapter Mail Problem

Hello All,
on PI 7.0, i have a scenario MAIL -> PI -> MAIL.
I've configured the sender mail adapter in order to keep attachment and using pop protocol.
When i test, the problem is that everything is green in the CC monitoring but it doesn't take any mail from the mailbox server, still in it. i see 0 mail taken in the CC monitoring.
Since i don't have error messages i don't know how and where to look at ! Do you have some ideas ?
For infos, i've based my configuration with the help of this blog :
/people/michal.krawczyk2/blog/2005/12/18/xi-sender-mail-adapter--payloadswapbean--step-by-step
EDIT : For further more informations, i am using a Lotus server for the mail.
Thanks,
Jean-Philippe
Edited by: Jean-Philippe PAIN on Jan 14, 2010 6:08 PM

Hi Jean,
Have you tried to open the link *http://xiserver:port/mdt/amtServlet
as suggested by Michal? What is the status there? There you can see whether the mail has been received by your mail adapter or not. If not, then check with your POP server and ports again. Look whether you have the POP port opened bi-directionally for your PI server.
Regards,
Sugata

SOAP Receiver Adapter problem (client certificate required)

My Scenario is similar to described in https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/3721. [original link is broken] [original link is broken] [original link is broken] I have two PI servers running on one machine. I am trying to post message HTTPS with Client authentication via SOAP adapter from one PI system to SOAP adapter of other PI server. I have done the following configuration.
PI Server AXD - (Client) - Receiver SOAP adapter
PI Server AXQ - (Server) - Sender SOAP Adapter.
Steps in AXD
1. I have created a certificate of AXD in the service_ssl view of key storage.
2. I have imported the AXQ public certificate in to AXD in the TrustedCAs of Key storage
Steps in AXQ
1. I have created a certificate of AXQ in the service_ssl view of key storage.
2. I have imported the AXD public certificate in to AXQ in the TrustedCAs of Key storage.
3. I have created a user in AXQ and assigned the certificate of AXD under usermangement in Security provider to this user.
4. I have added the AXD certificate under Client Authentication tab with require client certificate option checked in the SSL Provider.
5. I have assigned the user created in AXQ in the step above to the Sender Agreement.
Now when I post message from AXD with Configure Client Authentication checked (Here I have selected the certificate of AXD and view as service_ssl) I am getting the following error.
Exception caught by adapter framework: SOAP: response message contains an error XIServer/UNKNOWN/ADAPTER.JAVA_EXCEPTION - java.security.AccessControlException: client certificate required at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:884) at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl0_3
Any pointer to solve this problem is highly appreciated.
Thanks
Abinash

Hi Hemant,
I have couple of questions. Why do we need to import certificate for SOAP WS-Security and from where I can get it?
As far as my scenario goes I am not using message level security.
Secondly what do you mean by TRUSTED/WebServiceSecurity? I don't see any such view inside the Key Storage. I can see a view named just WebServiceSecuity though.
Also I don't have a decentralized adapter installation rather I have two separate PI instances having their own central adapter engine.
Abinash

Webservice to file (receiver determination problem)

Hi ...
I am doing webserive to file scenario in PI7.0 server. I have completed doing the scenario. But there is a problem in receiver side. In SXMB_MONI it is showing the below 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>XIServer</SAP:Category>
<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_BE</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Could you please help me out in this.

hi,
When you have used the WSDL wizard in the Integration Directory and have clicked on "Propose URL" in the second screen, did you ever wonder, why the URL does not point to a sender SOAP adapter channel, it is the URL of the Integration Server instead?
When you want to use the inbound channel of the Integration Server, you have to use following URL for the web service client:
http://<server>:<ABAP-port>/sap/xi/engine?type=entry&version=3.0&Sender.Service=<YourService>&Interface=<YourNamespace>%5E<YourInterface>
The namespace must be written with escaped characters. (%5E stands for "^")
Note: The WSDL wizard creates an address with the escape sequence & instead of &. Some SOAP clients (for example XPLSpy) do not automatically restore the character and you have to do this manually.
By default the SOAP call is treated as a synchronous call. If you want an asynchronous call, you have to add &QualityOfService=ExactlyOnce to the URL.
Additionally your web service client must provide the HTTP header parameter "SOAP action" = http://sap.com/xi/WebService/soap1.1
The Web Service Wizard of the Integration Repository creates a WSDL concerning this URL and this SOAP action automatically. Only for asynchronous calls you need to change the URL inside the WSDL file with an editor and add &QualityOfService=ExactlyOnce.
Advantage
When you send SOAP messages directly to the Integration Server, you reduce the message load on the adapter engine. This can improve the performance.
Restrictions
The SOAP inbound channel of the Integration Server does not support attachments. SOAP messages with content type "multipart" are rejected.
Hint
For testing purpose it is possible to add logon data directly to the URL. The parameters are the same as in the HTTP sender adapter: &sap-user=<username>&sap-password=<password>
/people/stefan.grube/blog/2006/09/21/using-the-soap-inbound-channel-of-the-integration-engine
regards
chandra

Problem in Receiver determination in case of BPM ASNElectronicLabelPost

Hi
I am working on AII flexible delivery scenario its a RFID scenario.
XI is part of this architecture.
In one BPM ASNElectronicLabelPost receiver service is selected based on <b>condition</b>.
the condition is ProcessStep=ASNtoAII based on which the concerned service needs to be selected.
   I am getting the following <b>Error</b>
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="RCVR_DETERMINATION">CX_RD_PLSRV</SAP:Code>
<SAP:P1>Problem extracting values from the message: The exception occurred (program: CL_SWF_RLS_CONDITION==========CP, include CL_SWF_RLS_CONDITION==========CM00Q, line: 161)</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error when determining the receiver: Problem extracting values from the message: The exception occurred (program: CL_SWF_RLS_CONDITION==========CP, include CL_SWF_RLS_CONDITION==========CM00Q, line: 161) Problem extracting values from the message: The exception occurred (program: CL_SWF_RLS_CONDITION==========CP, include CL_SWF_RLS_CONDITION==========CM00Q, line: 161) The exception occurred (program: CL_SWF_RLS_CONDITION==========CP, include CL_SWF_RLS_CONDITION==========CM00Q, line: 161) The exception occurred (program: CL_SWF_RLS_COMPARISON=========CP, include CL_SWF_RLS_COMPARISON=========CM002, line: 63) The exception occurred (program: SAPMSSY1, include , line: 0) The exception occurred (program: CL_SWF_EXP_EXPRESSION=========CP, include CL_SWF_EXP_EXPRESSION=========CM027, line: 50)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Please help me solve this error.
Thanks in advance.
Regards,
Amit Deshpande

Hi,
here is the coding
IF error_id CA 'EAX'.
<b>**** If a non-trivial error_map is active and an error still occurs,
this indicates a condition syntax error or a system error.</b>    CLEAR temp_result.
    LOOP AT lt_errors ASSIGNING <swa_error>.
      MOVE-CORRESPONDING <swa_error> TO t100_msg.
      CREATE OBJECT lcx_exception
        EXPORTING
          t100_msg = t100_msg
          previous = lcx_ifs.
      IF m_last_exception IS NOT BOUND.
        m_last_exception = lcx_exception.
I would check the condition. First simplify the condition and look if the error still exists.
Regards Mario

Problems in IDOC receiver communication channel

Hi,
I am trying to build an interface to get data from 3rd party legacy system using JDBC and post the data into ECC using IDOCS. I have IDOC built in ECC, I am able to import the metadata in IDX2 after creating port in IDX1. But after building the whole interface, I dont see the IDOC receiver communication channel which has to post IDOCS in the ECC 6.0 system.
Please assist.
Rgds
Kishore

OK in that case, we are getting the following error in the Message monitoring:
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="OUTBINDING">CO_TXT_OUTBINDING_ERROR</SAP:Code>
<SAP:P1>-BS_AVN_TO_FILE_JDBCSERVER</SAP:P1>
<SAP:P2>-BS_WOAV_IDOC_SENDER,urn:sap-com:document:sap:idoc:messages.ZAVENTITY01.ZENTITY</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>No standard agreement found for , BS_AVN_TO_FILE_JDBCSERVER, , BS_WOAV_IDOC_SENDER, urn:sap-com:document:sap:idoc:messages, ZAVENTITY01.ZENTITY</SAP:AdditionalText>
<SAP:Stack>Problem occurred in receiver agreement for sender -BS_AVN_TO_FILE_JDBCSERVER to receiver -BS_WOAV_IDOC_SENDER,urn:sap-com:document:sap:idoc:messages.ZAVENTITY01.ZENTITY: No standard agreement found for , BS_AVN_TO_FILE_JDBCSERVER, , BS_WOAV_IDOC_SENDER, urn:sap-com:document:sap:idoc:messages, ZAVENTITY01.ZENTITY</SAP:Stack
Please check and assist.
Rgds
Kishore

Problem in scenario JDBC - XI - File

Hi,
In my scenario, data is fetched from database and passed on to external file. In my design i have put source structure which is exactly the same as database structure and mapped it to target structure. Message interfaces for both the source and target message types are asynchronous outbound and asynchronous inbound respectively. in the communication channel for sender service, i have taken JDBC adapter as sender adapter and for reciever, file adapter.
     After activating the change list, i can see that JDBC adapter is able to connect to the database but not doing any message processing. similarly in adapter ramework monitoring, File adapter is showing "Up and running. no mesage processing until now".
     Can somebody guide me in finding the possible location of error?
     Do i need to specify the table name and action in the message mapping as in the case with outbound JDBC adapter? is the mapping adapter dependent in this case?
Best Regards,
Nitin Aggarwal.

Hi Sridhar,
Thanks for the valuable tips.. I reduced the poll interval in the sender JDBC adapter and in the adapterframework monitor, it is showing that the message processing started but again it terminated with the exception
Error: Sending message '0e4b36b0-c81c-11d9-85f8-001143eb68b9' failed with delivery exception - proceed anyway: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:MSGGUID_EXISTING:
last retry interval started 04:12:19 2005-05-19
Can you suggest where the problem is persisting?
Thanks and Regards,
Nitin.

HTTP to ABAP Proxy - Problem with "Current User" parameter

Hi experts,
We have a HTTP to ABAP proxy sceario, where I used an HTTP Destination to connect to the proxy.
We're trying to use the option "Current User" in that destination in order to login to ECC with the same user that in PI adapter plain.
The user exists i both systems, PI and ECC, with the same password.
Checking that parameter we get the following error:
<SAP:Error><SAP:Category>XIServer</SAP:Category><SAP:Code>INTERNAL.UNAUTHORIZED</SAP:Code><SAP:P1>401 </SAP:P1><SAP:P2>Unauthorized</SAP:P2><SAP:P3>(See attachment HTMLError for details)</SAP:P3></SAP:Error>
We think that PI is not getting the password.
Does aybody know how to do this?
Thanks and regards,
LUIS B.

Hi Chirumamilla,
If we put user and password in SM59 (unchecking "Current User") the commuication works without problems.
We don't want to leave a user set there, beacuse we are looking to access to PI with different users and login to ECC with the same user.
Thanks,

Problem with adapter

hello
running a sync service and recieve this error.
couldnt determine if this is XI problem or WS.
if it is XI, how can I debug it?
<?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>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">AE_DETAILS_GET_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>3: Unable to find URL for Adapter Engine af.xip.mgnt154</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error when reading the access data (URL, user, password) for the Adapter Engine</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>

Hi,
This merely problem with cache. It is saying XI engine is not able identify the adapter engine URL.
please do this.
You can view the cache data in
transaction SXI_CACHE. To do this,
select Go to &#56256;&#56518; Adapter Engine
Cache.
You can delete the cache data in
transaction SXI_CACHE. To do this,
select Go to &#56256;&#56518; Adapter Engine
Cache. Then choose the recycle bin
push button ( ).
Thanks,
Gujjeti

Problem in HTTP Request HTTP_RESP_STATUS_CODE_NOT_OK

Hai Gurus,
I am sending request from HTTP --> XI --> ABAP Proxy (Inbound). Its working fine when i execute proxy manually in tcode "sproxy". When do the same with HTTP Client it is throwing 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>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>
<SAP:P1>500</SAP:P1>
<SAP:P2>Internal Server Error</SAP:P2>
<SAP:P3 />
<SAP:P4 />
My proxy does the work of uploading the files to Document Storage System KPro using standard BAPI's. I have used SAPFTP and SAPHTTP dlls in client machine's system32 folder (Which will help in downloading the document from client windows OS machine to SAP GUI AIX based machine).
Still facing the same problem which will throw error HTTP_RESP_STATUS_CODE_NOT_OK with error code 500.
Any help is highly appreciated.
Regards,
Pushparaju Bollapalli.

Also Check these Foloowing ;
- URL for the receiver is like this:
http://<host>:<port>/sap/xi/engine?type=receiver .The XI 2.0 differs from XI 3.0 in this.
-path in the receiver communication channel
The path has to be defined as:
/sap/xi/engine?type=entry for XI 3.0
/sap/xi/engine?type=receiver for XI 2.0
Regards
Aashish Sinha
PS : Reward points if Helpful

File Adapter - Sender Problem

Hi,
While implementing a file to file interface I am facing problem in Integration Engine. Data is not passing to Integration engine, so it is not able to reach receiver.
Receiver file adapter is working fine for other scenarion like IDoc to File.
File Adapter status is Green in RWB.
I am not able to see message in SXMB_MONI
The error details in Adapter Engine is bellow
Audit Log for Message: 410424a0-c496-11da-aa48-00111120e6db
Time Stamp Status Description
2006-04-05 16:51:37 Success Channel file2file_in_channel: Send binary file "D:\usr\sap\QN7\DVEBMGS00\work\XiPattern2\testfile2in.xml". Size 209 with QoS EO
2006-04-05 16:51:37 Success Application attempting to send an XI message asynchronously using connection AFW.
2006-04-05 16:51:37 Success Trying to put the message into the send queue.
2006-04-05 16:51:37 Success Message successfully put into the queue.
2006-04-05 16:51:37 Success The application sent the message asynchronously using connection AFW. Returning to application.
2006-04-05 16:51:37 Success The message was successfully retrieved from the send queue.
2006-04-05 16:51:37 Success File "D:\usr\sap\QN7\DVEBMGS00\work\XiPattern2\testfile2in.xml" deleted after processing
2006-04-05 16:51:37 Success The message status set to DLNG.
2006-04-05 16:51:37 Error Transmitting the message to endpoint http://sapep:50000/sap/xi/engine?type=entry using connection AFW failed, due to: Received HTTP response code 404 : Not Found.
2006-04-05 16:51:37 Success The asynchronous message was successfully scheduled to be delivered at Wed Apr 05 16:56:37 GMT+05:30 2006.
2006-04-05 17:01:37 Success The message status set to WAIT.
2006-04-05 17:06:37 Success Retrying to send message. Retry: 3
2006-04-05 17:06:37 Success The message was successfully retrieved from the send queue.
2006-04-05 17:06:37 Success The message status set to DLNG.
2006-04-05 17:06:37 Error Transmitting the message to endpoint http://sapep:50000/sap/xi/engine?type=entry using connection AFW failed, due to: Received HTTP response code 404 : Not Found.
2006-04-05 17:06:37 Error The message status set to NDLV.
Please suggest the solution.
Is there any place where I can find the exact error log?
Thanks,
Smita.

Hi,
I found there was a problem with HTTP port in the URL. After fixing this, I am able to see the message in SXMB_MONI. But it is with an error. The error details is as bellow.
<?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">AE_DETAILS_GET_ERROR</SAP:Code>
<SAP:P1>af.qn7.sapep</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>no_messaging_url_found: Unable to find URL for Adapter Engine af.qn7.sapep</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error when reading the access data (URL, user, password) for the Adapter Engine af.qn7.sapep</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
In RWB->Adapter engine there is a success message, But in the RWB->Integration Engine there is an error with Error Code : AE_DETAILS_GET_ERROR.
Please suggest how to fix this. I am able to logon to XI system with user XIAFUSER.
Thanks,
Smita

XI messages problem

Hi all,
The team of infrastructure of the company made some settings in UNIX server which runs the XI for the XI that can run on cluster. The problem is they did a setting in the operating system pointing to a machine that would run on cluster with the XI.
But in the XI somehow got this setup and all messages are giving bellow error. The problem is you're trying to make a request in the HTTP server that would be used as a cluster. Does anyone have any idea of what might be happening?
SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">CLIENT_RECEIVE_FAILED</SAP:Code>
<SAP:P1>400</SAP:P1>
<SAP:P2>ICM_HTTP_CONNECTION_FAILED</SAP:P2>
table border="0"> <tr><td>Error:</td><td>-20</td></tr> <tr><td>Version:</td><td>6040</td></tr> <tr><td>Component:</td><td>ICM</td></tr> <tr><td>Date/Time:</td><td>Thu Oct 16 12:51:51 2008 </td></tr> <tr><td>Module:</td><td>icxxconn_mt.c</td></tr> <tr><td>Line:</td><td>2124</td></tr> <tr><td>Server:</td><td>briieai1_XIP_00</td></tr> <tr><td>Detail:</td><td>Connection request from (46/324/0) to host: briieai2_svc, service: 50300 failed (NIECONN_REFUSED) AP-T46, U324, 020 WF-BATCH, ES90F023J, 12:51:51, M0, W0, , 1/0</td></tr> </table> <p></p> </td></tr></table> <table><tr><td width=50 nowrap></td> <td nowrap><FONT SIZE=-1><a href="http://www.sap.com/">© 2001-2005, SAP AG</a></FONT></td></tr></table></SAP:AdditionalText>
the XI server is briieai1, but the XI has request the HTTP in another host ( briieai2_svc )....
any idea?
tks.

Hi
Check are you able to reach host: briieai2_svc, service: 50300
Ping it
Please go to SMICM and check wether the status is green.
Check Notes
755372,
710735
Thanks
Gaurav

File to file scenario problems

Hi all,
not so far ago I install XI and it was seems to me that I did all post installation steps.
But when I try to do <a href="https://wiki.sdn.sap.com/wiki/display/XI/FLAT%20FILE%20TO%20FLAT%20FILE">File to File scenario</a>, I receive error in audit log:
SOAPFault received from Integration Server. ErrorCode/Category: XIServer/IN_BIND_WRONG_ADPT; Params: File; AdditionalText: ; ApplicationFaultMessage: ; ErrorStack: Sender agreement found belongs to adapter File; however, current adapter is 'XI'
Transmitting the message to endpoint http://<xiserver>:8001/sap/xi/engine?type=entry using connection AFW failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 500 : Error during conversion of XI message.
(<xiserver> - name of my server)
Please help. Any ideas?
Maxim.

HI,
HTTP response code : 500 Internal Server Errors
Description: The server encountered an unexpected condition which prevented it from fulfilling the request.
Possible Tips: Have a look into SAP Notes 804124, 807000
From Notes :
<i>The problem can be solved in most cases by forcing the XI self-registration to use fully qualified host names.
For XI Integration Builder, Integration Engine and Runtime Workbench, you accomplish this by entering fully qualified host names in the XI Exchange Profile, then initiating a new self-registration (restarting the J2EE engine).
For the Adapter Engine, the approach is different: Change the properties "SLD.selfregistration.httpPort", "SLD.selfregistration.httpsPort" and "SLD.selfregistration.hostName" of the J2EE service SAP XI AF CPA Cache. Enter the fully qualified host name under which the Adapter Engine can be reached from all relevant network domains. Do this in the Visual Administrator of the J2EE Engine. Then restart the applications "com.sap.aii.af.cpa.app" and "com.sap aii.af.app", or restart the complete J2EE engine. This triggers a new Adapter Engine self-registration.
Go in the Integration Server (IS) to transaction "SXI_CACHE -> Goto -> Adapter-Engine-Cache" and delete the old Adapter Engine cache entries. After that the cache is refreshed from SLD as soon as a new message in sent to the respective Adapter Engine.
Check: After restart, navigate in SLD through "Content Maintenance -> XIAdapter Framework" to your Adapter Engine. As part of the "associated instances" you find e.g. at "XI Adapter Service XIRA -> Associated Instances -> Port for XIRA of af.<SID>.<hostname>" the new URL with the fully qualified host name</i>
Regards
Chilla..
<i>Points rewarded if it id usefull..</i>

SOAP: response message contains an error XIServer/UNKNOWN/ADAPTER.JAVA_EXCE

Hi ,
I am getting below error in SOAP reciever channel.
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: SOAP: response message contains an error XIServer/UNKNOWN/ADAPTER.JAVA_EXCEPTION - com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Connection SOAP_http://sap.com/xi/XI/System is currently not started. at com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:996) at sun.reflect.GeneratedMethodAccessor501_10002.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy2662_10002.process(Unknown Source) at com.sap.aii.af.app.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:275) at sun.reflect.GeneratedMethodAccessor326_10002.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy114_10002.process(Unknown Source) at com.sap.aii.adapter.soap.web.MessageServlet.callModuleProcessor(MessageServlet.java:175) at com.sap.aii.adapter.soap.web.MessageServlet.doPost(MessageServlet.java:470) 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)

Hi,
Can you please elaborate more on your problem.
Regards,
Raghu.

SOAP to SOAP scenario - XIServer:UNAUTHORIZED

Hello,
I created a scenario synchronous SOAP<>PI<>SOAP, but when I consume the WS (using soapui) this show me the next error:

<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
   <SOAP:Body>
      <SOAP:Fault>
         <faultcode>SOAP:Server</faultcode>
         <faultstring>Server Error</faultstring>
         <detail>
            <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
               <context>XIAdapter</context>
               <code>ADAPTER.JAVA_EXCEPTION</code>
               <text>com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIServer:UNAUTHORIZED:
     at com.sap.aii.adapter.soap.web.SOAPHandler.processSOAPtoXMB(SOAPHandler.java:663)
     at com.sap.aii.adapter.soap.web.MessageServlet.doPost(MessageServlet.java:447)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:202)
     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:103)
     at com.sap.engine.services.servlets_jsp.server.servlet.AuthenticationFilter.doFilter(AuthenticationFilter.java:126)
     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:428)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
     at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:276)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
     at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     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:78)
     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:78)
     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:78)
     at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)
     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:462)
     at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:270)
     at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
     at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
     at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
     at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)</text>
            </s:SystemError>
         </detail>
      </SOAP:Fault>
   </SOAP:Body>
</SOAP:Envelope>
I get the url from directory (sender component):
http://server:port/XISOAPAdapter/MessageServlet?senderParty=&senderService=BS_DEMOWS_100&receiverParty=&receiverService=&interface=SI_SendSMS&interfaceNamespace=http://namespace.com/WS/SendSMS
Into de SXI_MONITOR I can see errror:
<?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>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">UNAUTHORIZED</SAP:Code>
<SAP:P1>401</SAP:P1>
<SAP:P2>Unauthorized</SAP:P2>
<SAP:P3>(See attachment HTMLError for details)</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Authorization error while sending by HTTP (error code: 401 , error text: Unauthorized)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
And in the /MessagingSystem/monitor the log is:
2011-11-16 11:42:46.56 Success SOAP: request message entering the adapter processing with user XSICONSULTOR
2011-11-16 11:42:46.561 Success Application attempting to send an XI message synchronously using connection SOAP_http://sap.com/xi/XI/System
2011-11-16 11:42:46.562 Success Trying to put the message into call queue
2011-11-16 11:42:46.563 Success Message successfully put into the queue
2011-11-16 11:42:46.564 Success Message retrieved from call queue
2011-11-16 11:42:46.564 Success Message status set to DLNG
2011-11-16 11:42:47.101 Error Received XI System Error. ErrorCode: UNAUTHORIZED ErrorText: null ErrorStack: Authorization error while sending by HTTP (error code: 401 , error text: Unauthorized)
2011-11-16 11:42:47.101 Error Transmitting the message using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIServer:UNAUTHORIZED:
2011-11-16 11:42:47.102 Error Message status set to FAIL
2011-11-16 11:42:47.102 Error Returning to application. Exception: com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIServer:UNAUTHORIZED:
2011-11-16 11:42:47.103 Error SOAP: call failed: com.sap.aii.af.lib.mp.module.ModuleException: senderChannel 2e4c634fdd973c1c9c0323846834136d: Catching exception calling messaging system
2011-11-16 11:42:47.103 Error SOAP: call failed com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIServer:UNAUTHORIZED:
The XSICONSULTOR user has the next roles:
SAP_ALM_ADMINISTRATOR
SAP_ALM_CUSTOMIZER
SAP_SLD_ADMINISTRATOR
SAP_SLD_CONFIGURATOR
SAP_SLD_DEVELOPER
SAP_SLD_GUEST
SAP_SLD_ORGANIZER
SAP_XI_ADMINISTRATOR_ABAP
SAP_XI_ADMINISTRATOR_J2EE
SAP_XI_APPL_SERV_USER
SAP_XI_BPE_ADMINISTRATOR_ABAP
SAP_XI_BPE_CONFIGURATOR_ABAP
SAP_XI_BPE_MONITOR_ABAP
SAP_XI_CONFIGURATOR_ABAP
SAP_XI_CONFIGURATOR_J2EE
SAP_XI_CONTENT_ORGANIZER_ABAP
SAP_XI_CONTENT_ORGANIZER_J2EE
SAP_XI_DEMOAPP
SAP_XI_DEVELOPER_ABAP
SAP_XI_DEVELOPER_J2EE
SAP_XI_DISPLAY_USER_ABAP
SAP_XI_DISPLAY_USER_J2EE
SAP_XI_IS_SERV_USER
SAP_XI_MONITOR_ABAP
SAP_XI_MONITOR_J2EE
Z_PFUSER
And the profiles:
SAP_ALL
SAP_NEW
I don't know what happen, may be is a problem of configuration of PI but I don't understand what.
I hope that somebody have any idea and if you required more information I don't have problem.
Thank you in advance.
Greetings.
P.D.
I'm sorry the editor doesn't respet the tags.
--erva
Edited by: Esteban Vera on Nov 16, 2011 6:56 PM

Hi Esteban,
Increase the parameters in the Config Tool in the com.sap.security.core.ume.service service as below:
ume.ldap.connection_pool.max_size (default: 10) - change to 100
ume.ldap.connection_pool.max_wait_time (default: 60000) - change to 100000
(note 948654)
Also ensure you have maintained the correct password, which MUST be the same, for all the service users
on XI. You may check all the places it should be maintained, such as Exchange Profile, SU01, SLDAPICUST, etc..
Check the note below:
#999962 - PI 7.10: Change passwords of PI service users
And ensure that the user has the correct role as per link below:
http://help.sap.com/saphelp_nwpi71/helpdata/en/9f/d12940cbf2195de10000000a1550b0/frameset.htm
Kind regards,
Caio

XI - XIServer:ID_SA_MAX_CALLS_EXCEEDED problem

Similar Messages

Maybe you are looking for