Communication error, CPIC return code 027, SAP return code 4

[Former Member]

our SAP environment: R/3 4.6C, Oracle 9206, HP-UX 11.23.

We installed an additional application server. After the installation, in

the log of SM21, we have the following error:

17:23:55 DIA 00 288 LI_L R49 Communication error, CPIC

return code 027, SAP return code 456

17:23:55 DIA 00 288 LI_L R64 > CPI-C function: CMINIT(SAP)

Operating system call getsockname failed (error no. 22 )

I;'ve done the following:

1. I've run "test connection" in SM59. They are OK.

2. I've run SMGW -> goto -> Logged on client, it shows logged on RFC clients are OK with a normal state.

I read the dev_rd files but did not have a clue yet. Will you please help me out? Pls see below for the content of dev_rd files.

Below is the dev_rd from the app server:

trc file: "dev_rd", trc level: 1, release: "46D"

Thu Mar 29 14:03:22 2007

***LOG S00=> GwInitReader, gateway started ( 25049) [gwxxrd.c 1567]

relno 4640

patchlevel 0

patchno 2197

intno 0

pid 25049

CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.

CCMS: Initalizing shared memory of size 10000000 for monitoring segment.

Bind service sapgw02 to datagramm port 3302

Bind service sapgw02 (normal) to port 3302

GwPrintMyHostAddr: my host addresses are :

1 : [18.0.0.9] cheyenne

2 : [127.0.0.1] localhost

3 : [172.20.200.30] cheyenne-1

MtxInit: -2 0 0

Thu Mar 29 14:25:15 2007

***LOG Q0I=> NiStreamDflt: getsockname (22: Invalid argument) [niuxi.c 730]

Thu Mar 29 14:28:52 2007

***LOG Q0I=> NiStreamDflt: getsockname (22: Invalid argument) [niuxi.c 730]

Thu Mar 29 14:29:00 2007

***LOG Q0I=> NiStreamDflt: getsockname (22: Invalid argument) [niuxi.c 730]

Thu Mar 29 14:33:52 2007

***LOG Q0I=> NiStreamDflt: getsockname (22: Invalid argument) [niuxi.c 730]

Thu Mar 29 14:41:09 2007

***LOG Q0I=> NiStreamDflt: getsockname (22: Invalid argument) [niuxi.c 730]

Fri Mar 30 11:36:41 2007

***LOG Q0I=> NiStreamDflt: getsockname (22: Invalid argument) [niuxi.c 730]

Fri Mar 30 11:36:44 2007

***LOG Q0I=> NiStreamDflt: getsockname (22: Invalid argument) [niuxi.c 730]

Fri Mar 30 13:25:21 2007

***LOG Q0I=> NiStreamDflt: getsockname (22: Invalid argument) [niuxi.c 730]

Below is the dev_rd from the CI:

trc file: "dev_rd", trc level: 1, release:

Wed Mar 28 16:09:02 2007

***LOG S00=> GwInitReader, gateway started

relno 4640

patchlevel 0

patchno 2197

intno 0

pid 280

CCMS: AlInitGlobals : alert/use_sema_lock

CCMS: Initalizing shared memory of size 10

Bind service sapgw00 to datagramm port 330

Bind service sapgw00 (normal) to port 3300

GwPrintMyHostAddr: my host addresses are :

1 : [18.0.0.3] saadb

2 : [127.0.0.1] localhost

3 : [172.20.200.23] saadb-1

4 : [10.1.1.1] apache-hb

5 : [18.0.0.1] apache

6 : [172.20.200.20] apache-1

MtxInit: -2 0 0

..........

Fri Mar 30 14:59:27 2007

• ERROR => R3ISearchPartner: timeout, partner LU: >%%SAPGUI%%<, TP: >$SAPGUI\SAPF1H32\F1SRV32X.EXE< [gwr3cpic.c 5733]

• ERROR => R3ISearchPartner: HOST: %%SAPGUI%%, conv ID: 85196130 [gwr3cpic.c 5745]

Fri Mar 30 15:47:55 2007

***LOG Q0I=> NiStreamDflt: getsockname (22: Invalid argument) [niuxi.c 730]

Please share your opinion on this problem, Thanks!

[Former Member]

Hello Allforone,

One simple suggestion. May be you would have done it already. But make sure that you have maintained an entry for dialog instance in CI host file (just the host file) and a similaar one for CI in the DI host file.

Regards.

Ruchit.

[Former Member]

Hi! Ruchit:

Yes, I verified that we have the needed entries in the hosts file on both server. thanks.

[Former Member]

Hi,

Can you do a successful test connection for TCp/IP RFC destination SAPGUI in SM59?

Regards.

Ruchit.

[Former Member]

Yes, that's the very first few things I did in the beginning. I stated this in the original message. thanks.

[Former Member]

Hi, all:

Can somebody help me with this problem? Thank a lot!!

[Former Member]

Hello Allforone,

Just check how is SM51 behaving. I mean are you able to do cross instance login using SM51.

Regards.

Ruchit.

[Former Member]

Hi! Ruchit Khushu :

Thanks for the reply.

Yes, I've tried cross instance login using SM51and it is good.

[Former Member]

Your log shows two different gateways, in one case SAPGW02 and in another SAPGW00.

check to wee that both servers have the same gateway.

Also check to see that the hosts file has the proper SAP entries on both systems.

Hope this helps a little as you troubleshoot further.

[Former Member]

Thanks for the answer.

In the hosts and service file of all servers, we have the needed entries such as sapdp00/sapdp01/sapdp02/sapgw00/sapgw01/sapgw02.

D02 is the newly installed dialog instance server.

D01 and DEVBMGS00 are the original dia instance and the CI.

So we have gateway sapgw00 for CI and sapgw02 for the new dialog instance, I think these setting are OK, right?

[Former Member]

could you please have a look to Note 677552 - ***LOG Q0I=> NiStreamDflt: getsockname (22: Invalid argument

Cheers,

-Sunil

[Former Member]

Hi, Sunil Bujade :

Yes, I've read this note before. It says this error is due to gateway opening a closed connection and this bug will be fixed in the new kernel thus can be ignored for now.

The odd thing is that we only started to have this error after the dialog instance installation. And we've keep kernels on all server synchronized.