Neither the messager server nor the application server can be reached

[former_member209575]

Hi All,

I am getting one error in End to end monitoring and Configuration in RWB, Please help me.

In End to end monitoring

Neither the messager server nor the application server can be reached for system pirdev.xxx.co.in

In Configuration

Cannot read the configuration for the selected domain because the system was unable to connect to the monitoring server (possibly due to incorrect logon data). Error message: Neither the messager server nor the application server can be reached for system pirdev.xxxx.co.in

in Logs and trace -> Default Trace following error

***************************************************************************************************************

Full Message Text

enrichMessageData(): JCO-Communication error during retrieving the end-to-end-monitoring information

Thrown:

com.sap.mw.jco.JCO$Exception: Connect to SAP gateway failed

Connect_PM TYPE=A ASHOST=pirdev.xxxx.co.in SYSNR=00 GWHOST=pirdev.xxxx.co.in GWSERV=sapgw00 PCS=1

LOCATION CPIC (TCP/IP) on local host with Unicode

ERROR hostname 'pirdev.xxxx.co.in' unknown

TIME Mon Dec 29 12:02:54 2008

RELEASE 700

COMPONENT NI (network interface)

VERSION 38

RC -2

MODULE nixxhsl.cpp

LINE 223

DETAIL NiHsLGetNodeAddr: hostname cached as unknown

COUNTER 2

Connect_PM TYPE=A ASHOST=pirdev.xxxx.co.in SYSNR=00 GWHOST=pirdev.xxxx.co.in GWSERV=sapgw00 PCS=1

LOCATION CPIC (TCP/IP) on local host with Unicode

ERROR hostname 'pirdev.xxxx.co.in' unknown

TIME Mon Dec 29 12:02:54 2008

RELEASE 700

COMPONENT NI (network interface)

VERSION 38

RC -2

MODULE nixxhsl.cpp

LINE 223

DETAIL NiHsLGetNodeAddr: hostname cached as unknown

COUNTER 2

at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:457)

at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1025)

at com.sap.mw.jco.JCO$Client.connect(JCO.java:3255)

at com.sap.aii.mdt.api.server.MessageMonitoringBean.enrichMessageData(MessageMonitoringBean.java:976)

at com.sap.aii.mdt.api.server.MessageMonitoringBean.setMessageList(MessageMonitoringBean.java:776)

at com.sap.aii.mdt.api.server.MessageMonitoringBean.getPureMessageList(MessageMonitoringBean.java:582)

at com.sap.aii.mdt.api.server.MessageMonitoringObjectImpl1_0.getPureMessageList(MessageMonitoringObjectImpl1_0.java:979)

at com.sap.aii.mdt.api.server.MessageMonitoring_Stub.getPureMessageList(MessageMonitoring_Stub.java:1663)

at com.sap.aii.mdt.server.integrationserver.IntegrationServerMonitoringBean.getMessageList(IntegrationServerMonitoringBean.java:384)

at com.sap.aii.mdt.api.server.MessageMonitoringBean.setMessageList(MessageMonitoringBean.java:758)

at com.sap.aii.mdt.api.server.MessageMonitoringBean.getMessageList(MessageMonitoringBean.java:566)

at com.sap.aii.mdt.api.server.MessageMonitoringObjectImpl1_1.getMessageList(MessageMonitoringObjectImpl1_1.java:933)

at com.sap.aii.mdt.api.server.MessageMonitoring_Stub.getMessageList(MessageMonitoring_Stub.java:1552)

at com.sap.aii.mdt.util.WebUtil.generateTableViewModel(WebUtil.java:1279)

at jsp_monitor_new1224156038796._jspService(jsp_monitor_new1224156038796.java:9)

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

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

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

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

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(AccessController.java:219)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)

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

[Former Member]

Hi,

You have to make entry of fully qualified domain name and ip into host file of your PI server for all SAP system to which PI is connected.

Thanks,

Tuhin

[Former Member]

Hi Pradeep

first make a cache refresh. It might be that you did some change and some wrong entry is there in CACHE

so do a full cache refresh

error is that your host is not reachable

go to tcode sm49 and under the tag ping give ur server url and check if its reachable

unitl your server is not reachable ABAP and JAVA stack cant communicate each other and it will show you SAP gateway JCO error

Check whether you have given the right host name and right credential to login. If you are very sure that you have given right credentials then your problem will be solved by restarting J2EE engine

steps to restart J2EE engine

1) run transaction SMICM

2) then in the tab administration => J2EE instance(local) =>send soft shutdown with restart

by this java engine will restart and will be up in 5-10 minutes and your problem will be solved

Thanks

sandeep sharma