Skip to Content

SAPRouter Error

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.

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

4 Answers

  • Best Answer
    Jul 12, 2018 at 07:19 AM

    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

    Add comment
    10|10000 characters needed characters exceeded

  • Jul 09, 2018 at 03:02 PM

    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?

    Add comment
    10|10000 characters needed characters exceeded

    • 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

  • Jul 09, 2018 at 03:03 PM

    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

    Add comment
    10|10000 characters needed characters exceeded

    • 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.

  • Jul 18, 2018 at 09:54 PM

    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.

    Add comment
    10|10000 characters needed characters exceeded