XIServer: USER_CONTEXT_ERROR
Hello Everyone,
I hope that you could help with this problem that i'm facing. I Found some post related but with no answer about the problem.
Actually in any scenario with XI -> Proxy (Abap Proxy, XI channel) the message are processed wel but when the Call Adapter step is executed, the error in XI MONI is the next:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Adapter
-->
- <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">USER_CONTEXT_ERROR</SAP:Code>
<SAP:P1>Error al acceder a la memoria segura (-> Evaluar trace)</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>create_user_context</SAP:AdditionalText>
<SAP:Stack>An Error Has Occurred in User Context Error al acceder a la memoria segura (-> Evaluar trace)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
We presented this error recently, on DEV environment. Until this moment we dont know what could be the cause. If you have some advice, I'll appreciate a lot.
I found this link: USER_CONTEXT_ERROR
Regards,
Vicman
Hi Vicman,
In SECSOTRE transaction we can see a lot of error entries. You may clean the error entries under SECSTORE transaction.
And for your reference, please check:
#816861 - Migrating entries in the secure storage
You may delete the entry "/SEC/USERINFO/CL_XMS_USER_CONTEXT===========CP has an error'."
This should solves the issue.
Best regards,
Caio Cagnani
Similar Messages
-
SOAP:XIServer/UNKNOWN/ADAPTER.JAVA_EXCEPTION
Hi All,
I am getting the following error in Receiver SOAP adapter. Can anybody suggest wt could be the resone.
Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIServer/UNKNOWN/ADAPTER.JAVA_EXCEPTION - com.sap.aii.af.mp.module.ModuleException: either no channelID specified or no channel found for the specified party, service, and channel name, MessageServlet(Version $Id: //tc/xi/NW04S_18_REL/src/_adapters/_soap/java/com/sap/aii/af/mp/soap/web/MessageServlet.java#1 $) at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:427) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) 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:104) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)either no channelID specified or no channel found for the specified party, service, and channel name,
Is the channel properly created and present in ID, visible in RWB and SXI_CACHE?
Also are you refrering the proper channel in Receiver Agreement?
Do a dummy change to the channel...save...activate...refresh cache and then check.
Regards,
Abhishek. -
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. -
RFC-to-SOAP-Scenario: XIServer:NO_MAPPINGPROGRAM_FOUND
Hey guys,
We've implemented in SAP PI 7.11 a RFC-to-SOAP-Scenario. The whole scenario is sync. WSDL and RFC are imported objects.
Now we're going on to test in backend and call the related remote function module via se37.
The error message is (from xsmb_moni)::
<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="MAPPING">NO_MAPPINGPROGRAM_FOUND</SAP:Code>
<SAP:P1>Object ID A2DC458230C93030AE8B43396EEC43DB Software Component 83222F30FC9011DF8643DD3AC3E93CB3</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Mapping program is not available in runtime cache: Object ID A2DC458230C93030AE8B43396EEC43DB Software Component 83222F30FC9011DF8643DD3AC3E93CB3</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
What we've already done:
-> Cache refresh
-> server restart
-> soap fault mapping
-> dummy changes
-> mapping is available in sxi_cache
-> function module is not dumping in backend
Any ideas how we can go futher with this?
Thank you very much and greetings,
StefanFYI...
Apparently, this error message can sometimes be misleading.
I found in another thread that this message came after a short dump in the ABAP function. After viewing ST22 in our backend system I noticed short dumps corresponding to the times when I make the SOAP call.
[NO_MAPPINGPROGRAM_FOUND SOAP RFC Adapter]
We can call SE37 with the same parameters and there is no ABAP error. So the search for root cause continues, but maybe this info will help someone.
-Aaron -
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:
<!--see the documentation-->
<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" ?>
- <!-- Call Adapter
-->
- <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 PMHi 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 -
Hi all
This is without BPM scenario.
I am doing a SOAP - XI - RFC - XI - SOAP scenario(this is a sync call)......also at the same time i am writing a file onto a directory in async mode.
What exactly i want is ...when i receive file from SOAP...i want to call RFC using an interface mapping in a sync mode....also the SOAP request i have received...i want to write it as a backup file onto a directory....using FILE receiver adapter in Async mode.
So basically wheen i configure it in a receiver determination.... i have two receiver 1. RFC 2. FILE and two interface determination and recevier agreement respectively ....but i am facing a problem where when i run this scenario...it gives me following error:
<context>XIAdapter</context>
<code>ADAPTER.JAVA_EXCEPTION</code>
<text><![CDATA[
com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:TOO_MANY_RECEIVERS_CASE_BE:
at com.sap.aii.adapter.xi.ms.XIEventHandler.onTransmit(XIEventHandler.java:455)
at com.sap.aii.af.ra.ms.impl.core.queue.consumer.CallConsumer.onMessage(CallConsumer.java:134)
at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:917)
at com.sap.aii.af.ra.ms.runtime.MSWorkWrapper.run(MSWorkWrapper.java:56)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(AccessController.java:219)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Please help !have two receivers.
one for the RFC and other one for the File.
The have their respective interface determinations.
Plus you need to have a BPM in this case -
SOAPFault received from Integration Server. ErrorCode/Category: XIServer/IN
Hello All,
I work on PI 7.1 and needed to create an interface using a simple File-to-File scenario. I created this without using any IR/ESR Objects as per a technical article on the website saptechnical dot com /Tutorials/XI/File2File/Demo1.htm
This worked perfectly fine in my dev environment. However, when I moved it to Test environment, I am having issues. Error message shown in RWB for Adapter engine is
SOAPFault received from Integration Server. ErrorCode/Category: XIServer/INBOUND_BINDING_ERROR; Params: BS_ECC100, http://abc, ecc-to-external; AdditionalText: null; ApplicationFaultMessage: null; ErrorStack: Error in sender agreement for party , service BS_ECC100, interface namespace http://abc interface ecc-to-external No sender agreement found for , , , , ,
Error Transmitting the message to endpoint http://piq.uk.rweutil.net/sap/xi/engine?type=entry using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Received HTTP response code 500 : Error during Sender Agreement Determination.
I checked the Sender agreement. It seems fine. All other components are also active, however I do not see the sender agreement in SXI_CACHE transaction. Any clues what could be wrong ?
Many thanks in advance .
Regards
RajivHi Rajiv,
Please perform below tasks
1. Logon Integration Directory
2. Click on 'Modification' icon, put a 'dummy' change (may a space) in the description field
3. Save the change
4. Active the changed objects
5. Repeat 2, 3, 4 steps for all those objects you moved to Test environment.
All the above steps, eventually leads to have forceble cache refresh, if this won't helps resolve, Please perform full CPACache refresh using below URl
http://<host name>:<http port>/CPACache/refresh?mode=full
I presume these instructions will help to resolve the issue.
Regards
Sekhar -
XIServer error raised: 503 Service Unavailable with SOAP Adapter
Hi,
We are getting a very strange error from a process that is working fine in 2 other environments.
We are sending a message into the SOAP receiver adapter and are getting the following error at the Call Adapter part of the process :
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Adapter
-->
- <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>503</SAP:P1>
<SAP:P2>Service Unavailable</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title>Error Report</title> <style> td {font-family : Arial, Tahoma, Helvetica, sans-serif; font-size : 14px;} A:link A:visited A:active </style> </head> <body marginwidth="0" marginheight="0" leftmargin="0" topmargin="0" rightmargin="0"> <table width="100%" cellspacing="0" cellpadding="0" border="0" align="left" height="75"> <tr bgcolor="#FFFFFF"> <td align="left" colspan="2" height="48"><font face="Arial, Verdana, Helvetica" size="4" color="#666666"><b>&nbsp;&nbsp;503 &nbsp Service Unavailable</b></font></td> </tr> <tr bgcolor="#3F73A3"> <td height="23" width="84"><img width=1 height=1 border=0 alt=""></td> <td height="23"><img width=1 height=1 border=0 alt=""></td> <td align="right" height="23"><font face="Arial, Verdana, Helvetica" size="2" color="#FFFFFF"><b>SAP J2EE Engine/6.40&nbsp;</b></font></td> </tr> <tr bgcolor="#9DCDFD"> <td height="4" colspan="3"><img width=1 height=1 border=0 alt=""></td> </tr> </table> <br><br><br><br><br><br> <p><font face="Arial, Verdana, Helvetica" size="3" color="#000000"><b>&nbsp;&nbsp;The requested application, AFW, is currently unavailable.</b></font></p> <p><font face="Arial, Verdana, Helvetica" size="2" color="#000000"><table><tr><td valign="top"><b>&nbsp;Details:</b></td><td valign="top"><PRE>No details available</PRE></font></td></tr></table></font></p> </body> </html></SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP response contains status code 503 with the description Service Unavailable XML element Envelope missing in SOAP message header (SAP XI Extension)</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
We are on XI 3.0 SP13.
Any suggestions ?
Kind regards
Colin.Hi Colin,
Quick look into these-
1) Are you able to test the WebService, because the error tells about unavailable...
For more-
/people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi
/people/siva.maranani/blog/2005/03/01/testing-xi-exposed-web-services
2) Is your SOAP Receiver COnfiguration is correct
~ http://help.sap.com/saphelp_nw2004s/helpdata/en/29/5bd93f130f9215e10000000a155106/content.htm
3) Check the wsdl is correct and try look into the input message for the Webservice(SOAP Adapter)
Have a look into this thread-
503 service unavailable
Hope this helps,
Regards,
Moorthy -
Hi Experts,
we are testing file to RFC scenario. file adapter picked the file but not moving to Integration engine.we are getting below error someone can help us to resolve the issue. already we tested same one in development there it was works fine. but we are facing this problem in Quality.
we have done below checks also..
1. cache refresh (ESR, ID, Delta and full cache)
2.tested configurations in ID its working fine.
3. checked SXMB_ADM and and pipeline url and business systems in SLD. everything is fine.
4. when i checked in messaging system there i find something error like.
Transmitting the message to endpoint http://...sap/xi/engine?type=entry using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Received HTTP response code 500 : Error during Sender Agreement Determination
SOAPFault received from Integration Server. ErrorCode/Category: XIServer/INBOUND_BINDING_ERROR; Params: BC_xxxx, http://xxx//xxxx,; AdditionalText: null; ApplicationFaultMessage: null; ErrorStack: Error in sender agreement for party , service BC_xxxx, interface namespace http://xxx//xx, interface xxxx
No sender agreement found for , , , ,
can someone help us....
Regards,
vengal.Hi Vengal,
The error is only in one FTP scenario or all FTP scenario? Please check the below discussion
SOAPFault received from Integration Server. ErrorCode/Category: XIServer/IN
regards,
Harish -
Hi all,
I am currently doing a File --> RFC --> File synchronous interface ( I am not using RFC lookup functionality here ).
I am doing this scenario according to the following Wiki link,
[http://wiki.sdn.sap.com/wiki/display/XI/File-RFC-File(Without+BPM)]
When testing the interface, i am getting an error "Error: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:NO_MAPPINGPROGRAM_FOUND:" in the sender communication channel. I don't have any idea about this error, could anyone help me in this issue.
Cheers,
Sherin Jose PHi Sherin Jose P,
Please recheck your Integration Directory configuration for the scenario. Specially please check inbound interface determination settings. Here the communication channel is unable to find the interface mapping after receiving XML message. Did you use java mapping ? then please check the code again since it might not be producing exact target xml structure. Finally please ensure all mapping programs are existing and activated. If all mapping are activated then refresh the cache.
Please check in st22 transaction all errors in PI, whenever you get this message. There may be other reasons of error as well. There can be occasional short dumps due to data lengths or validations in ABAP programs. These short dumps in ERP may cause failures raised in PI.
Finally if there are some exception in mapping then this error you can expect.
Hope this helps.
regards
Anupam -
XIServer/IN_BIND_WRONG_ADPT
Until now I had 2 systems Dev and Prod. Dev was patched to SP17 two weeks ago, Prod is still SP15. All works fine till last week. Then we got a QA XI System with SP17. Therefore we made some changes in our central SLD. And no I have a lot of problems with my Dev system.
First of all: I have errors at every message processing. When I view the audit protocol at rwb message monitoring I get the following: (in german)
SOAPFault empfangen vom Integration Server. ErrorCode/Category: XIServer/IN_BIND_WRONG_ADPT; Params: SOAP; AdditionalText: ; ApplicationFaultMessage: ; ErrorStack: Die gefundene Sendervereinbarung gehört zum Adapter SOAP. Der aktuelle Adapter ist aber 'XI'.
That means, in the sender agreement a SOAP adapter is defined, but a XI adapter is sending. But I send the message with XML Spy to a SOAP adapter.
http://host:port/XISOAPAdapter/MessageServlet?channel=:SERVICE:ADAPTER
The specified channel is defined as SOAP adapter in the repository. I don't know why the AF sconsiders this as a xi adapter since last friday.
Furthermore in the adapter monitor of the rwb none of my configured adapters is visible. But when I view at the new communication channel monitor I can see all my channels with status "started but inactive" or with error, when I have used this channel.
Yes, I know Adapter-Q3 of the XI FAQ.
I have no idea where I can start fixing this problem.The problem was solved by Stefan Grube in this thread:
Java proxy client with HTTP sender
Thanks. -
XIServer:LCR_ERROR:No own business system
Hi Experts,
I am having a inbound scenario SOAP - > XI - > PROXY where I am gettiing the following error while testing from SOAP UI for Sender SOAP Adapter.
<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.aii.af.ra.ms.api.DeliveryException: XIServer:LCR_ERROR:No own business system
at com.sap.aii.adapter.xi.ms.XIEventHandler.onTransmit(XIEventHandler.java:455)
at com.sap.aii.af.ra.ms.impl.core.queue.consumer.CallConsumer.onMessage(CallConsumer.java:134)
at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:910)
at com.sap.aii.af.ra.ms.runtime.MSWorkWrapper.run(MSWorkWrapper.java:56)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java(Compiled Code))
at java.security.AccessController.doPrivileged1(Native Method)
at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code))
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code))
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code))</text>
</s:SystemError>
</detail>
</SOAP:Fault
I have tested the SLDCHECK, SLDAPICUST and also the LCRSAPRFC working fine. Also the business system in SLD is OK.
I have no clue why the error is thrown.
Please help me in resolving the issue.
Thanks,Check if the user mentioned in SLDAPICUST is locked. What is the type of Business System used in SLD?
Regards,
Prateek Raj Srivastava -
When I am testing java map in XI.every time connection to the XIserver lost
Hi All,
When I am testing java map in XI.every time connection to the XI server lost.XI is asking for login again
Can any one help me on this.what could be the problem
Thanks
SireeI dont no whether problem with java code or XI .but its a very simple java code.
Just i am getting 6 Xpath values and comparing those values with "" OR Null.if the condition is true i am displaying some text message.
Sample Code
execute(in,out)
Xpath1
Xpath2
if("".equls(Xpath1)||Xpath1==null)
Textmessage = No value in Xpath1 -
Value Mapping Replication : Error Category: XIServer
Hi All,
I'm doing a value mapping replication. Have configured the interface proxy-pi (Async) and the message is transferred to pi with no issues but in pi the message is logged with the following error as in payload:
>Error while receiving by HTTP (error code: 200, error text: Error Parsing Response. No XI Response Received
Link to payload > [http://www.esnips.com/web/SAPIssues ]
tried various cases yet the issue remains the same. any helpful tip on this?
thanks
PrabhuError in RWB: To be delivered
Error in moni: Payload as posted in the thread (refer link)
Error in SMQ2: User column:XIISUSER statustext column: Command to tRFC/qRFC: Execute LUW again -
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!!!
RedID_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.
Maybe you are looking for
-
How to add a signature at the end of each post
How do you add a signature at the end of each post (if possible)? ^^right now, I just have to copy and paste that
-
Hi! I'm now building an extension for Photoshop. The script (jsx) should save the active document as Photoshop PDF secured with a password. The PW is the same all the time and is set in the script. Then the script is to open the PDF with that same pa
-
Weblogic Configuration with Apache 2.2
Hi , I am getting the below error configured weblogic 10.3.5 with apache 2.2 <HTML> <HEAD> <TITLE>Weblogic Bridge Message </TITLE> </HEAD> <BODY> <H2>Failure of server APACHE bridge:</H2><P> <hr>Your content length exceeded INT_MAX<hr> </BODY> </HTML
-
Parse time for OLAP SQL statements
Hello! I have built ROLAP cube and now trying to analyse performance. Most of problems are coming from SQL statements which are prepared by BI beans (Disco or Excel). These statements have a very big parse time because they use IN predicates with a l
-
Filter for exposure compensation
When bracketing exposures, as is often done for landscape work HDR, etc), you typically end up with a large number if variants. It would be very helpful to be able to identify all images with a given exposure bias (typically zero). You could then qui