JCo Error

[Former Member]

Hi

I have configured SLD.

But on creating JCO's, i get following error.

com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=B MSHOST=epnetweaver GROUP=PUBLIC R3NAME=CE6 MSSERV=sapmsCE6 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '127.0.0.1:sapgw01' not reached TIME Fri Oct 10 11:22:08 2008 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

Ne ideas, how to rectify it?

Thanks....

[Former Member]

goto backend

open trasction RZ70

give host name

activate current configuration

then check rfc is ping or not

if yes check in SLD , u will get technical system name (auto)

n create JCO from technical system name

if not

open file server "server" is file name

on os level of backend server

add ur server name their and check it

if not

then check VA values for RFC

[Former Member]

Hi Nishant,

Thank you for you're quick response.

just to clarify. when you say backend do you mean the R/3 server im connecting to through portals?

I've checked it and basically there was a SLD bridge. defined for host which we werent using. I removed it and loaded the same config with one of the systems where the JCO connection works for.

I still cannot connect to it though.

Also how do you restart SLD? i basically went to SLD administration and stopped and started the server. is that what i need to do?

The file "server" whats the exact location of it on the R/3 side? i searched for it but got a few files with the name.

funny thing is that this was working fine until one day it just stopped working. very strange.

thanks again for you're response.

dilanke

[Former Member]

yes backend means R/3 (system that you want to connect with Portal)

goto rz70

give hostname -->

service --> sapgw00 (sapgw(instance number)

execute it

click on yes

check rfc call (success or failed)

if it is success then technical system name will be in sld

to restart sld --> /sld --> administration --> stop server --> restart server

or check in VA --> SLD data supplier value --> Runtime

Services file is locted on OS level of R3 system--> Goto --> Start --> Run -> (type)Drivers(enter) --> etc -> (here is services file)

check ur r/3 server entry is there or not,

if not add it

check message by Kanthiah Gomath...

if yet it not solve, paste error

Edited by: nishant kale on Jan 21, 2009 11:49 PM

[Former Member]

Hi nishant,

I have opened a new thread for this with answers to you're previous queries. please see below link

Link: [;

thanks,

dilanke

[Former Member]

Hi sorry wrong link.

[;

[Former Member]

Hi all

Making entry in services and host file of R/3 Server also

&

Restarting the R/3 server once..

Solved the problem...

This is the solution for this error...

Thanks...all...

Regards..

Chetna

[Former Member]

Hi Chetna,

I have the same issue as you did. however my JCO destinations were working perfectly until recently. I checked on the logon group. I have one called CLUST, which i use for this purpose.

I have also checked both service files and they have the following for the ECC server im connecting to.

3610 because its system number 10 i am connecting to.

sapmsDMI 3610/tcp

From the JCE destinations scren i cannot even ping the server. I can though when i log on to the server through remote desktop.

not too sure exactly whats going on would appreciata any help you can give me.

thanks and regards

dilanke

[Former Member]

Chetna,

Unicode ERROR partner '127.0.0.1:sapgw01' not reached 

This means either you are backend systems ip adddress is not 127.0.0.1 which has to be changed in the JCO by clicking on edit.

Or make sure that your backend system is up in running.

Or try pinging from your system, ping 127.0.0.1 and see if you are able to ping.

Good Luck.

Sandeep Tudumu

[Former Member]

Hi Sandeep

Thanks for reply..

*As confirmed from Basis ppl, This (127.0.0.1) is Domain Name Server of the Hostname what i have put while SLD configuration.

*Backend system is up in running.

*Ping is successful too.

Thanks...

[Former Member]

Hi,

Go to transaction smlg in ECC system and check whether any logon group is defined. If there is no group, create a logon group named PUBLIC.

Regards

Deb

[Former Member]

Hi

Group named Public is defined..

Thanks..

[Former Member]

Check if portal serveru2019s service file is added with following line :

 sapmsCE6      3600/tcp        # SAP System Message Port 

Check with SAP Basis for SAP's system message port in place of 3600