Receiving Error Data for "Data for alien client" dev_disp trace file

[Former Member]

Hi,

Since our upgrade to ECC 6.0 and Unicode conversion we are receiving the following error message in the dev_disp trace file. The message is consistently logged every 10 minutes. We, along with SAP, cannot find where it is coming from. If anyone can help, it is appreciated. Please let me know if you require additional information.

Mon Dec 8 17:07:00 2008

• ERROR => DpRGetLogin: Data for alien client [dpxxdisp.c 11409]

Connect request from wrong client at address 127.0.0.1(localhost)

Thanks,

Domenick

[Former Member]

Hi Domenick,

I have the same issue.. can you please share the solution of this with us.

Thanks

[former_member189725]

Please ensure that in the /etc/services file the following entry exists

sapgw<instance_no>     33<instance_no>/tcp

and also the port 33<instance_no> is not used in the services file elsewhere.

Regards

Ratnajit

[Former Member]

yes it does have the /etc/services gw entries.

Also, just to give you background.. I am in process of upgrading our system from NW7.01 to NW7.3 through SUM. In Execution step, as soon as SUM started Execution phase it stop SAP and tweeks the profiles as per the NWugpr process needs. And after those profiles changes it tries to start the system back.. so after that my system is running very slow.. and giving the below errors repeatedly.

Also, right now its on MAIN_SWITH/JOB_BTCTRNS1 phase and running for almost 7-8 hours.. no change..

Log file Dev_disp:

Mon Sep  3 02:03:55 2012

*** ERROR => DpRGetLogin: Data for alien client [dpxxdisp.c   12039]

DpRTmPrepareReq: connect request from wrong client at address 127.0.0.1(localhost)

Mon Sep  3 02:04:00 2012

*** ERROR => DpRGetLogin: Data for alien client [dpxxdisp.c   12039]

DpRTmPrepareReq: connect request from wrong client at address 127.0.0.1(localhost)

Log file Dev_w0:

M Mon Sep  3 17:20:44 2012

M  ***LOG Q0I=> NiPConnect: 10.108.4.150:50119: connect (239: Connection refused) [nixxi.cpp 2897]

M  *** ERROR => NiPConnect: SiConnect failed for hdl 2/sock 16

    (SI_ECONN_REFUSE/239; I4; ST; 10.108.4.150:50119) [nixxi.cpp    2897]

M  {root-id=3E48B1BEE2301EE1BDC160B2E0675D00}_{conn-id=00000000000000000000000000000000}_0

M  *** ERROR => EncNiConnect: unable to connect (NIECONN_REFUSED) [encomi.c     446]

M  {root-id=3E48B1BEE2301EE1BDC160B2E0675D00}_{conn-id=00000000000000000000000000000000}_0

[Former Member]

I am facing the same issue.

Can you please tell me if this issue was fixed and what was the fix?

[Former Member]

Yes our issue is resolved. Are you performing NW upgrade as well.. and have issue in same phase..?

[Former Member]

Hi,

Yes . I am doing an NW upgarde too using SUM ..

I am currently at the phase MAIN_SWITCH/SETUPGPAR_UPG_DOWN .

dev_disp

ERROR => DpRGetLogin: Data for alien client

DpRTmPrepareReq: connect request from wrong client at address <ip> localhost

dev_w0 - log

***LOG Q0I=> NiPConnect: 162.53.32.111:50019: connect (79: Connection refused) [nixxi.cpp 2898]

M  *** ERROR => NiPConnect: SiConnect failed for hdl 13/sock 13

    (SI_ECONN_REFUSE/79; I4; ST; :50019) [nixxi.cpp    2898]

M  {root-id=50620778E54616D0E1008000A235206F}_{conn-id=00000000000000000000000000000000}_0

[Former Member]

Could you please tell me what was the fix in your case ?

[Former Member]

OK... here's the solution.. in the instance profile make changes as mentioned below.. and restart the SAP.

Comment out these parameters  in instance profile..

#enque/serverhost = xxxxxxx

#enque/serverinst = 00

#enque/encni/port = 5xx19

#enque/process_location = REMOTESA

And uncomment the below one..

rdisp/wp_no_enq = 1

After this restart SAP.

Let me know if this solves your issue.. and don't forget to give me points.

[Former Member]

looks like SUM itself was updated the parameter .

I have commented those parameters and uncommented rdisp/wp_no_enq = 1 .

Issue has been fixed .

Thanks for the help

I will award the points .

[Former Member]

Hi,

Please attach the full dev_disp trace file and SM21 log

Cheers!

Edited by: Warren Wong on Dec 9, 2008 4:50 PM

[Former Member]

Thanks Warren!

Here is a piece of the trace file. It is too large to include entire trace file.

Wed Dec 10 08:37:01 2008

• ERROR => DpRGetLogin: Data for alien client [dpxxdisp.c 11409]

Connect request from wrong client at address 127.0.0.1(localhost)

Wed Dec 10 08:47:01 2008

• ERROR => DpRGetLogin: Data for alien client [dpxxdisp.c 11409]

Connect request from wrong client at address 127.0.0.1(localhost)

Wed Dec 10 08:57:00 2008

• ERROR => DpRGetLogin: Data for alien client [dpxxdisp.c 11409]

Connect request from wrong client at address 127.0.0.1(localhost)

Wed Dec 10 09:07:00 2008

• ERROR => DpRGetLogin: Data for alien client [dpxxdisp.c 11409]

Connect request from wrong client at address 127.0.0.1(localhost)

Wed Dec 10 09:17:00 2008

• ERROR => DpRGetLogin: Data for alien client [dpxxdisp.c 11409]

Connect request from wrong client at address 127.0.0.1(localhost)

Wed Dec 10 09:27:00 2008

• ERROR => DpRGetLogin: Data for alien client [dpxxdisp.c 11409]

Connect request from wrong client at address 127.0.0.1(localhost)

Wed Dec 10 09:37:00 2008

• ERROR => DpRGetLogin: Data for alien client [dpxxdisp.c 11409]

Connect request from wrong client at address 127.0.0.1(localhost)

Wed Dec 10 09:47:00 2008

• ERROR => DpRGetLogin: Data for alien client [dpxxdisp.c 11409]

Connect request from wrong client at address 127.0.0.1(localhost)

Wed Dec 10 09:57:00 2008

• ERROR => DpRGetLogin: Data for alien client [dpxxdisp.c 11409]

Connect request from wrong client at address 127.0.0.1(localhost)

Wed Dec 10 10:07:00 2008

• ERROR => DpRGetLogin: Data for alien client [dpxxdisp.c 11409]

Connect request from wrong client at address 127.0.0.1(localhost)

Wed Dec 10 10:17:01 2008

• ERROR => DpRGetLogin: Data for alien client [dpxxdisp.c 11409]

Connect request from wrong client at address 127.0.0.1(localhost)

The only entry during this time in the system log is:

10:24:13 DIA 015 030 KMOTURI R4 7 Delete session 001 after error 061

Please let me know if I can give any more information.

Thanks,

Domenick

[Former Member]

Hi,

What SAP kernel patch level are you on?

This is an information telling you that a user session is deleted from system. It could also happene If someone with enough permissions for the SM04 transaction deletes a session of a user. Also check if your network settings and connections are ok.

Cheers

[Former Member]

Warren,

Here is our kernel info. Release 700 Patch 146. I will again take a look at other port settings.

Thanks!

Domenick