cancel
Showing results for 
Search instead for 
Did you mean: 

com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION

Former Member
0 Kudos

Hi,

I know, JCO configuration was already 1000 times discussed. I have read many threads but i didn't find solution to my problem.

When I test JCo for metadata an error occured:

com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=sap47c13 GROUP=PUBLIC R3NAME=C13 MSSERV=sapmsC13 PCS=1 ERROR service 'sapmsC13' unknown TIME Thu Mar 02 09:51:43 2006 RELEASE 640 COMPONENT NI (network interface) VERSION 37 RC -3 MODULE ninti.c LINE 505 DETAIL NiPGetServByName2: <b>service 'sapmsC13' not found</b> SYSTEM CALL getservbyname_r COUNTER 1

I suppose that error reason is that message service couldn't been find by name (that suggest error message).

I can connect with my R3 host (telnet) on port 3600 but can not on service "sapmsC13" (despite i have entry "sapmsC13 3600/tcp # SAP System Message Port" in my services file on R3 host).

My sld is running, R3 system is in technical landscape.

What more should i do to correct "mapping" port to service name?

Can anybody help me?

regards

Bogdan

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi

Make service entry for sampmsC13 ( C13 = SID for R/3) on the J2EE host. and also Check whether PUBLIC group is availablein your R/3 System. Transaction SMLG.

Give a system reboot for J2EE host.

Should work.

Deepti

Former Member
0 Kudos

Hi Deapti,

I know now that entry for message server must be on both side.

Thanks a lot

Bogdan

Former Member
0 Kudos

Hi ,

Can you explain the solution for this problem.I am novice in portal.

Please help me regarding this.

Thanks,

Rao.

Answers (0)