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 to ALL,

I have a problem in getting access to one of my servers

we have two servers one NDB and ODB both logon groups are same

but when i tried to test the JCO Connections

i have problem with the following error

could you please let me how can i resolve this,

com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=B MSHOST=co-odb-dev GROUP=UNILOG_LINK_RFC R3NAME=ODB MSSERV=sapmsODB PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '172.31.208.121:3320' not reached TIME Tue May 12 21:57:16 2009 RELEASE 700 COMPONENT NI (network interface) VERSION 38 RC -10 MODULE nixxi.cpp LINE 2764 DETAIL NiPConnect2 SYSTEM CALL connect ERRNO 10060 ERRNO TEXT WSAETIMEDOUT: Connection timed out COUNTER 1

both my service file and host file .

To be more elobarated,

we have natted IP's (10.83 series ) that hits 172 series and its 172 series where the server lies.

so we access this 10.83 series in our host file.

but we have no problem with one of our servers, problem is with ODB which is the second server.

the same rules is applied for this too.

thanks in advance

Regards

Chandra

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi PJ,

to your question

Also, verify that you can get to the Web Dynpro console on ODB?

i am testing this from the webdynpro content administrator and not on webdynpro console

we have a local server where we created JCO destinations which points to 4 servers one to NDA,NDB,ODA,ODB

it croses geographies, we the developers do the dev from india and the servers are in france

clients series starts with 172 series and they give natted IP's to access their servers

these are managed directly by our clients

these natted IP's are configured in the host file and service files

NDA NDB ODA are fine. they point to 10.83 series which i have told previously

the problem is ODB.

Do you have the idea how they point to these type of things in the servers and how they do it.

here the sap admnistrator at france doesnt know what to do, we spoke with them today

could you please help its really critical for us

Kind Regards

Chandra

Edited by: chandrasekhar.klmn on May 13, 2009 3:20 PM

Former Member
0 Kudos

Chandra

So you are able to login to the ABAP stack of ODB with SAP GUI?

If so, please verify that the following:

- RFC settings are identical from ODB and NDB.

- syntax of logon groups

- syntax of security and connection information in JCO connection

- IP addresses and ports were NATed correctly

Hope this helps!

PJ

Former Member
0 Kudos

HI PJ,

we tried to check the points we did,

Please find the solution what we did, its working now

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

RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed

Connect_PM TYPE=B MSHOST=apollon GROUP=RFC_balancing R3NAME=ODA MSSERV=sapmsODA PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '172.26.8.7:3310' not reached TIME Wed Aug 29 17:58:06 2007 RELEASE 700 COMPONENT NI (network interface) VERSION 38 RC -10 MODULE nixxi.cpp LINE 2764 DETAIL NiPConnect2 SYSTEM CALL connect ERRNO 10061 ERRNO TEXT WSAECONNREFUSED: Connection refused COUNTER 1

**Check that the gateway is accessible from the AS JAva with the IP written in the error message.**

**If you are using a NAT network, the message server must return the IP usable by the AS Java. In that case, configure the IP in the logon group in transaction SMLG.**

**Check that the checkbox "external RFC enable" is not ticked.**

Once again thanks for your valuable suggestions

Regards

Chandra

0 Kudos

I am getting same error.

Can you please help to resolve this.

Regards,

Portal Developer

former_member214355
Contributor
0 Kudos

Hello Portal Developer

Please do not open an answered thread, rather provide details on your own query in a new thread.

Thanks

Kenny

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi,

I am able to ping with both Natted IP and also short name.

I have to check the nslookup from ODB

it would be great if you can tell me something about lookup at the server, i have been more of the development side and the whole sap related administration works from other location and i am very new to this side.

i can pass this on to the sap administration team how to do this.

thanks in advance.

Regards

Chandra

Former Member
0 Kudos

Chandra

Iu2019m not sure if you are asking for information on nslookup or saying that you will ask the admin team.

In either case, the admin team should be able to provide a great deal on information.

After checking that, can you provide the steps you are using to test?

Also, verify that you can get to the Web Dynpro console on ODB?

Hope this helps.

PJ

Former Member
0 Kudos

Hi ,

From webdynpro our the application cannot access the modules that are from ODB server,

for more information,

i am able to do SAP Logon to ODB server and acess all the function modules and so on, but when i try to test the JCO i am resulting with this exception,

the administration team is not able to identify the problem,so we are all trying to see where the problem is.

i have tried to see all the threads but all are scenario specific.

it would be helpful if you/someone can answer or give your valuable suggestions on this.

thanks in advance

Kind Regards

Chandra

Former Member
0 Kudos

hi

thanks for the quick reply

i am able to ping it with the natted IP(ODB)- 10.83 series- this is the server where i get a JCO Exception

i am able to ping NDB- 10.83.series- i am able to test JCO successfully

thanks in advance

Regards

Chandra

Former Member
0 Kudos

>

> i am able to ping it with the natted IP(ODB)

>

Chandra

Did you also try pinging the ODB server with short name and FQDN ?

And nslookup on the ODB server with server name?

PJ

Former Member
0 Kudos

Chandra

Can you ping the ODB server with short name and FQDN?

Also, try nslookup on the ODB server.

Hope this helps!

PJ