cancel
Showing results for 
Search instead for 
Did you mean: 

Error on SXMB_ADM and proxy runtine in RWB

Former Member
0 Kudos

Hello all,

2 questions :

First one :

I am configuring an abap proxy.

I made all connections and RFC Destination. SLDCHECK working fine.

When i do a check by the t-code sxmb_adm on the receiver system and application system url as dest://<the Http dest con to XI>, a error says :

"

Role of Business System: Application System

Corresponding Integration Server: dest://INTEGRATION_SERVER_ECC

System Landscape :

No access to system landscape at present

Comparison of Current Configuration with System Landscape

Role of Business System: Current Configuration = System Landscape"

I have check this blog and i've done everything on it :

/people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies

Is this message normal ? As i wrote before, all my RFC/ HTTP destination works fine, idem for my sldcheck on my ECC.

Second one :

When i look in my RWB -> component monitoring -> Integration Engine -> Proxy runtime

I saw my proxyruntime_ECC in Red. It says :

"

Message: Unable to log on to system ECC in language EN with user PIRWBUSER

Stacktrace:

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

at com.sap.aii.rwb.core.R3System.getJCOPool(R3System.java:871)

at com.sap.aii.rwb.core.R3System.getJCOPool(R3System.java:726)

at com.sap.aii.rwb.core.R3System.getJCOPool(R3System.java:698)

at com.sap.aii.rwb.core.R3System.getRepository(R3System.java:910)

at com.sap.aii.rwb.core.BusinessSystem.getRepository(BusinessSystem.java:802)

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

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

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

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

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

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

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

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_Secure1204540347192._jspService(jsp_FC_Secure1204540347192.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:566)

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

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

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

I think there ise a conflict with the user PIRWBUSER but i don' t the RFC or HTTP connection it use for connectinf to my R/3 backend. there is not informations in the settings tab -> categories -> RFC-SYSTEM-INFO.

How can i know which connection it used ?

Thanks by advance,

Best regards,

JP

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

Just check if the user exists in the ETD system...thats it

regards

krishna

Former Member
0 Kudos

thanks jean-charles and krish,

Actually, the user has been "magicaly" delete...:/

It has been create and it wordks fine now..thanks.

Former Member
0 Kudos

Which system has SP14 ? Application system or Integration server.

Your log let think the error occured in application system.

The related note must be executed on integration server

Former Member
0 Kudos

Error from me.

My sap basis is in sp13. you were right.

Thanks again.

Jean-Philippe.

Answers (1)

Answers (1)

Former Member
0 Kudos

For the first question :

Check note : 1076846 - XI runtime: Incorrect message in transaction SXMB_ADMIN

Former Member
0 Kudos

For the second one, you must create the user PIRWBUSER on all local integration engine systems you want to monitor in end to end monitoring tool.

Check PMI post-instalation steps.

Former Member
0 Kudos

Thanks for the answers.

For the PIBWRUSER; i send the documentation and your advices to admins.

For the note, it suggest to be in SP 14 for sap basis 7.0 and i am in sp13.i will correct this.

Thanks for answers,

JP

Edited by: Jean-Philippe PAIN on Mar 4, 2008 11:29 AM