RFC_ERROR_COMMUNICATION

[yogesh_galphade]

Hi All

I getting this error; also checked the troubleshooting guide and followed the given solutions

But still getting this error, if I refresh the iview this error goes.

com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: CPIC-CALL: CMRCV on convId: 83148368 LOCATION SAP-Gateway on host erpapprcl4 / sapgw00 ERROR Conversation 83148368 not found TIME Fri Nov 28 16:43:05 2008 RELEASE 700 COMPONENT SAP-Gateway VERSION 2 RC 728 MODULE gwxxrd.c LINE 6012 COUNTER 69583

Any permanent solution?

As guide described we are on load balanced server

The comments in troubleshooting guide:

Likely Causes:

1. The R/3 which you are trying to connect to is down or overloaded. Please login through the SAPLogon

to check if this works.

2. The most likely reason could be that the RFC communication service is not maintained for the R/3

system you want to use on the J2EE.

Solution:

The solution is with respect to Point 2 above

1. In the file %windir%\system32\drivers\etc\services add an entry

sapms<SID> <PORT>/tcp" (<SID> = R/3 system ID, <PORT> = message server port).

2. Run "Update SAPPCADM" in Windows Start / SAPPCADM. This will (among other things) update

the above mentioned file with data for SAP internal R/3 systems. This is only for Internal SAP use.

The error only occurs for "load balanced" connections as only these need this message server entry.

Solution 1. Is done in CI

Solution 2. It is for windows .Cant apply here in Solaris OS

[Former Member · Accepted solution]

So you're trying to connect to server "erpapprcl4" system 00, right?

What type of RFC connection is this? A regular R/3 connection?

[yogesh_galphade · Accepted solution]

Hi

Thanks for reply

Yes it is trying to connect erpapprcl4, there are another three r/3 servers.

In portal fetching data for applications using JCO (ticket).

[Former Member · Accepted solution]

 Yes it is trying to connect erpapprcl4, there are another three r/3 servers. 

Yogesh, Check if you are able to reach the r/3 servers from the portal using the hostname erpapprcl4. Try pinging to erpapprcl4 from OS level.

Also check if the entry sapgw00 is there in the etc/services file in the portal server.

Cheers,

Jazz

[Former Member · Accepted solution]

hi,

I had the same problem before and solved it as per the below steps

1. the network team changed the Alias name in Unix

2. Increased the Server node in Portal

3. Increased the time out in JCO settings.