SAPRouter Error

[former_member573062]

Hi All,

my dev clients don't connect with saprouter, when vi the tracefile in saprouter, this have this error:

Mon Jul 9 08:19:30 2018 ***LOG Q0I=> NiPConnect2: 192.168.1.215:3200: connect (79: Connection refused) [/bas/745_REL/src/base/ni/nixxi.cpp 3377] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 467/sock 63

my solution of SAP if installed in AIX environment.

Sorry for my bad English.

[raquel_gomez · Accepted solution]

Hi Jose Luis,

Error shown:
Mon Jul 9 08:19:30 2018
***LOG Q0I=> NiPConnect2: 192.168.1.215:3200: connect (79: Connection refused) [/bas/745_REL/src/base/ni/nixxi.cpp 3377]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 467/sock 63

Points to a disconnection to the Dispatcher form application server running on host 192.168.1.215, instance number 00.
Is application server up? Check Dispatcher tace file (dev_disp), that should be located \usr\sap\<SID>\<INSTANCE_00>\work.

You can also check application server status running at OS level command:
sapcontrol -nr 00 -function GetProcessList

Regards,
Raquel

[BJarkowski]

SAProuter throws the error because it can't connect to 192.168.1.215 on port 3200.

I would recommend to check:

a) what is the SAP instance number on host 192.168.1.215

b) is the SAP instance up and running correctly?

c) are there any firewall ports blocked?

[former_member573062]

a) The instance number is 00 and 01

b) The log of sap no have errors

c) The firewall don't have ports blocked

When run netstat -a -n the port 3200 don't have, but the port 3201 is established

[BJarkowski]

Hi,

what is the instance 00? Is it ASCS or Dialog instance?

In SAP GUI you need to provide the Dialog instance (not ASCS). Did you try to change the instance number to 01 in GUI?

[former_member573062]

In the SAP GUI the instance is 00 assuming is Dialog instance. When change de instance number to 01 in the GUI and try to connect the GUI send me this error

[BJarkowski]

Looks like your dialog instance is shutdown. Please verify that - there is a lot info in the internet.

[isaias_freitas]

Hello Jose,

Have you solved the issue? Can we still assist you?

The error suggests that either the incorrect IP/port is used, that there is a firewall blocking the connection, or that SAP is not running (the 3 items suggested by Bartosz).

If the issue was solved, please update the question with the solution and close the question, selecting the best answer :).

Thanks and regards,

Isaías

[former_member573062]

Hello friends

Thanks for your supports. I solved the problem.

I check the trace file disp_w0 in the path that Raquel Gomez say. The error that the file(disp_w0) show is the saptemp is too fully.

I execute the command "dump transaction ERP with no_log", with the isql64(Sybase) interface in AIX, then execute starsap command and I already connect to the instance.

Thanks for your help. Peace.

MJ.

[former_member108703]

Hello Jose,

Could You check the message server state? Is it started?

Check the message server log file (dev_ms) in the SCS work directory and the System Log entries using SM21 if any errors appear.

Regards,

Zoltan

[former_member573062]

What is the path of the message server log?. How to check if message server is started?

I new to basis.

[former_member108703]

The SCS work directory can be found at this location:

"LocalDrive\usr\sap\<SID>\SCS<XX>\work"

In this directory the message server log is the dev_ms file.

The following entries indicates that the message server is started and listening the internal and external ports.

"*** I listen to internal port 3950 (3950)"

"*** HTTP port 8150 state LISTEN ***"

"Server state ACTIVE"

You can check the state of the message server in the SAP Management Console: select the SCS instance and check the status of msg_server.EXE.