Neither the messager server nor the application server can be reached

[Former Member]

I am running XI 3.0 sp12, oracle 9.2.0.6 on windows 2003 cluster.

I have just consolidated my SLDs into one (from three), as per SAP Notes, but now, when I go into the runtime workbench on our QA system, select component monitoring, and click either Integration Builder or Business Process Engine,I get a red traffic light and the following error:

Details for 'Ping Status'

Message: Neither the messager server nor the application server can be reached for system XIT

Stacktrace:

com.sap.aii.rwb.exceptions.OperationFailedException: Neither the messager server nor the application server can be reached for system XIT

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

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

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

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

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

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

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

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

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

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

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

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

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

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

at jsp_FC_Secure1125580234490._jspService(jsp_FC_Secure1125580234490.java:26)

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

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

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

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

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

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

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

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

at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)

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

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

How can I resolve these errors??

Regards

[MichalKrawczyk · Accepted solution]

Hi Barry,

all of your SDL checks (SLDCHECK, etc.) work on QA?

(as per note from your previous post)

Regards,

michal

[Former Member · Accepted solution]

Michal

All working correctly from SLDCHECK.

Broswer Launched successfully.

Summary: Connection to SLD works correctly.

Summary: Connection to the XI Profile works correctly.

The one thing I did notice was in the RWB on the SLD:

In Technical Landscape:

RWB on XID - points to app server

RWB on XIT - points to db server

RWB on XIP - points to app server

They also to appear like this for Integration Directory and Integration Repository.

These were automatically created...

[MichalKrawczyk · Accepted solution]

The error from RWB may not tell us a lot:)

try searching for more errors in VA

(in logs shown in my weblog):

if you won't find any more error descriptions

try sending a test message on QA then maybe some more

errors will appear and you'll see some more error descriptions

maybe this will help to recognize what's going on

Regards,

michal

[Former Member · Accepted solution]

Michal

Thanks for your input.

Issue resolved.

Barry

[Former Member · Accepted solution]

> Michal

>

> Thanks for your input.

>

> Issue resolved.

>

> Barry

How do you solve the problem?

I have exactly the same. I switched my SLD from one server to another. I have 3 SAP backends with proxy runtime. In the RWB I have green lights for T and QA but a red one for the proxy runtime of my P system. Under ping status details have the same exception. Parameters LCRSAPRFC and SAPSLDAPI are correct an equal to the parameters of the T and QA Systems. SLDCHECK looks fine.

[s0002529520 · Accepted solution]

Has anyone found out what the solution to this problem was? I have exactly the same issue after a failover to a different server.

[former_member183898 · Accepted solution]

Hi All,

Error is because MEssage server & Applications erver details are missing in Technical system mentioned in SLD.

Thanks,

Pushkar