cancel
Showing results for 
Search instead for 
Did you mean: 

Recv. Detrmtn Error

Former Member
0 Kudos
61

Hi,

While testing the configuration:

Receiver Determination <Not found>

Runtime error Error while refreshing the XI runtime cache

<Trace level="1" type="B">CL_RD_PLSRV-ENTER_PLSRV</Trace>... (2 lines)

I have activated all objects before testing.

Plz give the relevant solution for this error.

Regards,

Balaji

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Check

sxi_cache and also check whether you defined the Receiver

determination

Answers (5)

Answers (5)

Former Member
0 Kudos

HI

Check

SXI_CACHE and also check the Receiver determination

regards

Former Member
0 Kudos

Hi,

Check the SXI_CACHE and receiver determination, still problem occur then delete the receiver determination and again create and active, after test the scenario.

samiullah_qureshi
Active Contributor
0 Kudos

Hi

In addition to check INTEGRATION_DIRECTORY_HMI rfc destination also do the complete CPA cache refresh by using following URL

[http://<host>:<port>/CPACache/refresh?mode=full]

Regards

Sami

Reward points if helpful.

prateek
Active Contributor
0 Kudos

Check if INTEGRATION_DIRECTORY_HMI rfc destination is working

Regards,

Prateek

Former Member
0 Kudos

Hi,

In XI Server, T.Code SM59, HTTP Connections to ABAP System->

INTEGRATION_DIRECTORY_HMI

if i do the Connection test, it is showing one popup box:

Response from Web Server Contains Cookies

Accept?

if i click yes or no,

in the test result tab,

it is showing Status Text as

Internal Server Error

Also,

In the Runtime Workbench, when i click Message Monitoring tab, it is showing this error:

javax.ejb.CreateException: Unable to log on to system IDS in language en with user PIRWBUSER

Also, in the Component Monitoring,

Components>Integration Engines>

Proxy Runtime BS_IDES_765

Here, BS_IDES_765 is the business system i created in SLD.

Showing error as:

Details for 'Ping Status'

Message: Unable to log on to system BS_IDES_765 in language en with user PIRWBUSER

Stacktrace:

com.sap.aii.rwb.exceptions.OperationFailedException: Unable to log on to system BS_IDES_765 in language en with user PIRWBUSER

at com.sap.aii.rwb.core.XIAbapRTCComponent.getConnector(XIAbapRTCComponent.java:114)

at com.sap.aii.rwb.core.XIRTCComponent.ping(XIRTCComponent.java:199)

at com.sap.aii.rwb.web.componentmonitoring.model.CompTestModel.doPing(CompTestModel.java:583)

at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.doPing(CmDynPage.java:298)

at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.updateTests(CmDynPage.java:372)

at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.selectNode(CmDynPage.java:388)

at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.process_treeClick(CmDynPage.java:339)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:324)

at com.sapportals.htmlb.page.DynPage.doProcessCurrentEvent(DynPage.java:172)

at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:115)

at com.sapportals.htmlb.page.PageProcessorServlet.handleRequest(PageProcessorServlet.java:62)

at com.sapportals.htmlb.page.PageProcessorServlet.doPost(PageProcessorServlet.java:22)

at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmPageProcessor.doPost(CmPageProcessor.java:35)

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.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)

at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)

at jsp_FC_Secure1208243635625._jspService(jsp_FC_Secure1208243635625.java:24)

at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)

at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:544)

at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:186)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)

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:100)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

Regards,

Balaji

Former Member
0 Kudos

thanks for all replies...

Former Member
0 Kudos

Hi,

Check in the area SXI_CACHE.

and double check your receiver determination for receiver details.

Thanks,

Inidra D