cancel
Showing results for 
Search instead for 
Did you mean: 

Jco Error after sso

Former Member
0 Kudos

HI all,

We have configured sso between portal  , the jco's were working fine. After configuring sso between  a new EREC system  and the existing portal sytem, the jco's keep failing.

Service and host entries are maintained in both servers,

Connection parameters are maintained properly.

but the following error occurs: the jco's point to the existing HR system,

com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connection parameters: TYPE=B DEST=<Java Rfc client> MSHOST=smcides R3NAME=DEV GROUP=SPACE PCS=1 LOCATION    CPIC (TCP/IP) on local host with Unicode ERROR       partner '127.0.0.1:SAPGW00' not reached TIME        Mon Jun 02 02:24:47 2014 RELEASE     721 COMPONENT   NI (network interface) VERSION     40 RC          -10 MODULE      nixxi.cpp LINE        3285 DETAIL      NiPConnect2: 127.0.0.1:3300 SYSTEM CALL connect ERRNO       10061 ERRNO TEXT  WSAECONNREFUSED: Connection refused COUNTER     11



Kindly help


Thanks,


Aishwarya



Accepted Solutions (0)

Answers (3)

Answers (3)

0 Kudos

Check you hosts file. I think there's something wrong:

'127.0.0.1:SAPGW00' not reached


Your Enterprise Portal and ABAP Server are on the same machine?

Former Member
0 Kudos

Hi Rodrigo Kruger,

127.0.0.1 was maintained as local host before in host entry but i have  removed that.

Still its showing this.


Sriram2009
Active Contributor
0 Kudos

Hi

Kindly refer the SAP Note

1147336 - JCo sizing for Web Channel/E-Commerce/Internet Sales


On local host file you have to retain the enter 127.0.0.1 as local loop-back adapter and also you can define the portal server ip to FQDN name

for example

  Portal server name = ABCDEF

On local host file

    127.0.0.1       Localhost

    10.10.10.1     ABCDEF

    10.10.10.1     ABCDEF.Domain name.com


BR

SS

Former Member
0 Kudos

Hello Sriram,

The issue is in sandbox system and there are not much connection,

What does 10.10.10.1 denote here. Could you please explain for what we are adding this in the host file?

Thanks,

Aishwarya.

Sriram2009
Active Contributor
0 Kudos

Hi

10.10.10.1 is example IP address for Portal server name = ABCDEF

BR

SS

Former Member
0 Kudos

Hi,

I have the host entry

192.XX.XX.XX  hostname.domain.com

maintained in both the servers , but still the error persists.

Thanks,

Aishwarya

anil_kumar259
Active Contributor
0 Kudos

Did you check the Group = "SPACE " is present ??

Even i have faced the same problem with the group name.Once the group is added into backend using T-code "SMLG" its worked for me.

Regards,

Anil

Former Member
0 Kudos

Hi Anil,

I Have checked and the group SPACE is there in the backend.

Thanks,

Aishwarya.

Sriram2009
Active Contributor
0 Kudos

Hi

Are you using SAP Gateway server? or internal one? is this portal system dual stack?

Could you check the SLD/LMDB ?

BR

SS

Former Member
0 Kudos

Hello Sriram,

We are using the internal gateway , not a separate gateway, And the portal is 7.3 ehp 1 java stack.

In SLD the backend system is available.The Jco's were working fine before .

Thanks,

Aishwarya.

Former Member
0 Kudos

Hello

1) Configuration issue. The IP address or the port is incorrect.
2) The gateway on localhost with instance number 00 is not running.

3) Please check if you can reach the gateway from the operating system your j2ee engine is running on.

telnet <host of  EREC> sapgw00
telnet <host of  EREC> sapgw01

Which one of the above works?

Check in the transaction SMGW  - goto parameters display - then you will see the parameters configured on your gateway host.

Cheers,

Tapan

Former Member
0 Kudos

HI Tapan Goyal,

I have checked the configurations and also the parameters. how to check the gateway on local host is running or not ???

Former Member
0 Kudos

Hi Aishwarya,

Have you pinged and tested the  JCo's.

If yes what all are the values there and check whether its correct or not?

May be in JCo'c you have mention the uid/pwd.. Please mention the logon ticket instead of uid/pwd.

And also please check the host entry once.

Former Member
0 Kudos

Hi nitin,

I have checked everything. I was working fine before . All parameters are maintained properly and host and service entries are in both the servers.

Thanks,

Aishwarya.