SAP router connection.

Hi,
   I wanted to know how do we know 'saprouter' is configured on solution manager 4.0 and if it is how can we get the password for it.
  Thank You.

Dear
You can check by following option
1. where u have installed the saprouter you have to type command saprouter -s,saprouter -l
2.go to sm59 choose the oss RFC then test
shailesh

Similar Messages

  • SAP Router connection configuration

    Dear experts
    Out SAP router is currently using VPN connection to SAP. Due to some migration task, I need to reinstall this router now and would like to ask you what security type is currently "state of the art", also keeping in mind, that I would use our Solution Manager to keep track of service connections between us an SAP.
    Should we now change to SNC or keep VPN as security provider?
    Thank you for any hints.
    Best regards, Michael

    In your SLD configuration,  what do you have as your Logon Group under the message server config.  Is it "PUBLIC".  if so, then the user id needs to belong to that Logon Group in the system.
    Regards,
    Rich Heilman

  • SAP router connection is not working

    Dear Experts,
    I cannot connect my systems to SAP, getting the below error.My router is not expired and port 3299 is reachable.
    SAPRouter "dev_rout" log as follows:
    trc file: "dev_rout", trc level: 1, release: "720"
    Wed Apr 09 15:55:51 2014
    SAP Network Interface Router, Version 40.4
    command line arg 0:    C:\saprouter\saprouter.exe
    command line arg 1:    -r
    command line arg 2:    -W
    command line arg 3:    60000
    command line arg 4:    -R
    command line arg 5:    C:\saprouter\saprouttab
    command line arg 6:    -K
    command line arg 7:    p: CN=SOLMAR, OU=0000881026, OU=SAProuter, O=SAP, C=DE
    SncInit(): Initializing Secure Network Communication (SNC)
          PC with Windows NT (mt,ascii,SAP_UC/size_t/void* = 8/64/64)
          GetUserName()="Administrator"  NetWkstaUser="Administrator"
    SncInit(): Trying environment variable SNC_LIB as a
          gssapi library name: "C:\saprouter\nt-x86_64\sapcrypto.dll".
      File "C:\saprouter\nt-x86_64\sapcrypto.dll" dynamically loaded as GSS-API v2 library.
      SECUDIR="C:\saprouter\" (from $SECUDIR)
      The internal Adapter for the loaded GSS-API mechanism identifies as:
      Internal SNC-Adapter (Rev 1.0) to SAPCRYPTOLIB
      Product Version = SAPCRYPTOLIB  5.5.5C pl36  (Jul  3 2013) MT,[aesni],NB
    main: pid = 3656, ppid = 0, port = 3299, parent port = 0 (0 = parent is not a saprouter)
    reading routtab: 'C:\saprouter\saprouttab'
    Wed Apr 09 16:00:49 2014
    NiHLGetHostName: to get 192.168.4.69 succeeded in 4660ms (tl=2000ms)
    Wed Apr 09 16:00:50 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 380
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Wed Apr 09 16:03:12 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 380
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Wed Apr 09 16:03:13 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 380
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Wed Apr 09 16:03:24 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 20/sock 380
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Wed Apr 09 16:03:25 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 21/sock 380
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Wed Apr 09 16:03:27 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 22/sock 380
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Wed Apr 09 16:08:16 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 380
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Wed Apr 09 16:11:42 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 380
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Wed Apr 09 16:20:05 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 360
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Wed Apr 09 18:20:07 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 380
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Wed Apr 09 18:20:08 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 380
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Wed Apr 09 18:28:05 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 384
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Wed Apr 09 18:28:06 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 384
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 384
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Wed Apr 09 18:53:05 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 20/sock 372
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Wed Apr 09 18:53:06 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 21/sock 372
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Wed Apr 09 18:53:07 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 22/sock 372
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Wed Apr 09 18:53:10 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 372
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Wed Apr 09 18:53:11 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 372
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Wed Apr 09 18:53:12 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 372
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Wed Apr 09 19:20:05 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 380
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Wed Apr 09 19:20:06 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 380
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Wed Apr 09 19:20:07 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 20/sock 380
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Wed Apr 09 19:28:05 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 21/sock 384
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Wed Apr 09 19:28:06 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 22/sock 384
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Wed Apr 09 19:28:07 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 384
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Wed Apr 09 20:20:05 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 360
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Wed Apr 09 20:20:06 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 360
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Wed Apr 09 20:20:07 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 360
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Wed Apr 09 20:28:04 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 380
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Wed Apr 09 20:28:05 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 20/sock 380
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Wed Apr 09 20:28:06 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 21/sock 380
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Wed Apr 09 21:20:05 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 22/sock 384
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Wed Apr 09 21:20:06 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 384
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Wed Apr 09 21:20:07 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 384
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Wed Apr 09 21:28:05 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 360
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Wed Apr 09 21:28:06 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 360
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Wed Apr 09 21:28:07 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 360
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Wed Apr 09 21:55:05 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 20/sock 380
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Wed Apr 09 22:20:06 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 21/sock 384
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Wed Apr 09 22:20:07 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 22/sock 384
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Wed Apr 09 22:20:08 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 384
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Wed Apr 09 22:28:05 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 360
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Wed Apr 09 22:28:06 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 360
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Wed Apr 09 22:28:07 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 360
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Wed Apr 09 23:20:06 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 380
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Wed Apr 09 23:20:07 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 20/sock 380
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Wed Apr 09 23:20:08 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 21/sock 380
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Wed Apr 09 23:28:05 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 22/sock 384
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Wed Apr 09 23:28:06 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 384
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Wed Apr 09 23:28:07 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 384
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Thu Apr 10 00:20:05 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 360
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Thu Apr 10 00:20:06 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 360
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Thu Apr 10 00:20:07 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 360
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Thu Apr 10 00:28:05 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 20/sock 380
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Thu Apr 10 00:28:06 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 21/sock 380
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Thu Apr 10 00:28:07 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 22/sock 380
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Thu Apr 10 01:20:05 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 384
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Thu Apr 10 01:20:06 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 384
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Thu Apr 10 01:20:07 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 384
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Thu Apr 10 01:28:05 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 360
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Thu Apr 10 01:28:06 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 360
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Thu Apr 10 01:28:07 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 20/sock 360
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Thu Apr 10 02:20:05 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 21/sock 380
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Thu Apr 10 02:20:06 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 22/sock 380
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Thu Apr 10 02:20:07 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 380
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Thu Apr 10 02:28:05 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 384
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Thu Apr 10 02:28:06 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 384
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Thu Apr 10 02:28:07 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 384
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Thu Apr 10 03:20:05 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 360
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Thu Apr 10 03:20:06 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 20/sock 360
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Thu Apr 10 03:20:07 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 21/sock 360
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Thu Apr 10 03:28:05 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 22/sock 380
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Thu Apr 10 03:28:06 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 380
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Thu Apr 10 03:28:07 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 380
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Thu Apr 10 04:20:05 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 384
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Thu Apr 10 04:20:06 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 384
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Thu Apr 10 04:20:07 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 384
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Thu Apr 10 04:28:05 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 20/sock 360
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Thu Apr 10 04:28:06 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 21/sock 360
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 22/sock 360
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Thu Apr 10 05:20:05 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 380
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Thu Apr 10 05:20:06 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 380
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Thu Apr 10 05:20:07 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 380
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Thu Apr 10 05:28:05 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 384
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Thu Apr 10 05:28:06 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 384
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Thu Apr 10 06:20:07 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 360
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Thu Apr 10 06:28:05 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 380
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Thu Apr 10 08:20:07 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 384
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Thu Apr 10 08:20:08 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 384
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Thu Apr 10 08:28:05 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 360
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Thu Apr 10 08:28:06 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 20/sock 360
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Thu Apr 10 08:28:07 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 21/sock 360
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Thu Apr 10 08:56:37 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 22/sock 380
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Thu Apr 10 08:56:38 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 380
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Thu Apr 10 08:56:39 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 380
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    Thu Apr 10 08:58:15 2014
    ***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
    *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 380
        (SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp    3283]
    SAPRoutab:
    P * * *   
    P 192.168.0.96 194.117.106.129 3299
    P 192.168.0.96 194.117.106.129 *
    # SNC-connection from and to SAP
    #KT "p:CN=sapserv1, OU=SAProuter, O=SAP, C=DE" 194.117.106.129 *
    # SNC-connection from SAP to local R/3-System for Support
    #KP "p:CN=sapserv1, OU=SAProuter, O=SAP, C=DE" 192.168.* 32*
    P    *    194.117.106.129    *
    P 127.0.0.1 194.117.106.129 3299
    P    *    *    *
    P    sapserv1    192.168.0.165    3389
    P    sapserv1    192.168.0.96    3389
    P    sapserv1    192.168.0.162    3389
    SAPOSS Screens:

    Hi Philip
    This looks fine. Just click on change and save again , it will automatically create SAPOSS RFC, u  can see that in  TX; SM59,
    seems you Public IP : 192.168.0.96
    The entry that you maintained in the sapsouttab was:
    KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 192.168.0.96, 3200
    you supposed to maintain the IP Address of the server that you opening the connection.not the router IP(192.168.0.96,)
    make sure it looks like the below:
    KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" <IP Address of the server that you working with RFC>, 3200
    Please follow this:
    1.Maintain then  correct entries in the saprouttab
    2.restart the saprouter
    3.Delete RFC: SAPOSS from TX:SM59
    4. Recreate the RFC: SAPOSS from OSS1 after  deleting that from SM59..
    5.Go to TX: SM59 and open the RFC:SAPOSS and  go to technical setting tab: and make sure that the string looks ok  and make sence(if requied copy the string frm the anotherserver where the RFC:SAPOSS is workingalready) and go to log on security tab and reenter the password of the user:OSS_RFC as CPIC (all in Capital letters)
    save it and test.
    please send me the screen shots of saproutab and  screen shot of the SAPOSS RFC from SM59 and error screen shot.
    hope it clarifies the now.
    Kind Regards,
    Phaneendra kakani

  • SAP  ROUTER CONNECTION STRING FOR SAP SERVERS

    Hi,
    I want to create saprouter string for accessing ecc6.0 server, router is given with one public ip and my server is in domain,help me in creating saprouter string.
    Thanks & Have a good day
    Naveen

    Hi Naveen,
    There are some SAP notes that can help you understand how to create such strings.
    The main idea is to create a string like this:
    /H/<ip address of your saprouter>/S/<service port of your saprouter>/H/
    Regards,
    Val

  • SAP Router connection  refused

    Hi SAPRouter-experts!
    <b>I have a problem to establish OSS1-connection, to ping sapserv3 (147.204.2.5) --> time out error, and to configure saprouter.</b>
    Here the developer trace from ST11
    RSTR0006 - Anzeige der Entwickler-Traces                                                                            
    1
    trc file: "dev_lg", trc level: 1, release: "700"
    [Thr 7656] Sun Jun 17 13:58:57 2007
    [Thr 7656] ***LOG Q0I=> NiPConnect2: connect (10061: WSAECONNREFUSED:
    Connection refused) [nixxi.cpp 2764]
    [Thr 7656] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 0 /
    sock 1876
         (SI_ECONN_REFUSE; I4; ST; 192.168.177.10:3299) [nixxi.cpp    2764]
    [Thr 7656] *** ERROR => MsIAttachEx: NiBufConnect to
    /H/192.168.177.10/S/sapdp99/H/192.168.147.101/S/sapdp99/H/147.204.2.5/S/sapdp99/H/oss001/S/sapmsO01/x
    failed (rc=NIECONN_REFUSED) [msxxi.c      6
    [Thr 7656] *** ERROR => LgIAttach: MsAttach (rc=NIECONN_REFUSED)
    [lgxx.c       3980]
    [Thr 7656] *** ERROR => LgApplSrvInfo: LgIAttach(rc=LGEMSLAYER) [lgxx.c      
    1272]
    [Thr 7656]
    [Thr 7656] *  ERROR       partner '192.168.177.10:sapdp99' not reached
    [Thr 7656] *
    TIME        Sun Jun 17 13:58:57 2007
    [Thr 7656] *  RELEASE     700
    [Thr 7656] *  COMPONENT   NI (network interface)
    [Thr 7656] *  VERSION     38
    [Thr 7656] *  RC          -10
    [Thr 7656] *  MODULE      nixxi.cpp
    [Thr 7656] *  LINE        2764
    [Thr 7656] *  DETAIL      NiPConnect2
    [Thr 7656] *  SYSTEM CALL connect
    [Thr 7656] *  ERRNO       10061
    [Thr 7656] *  ERRNO TEXT  WSAECONNREFUSED: Connection refused
    [Thr 7656] *  COUNTER     1
    [Thr 7656] *
    [Thr 7656]
    <b>Can you tell the procedure to fix all the prooblems?</b> Tnak you very much!
    regards

    Hi!
    Thank you!
    BUT, I am talking about the OSS1-issue in SOLMAN.
    Unfortunetaly I can not ping to sapserv3 or open ftp with sapserv3..
    I completly installed the latest version of Saprouter, installed the service in Windows, have run ltgt.exe...
    <b>How can I establish the connection with SAPRouter? Is there some Network limitations? </b>
    Thank you!

  • DBACOCKPIT Connection for SAP systems with SAP Router

    Hello!
    We are trying to integrate all the remote SAP systems and their databases (primarily Oracle) into DBACOCKPIT of SAP Solution Manager 7.1.
    Our SAP Solution Manager is running on Windows with Oracle 11.2.0.2
    The most SAP systems (Unix and Windows) can only be reached from SAP Solution Manger over the SAP Router connection.
    It means no direct ping from Solution Manager server to the Server of managed system will work.
    Question
    Is it possible to integrate such SAP systems (with SAP Router) into DBACOCKPIT of Solution Manager?
    According to sap note 1265134 only the DBCON-connection will be required.
    By doing so (tcode SOLMAN_SETUP), we get TNS errors.
    Do we miss some additional steps (adapting tnsnames.ora of SOLMAN with the entry of managed system), etc.?
    Thank you!
    regards

    SAP-SDN wrote:
    > We of course can reach these systems via SM59.
    >
    > The question still is whether or not the several SAP systems with Oracle that can be reached from Solution Manager over SAP Router can be integrated into DBACOCKPIT of SAP Solution Manager in order to gather/ analyze performance data?
    Systems can be reached via SM59, then what's the problem ?
    In fact, this 'is' the standard procedure. This is as normal as you could have Solution manager in same 'network' with rest of the remote systems.
    Answer should be yes, you can manage several remote sap systems from sap solution manager dbacockpit.
    Thanks

  • Is this possible: SNC connection from SAP GUI to SAP Router, and ...

    Hi,
    I have (stupid perhaps) question.
    Is this scenario possible:
    SNC connection from SAP GUI to SAP Router, and non-SNC connection from SAP Router to SAP System.
    I know how to set up scenario like this:
    SAP System --- (non-SNC conn) --- saprouter1 --- (SNC conn) --- saprouter2 --- (non-SNC conn) --- SAP GUI.
    Best regards,
    Marek Majchrowski

    Wolfgang,
    To be sure myself and Marek understand, can you confirm the different scenarios supported:
    Scenario 1:
    SAP GUI --- (non SNC conn) --- saprouter1 --- (SNC conn) --- saprouter2 --- (non-SNC conn) --- SAP System
    With this scenario, it would be possible for a user to logon using SAP GUI onto the SAP System, but without SAP GUI SNC.
    Scenario 2:
    SAP GUI --- (SNC conn) --- saprouter1 --- (non SNC conn) --- saprouter2 --- (SNC conn) --- SAP System
    With this scenario it would be possible to logon to the SAP System using SAP GUI, and using SNC authentication.
    Also, with this scenario the SAP GUI software and SAP System software would consider this to be similar to:
    SAP GUI -- (SNC conn) -- SAP System
    Scenario 3:
    This is the scenario mentioned by Marek in his initial question:
    SAP GUI -- (SNC conn) -- saprouter1 -- (non SNC conn) -- SAP System
    With this scenario it will not be possible to logon to SAP System using SNC, and only possible if the SAP GUI is configured to not use SNC. In other words the SNC connection between SAP GUI and saprouter1 is available, but cannot be used.
    Thanks,
    Tim
    Edited by: Tim Alsop on Feb 25, 2008 5:24 PM

  • Connection to R/3 with SAP Router

    Hello,
    I want a connecton from XI 3.0 to R/3 with SAP Router.
    But if i want to import the RFCs i become no connection.
    I Edit Software Component Version, but there is it not possible to set any Sap Router String.
    For Connection Data you can only set System, Client, Message Server and
    Group.
    I have also test to write the Router String before the Message Server IP without any sucess. Not enough Place to write the holfe Path in the Field.
    I become no connection to the R/3 to import the RFCs.
    Regards,
    Robin

    pls check correct port number..
    basis will give u this information. or u use tcode SCOT.

  • RFC connection between two SAP systems (with SAP router)

    Hi!
    I would like to set up a RFC-connection from SAP Solution Manager to other SAP system.
    The network connection between the servers is VPN.
    How can I set up this RFC-connection, if my connection between two SAP systems looks as follows,
    (I use the following SAP routers)?
    my server  --> customer
    my server --> internal SAP Router server xy (10.101....) --> SAP Router customer 2 (10.1....) --> SAP System customer (134....)
    Back-way
    SAP Systeme customer --> SAP Router customer (134.1....) --> internal SAP router (212.6....) --> my server
    How can I set up this RFC-connection, if my connection between two SAP systems looks as follows,
    (I use the following SAP routers)?
    something like:
    /H/10.101..../S/sapdp99/H/10.1.4..../S/sapdp99/H/134...
    Thank you very much!
    regards
    Thom

    Same answer as in the other forum where you cross posted....

  • Error while checking connection after establishing sap router

    Hello All,
    I have installed a sap router on our solution manager on Linux environment
    when i try to check the RFC connection from SM59 i am receiving the following error.
    my  message server is configured as follows
    Msg. Server - /H/<SAP Router Ip>/S/sapdp99/H/194.39.131.34/S/sapdp99/H/oss001
    <SAP Router> is my solman ip address
    Connection Test SAPOSS
    Logon     Connection Error
    Error Details     Error when opening an RFC connection
    Error Details     ERROR: timeout while pending for route completion
    Error Details     LOCATION: SAP-Server sgtr-s-devs1d_S1D_67 on host sgtr-s-devs1d (wp 0)
    Error Details     DETAIL: NiErrSet
    Error Details     COMPONENT: NI (network interface)
    Error Details     COUNTER: 175
    Error Details     MODULE:
    Error Details     LINE:
    Error Details     RETURN CODE: -12
    Error Details     SUBRC: 0
    Error Details     RELEASE: 700
    Error Details     TIME: Wed Feb 22 23:33:20 2012
    Error Details     VERSION: 38
    my oss1 tecnical settings are as follows.
    sap router at customer side
    Name          sgtr-s-devs1d
    IP Address    65.38.107.196
    Instance no.  99
    sap router at sap
    Name          sapserv2
    IP Address    194.39.131.34
    Instance no.  99
    when i do a logon i get the following error
    Unable to connect to SAPNet message server
    (Default connection will be used...)
    To check whether saprouter is working or not i  have executed few commands
    u2022     ps -ef|grep saprouter
    s1dadm    9873  9590  0 05:53 pts/2    00:00:00 saprouter -r -S 3299 -V 3 -K p:CN=sgtr-s-devs1d, OU=0000858034, OU=SAProuter, O=SAP, C=DE
    s1dadm    9951  9590  0 06:09 pts/2    00:00:00 grep saprouter
    u2022     lsof -w -n -i tcp:3299
    COMMAND    PID   USER   FD   TYPE  DEVICE SIZE/OFF NODE NAME
    saprouter 9873 s1dadm    4u  IPv4 5333574      0t0  TCP *:pdrncs (LISTEN)
    u2022     fuser -n tcp 3299
    3299/tcp:             9873
    u2022     netstat -anp|grep :3299
    tcp        0      0 0.0.0.0:3299            0.0.0.0:*               LISTEN      9873/saprouter
    In /usr/sap/saprouter
    my saprouttab contains
    SNC connection to and from SAP
    KT "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 194.39.131.34 *
    SNC-connection from SAP to local system for R/3-Support
    KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 65.38.107.196  3267
    Access from your local Network to SAP
    P 65.38.107.196 194.39.131.34 3299
    All other connections will be denied
    #D * * *
    one thing i want to know is my saprouter started or did i miss any configuration how to check whether my sap router is started.
    Please advice me if i miss any,
    Thanks in advance,
    Vardhan.

    Thanks for the quick reply.
    sgtr-s-devs1d:s1dadm > saprouter -r
    trcfile  dev_rout
    LOCATION    SAProuter 38.10 on 'sgtr-s-devs1d'
    ERROR       service '0.0.0.0:3299' in use
    TIME        Thu Feb 23 07:23:36 2012
    RELEASE     700
    COMPONENT   NI (network interface)
    VERSION     38
    RC          -4
    MODULE      nixxi.cpp
    LINE        3227
    DETAIL      NiIBindSocket
    SYSTEM CALL bind
    ERRNO       98
    ERRNO TEXT  Address already in use
    COUNTER     2
    looke like my sap router is on SAProuter 38.10
    already i have started  router earlier
    Thanks!
    Vardhan

  • Host did not respond error in connecting the SAP Router from SERVICE PLACE

    Dear Sir,
    We renew the Router Certificate by October 2008.  We are using broadband connection in our office with firewall (ISA) .
    When we try to connect the sap router from SAP Service Market Place, It is connected and after some time, status is changing to Host did not respond due to timeout.
    We checked the SAP Router Tab File also. It is correct.  Guide us to solve this issue
    With Regards
    K.Natarajan

    Hi
    This type of error occurs maximum,only when there is no proper connection between the systems.So,my suggestion is to check with the connection between the systems with the help of Basis person.
    regards
    krishna

  • Quality Server not connect through SAP Routing String

    Hi,
    When remotely access client SAP through SAP routing string in Quality Server it shows error message as
    "timeout occured
    Location : SAP router 37.11 on solman
    Time: Tue May 05 11:19:37 2009
    Component : NI (Network Interface)
    Release : 640
    Version : 37
    Return Code : -93
    Counter : 131 "
    Here GUI version is 7.1(where from connecting). Client SAP version is ECC 5.0 and they use GUI 6.4 version. But Development server is being connected through SAP Routing String.
    Regards,
    Samrat

    You might want to check following things:
    Can you do a ping to the IP address you specified?
    Is the data correct (ip, host, system number,...)?
    Is the gateway with system number 00 running on the server?
    Did you install the SAP RFC SDK dll's?
    Glenn Colpaert - MCTS BizTalk Server - Blog : http://blog.codit.eu

  • Connect EPM and web portal BPC through SAP router string

    Dear Expert,
    Please tell me how to connect EMP and web BPC through SAP router string?
    thanks so much
    hungth

    Hi hungth,
    Can you explain more? Do you mean you need a sap support to log on to your BPC web and investigate your BPC issues? If so, you can open HTTP connect connection by following note 592085.
    Best regards,
    Charlie

  • Sap Router not connecting

    When I check via SM59  to SAPOSS. It giving messege before 4 days It was working ,But Noe
    Sap Router giving Error
    Logon     Connection Error
    Error Details     Error when opening an RFC connection
    Error Details     ERROR: CPIC program connection ended (read error)
    Error Details     LOCATION: SAP-Server appkg_PRD_01 on host appkg (wp 0)
    Error Details     COMPONENT: CPIC
    Error Details     COUNTER: 4662
    Error Details     MODULE:
    Error Details     LINE:
    Error Details     RETURN CODE: 223
    Error Details     SUBRC: 0
    Error Details     RELEASE: 700
    Error Details     TIME: Thu Oct  9 09:21:22 2008
    Error Details     VERSION:
    What-2 option we should check.Where should be problem.
    Thanks manu

    Thanks rahul for your repply. I check in my Portel that SAP Router has been Expired.When I activate in service market place, what i should  give value in  " Insert the Certificate Signing Request "
    I am giving    SAProuter name : saprouter
                       Distinguinshed name: CN=saprouter, OU=0000870506, OU=SAProuter, O=SAP, C=DE
    Then continue  It give messege  "  Error - Applying for a certificate for SAProuter "
    What the value or Text will come in   "Insert the Certificate Signing Request "
    Thanks
    manu

  • SLD configuration - JCO connection with SAP Router

    Hi,
    I installed the new Sneak Preview SP11 Java Edition including SAP Portal. I tried to run an own Web Dynpro Application with RFC-Access on a R/3 System.
    Unfortunately I was not able to get the JCO Connection to run. The R/3 System is reached via SAP Router. I am a little bit confused, because with the last Sneak Preview (SP6 or SP7) this application was running without problems. Of course I thought that this can't be. So I uninstalled SP11 and installed the old version (SP7). I configured the JCO-connection, no problems.
    Now I know that this is not my mistake (hopefully ).
    If I configured a JCO-connection in SP11 and tried to PING, the first PING was ok. After testing the connection with user, the PING failed. The testing with user returns something like "user or password are not accepted".
    Any ideas?
    Best regards
    Renald

    In your SLD configuration,  what do you have as your Logon Group under the message server config.  Is it "PUBLIC".  if so, then the user id needs to belong to that Logon Group in the system.
    Regards,
    Rich Heilman

Maybe you are looking for

  • When are Apple going to sort out the Final Cut Pro X Key Frame problem

    Hello, I'm trying to move three custom text clips to different locations on the screen & change the text size. The text clips drift around between two key frames with the same values. ("linear" is set on the red wire frame movement indicator) I know

  • How to retain zoom position of an image using Adobe Flash Builder?

    Hi,   I have created an Adobe Flash Builder Mobile App. I placed an image in the Homeview. I allow the user to zoom out or zoom in the image using GestureZoom. The problem is each time the user zooms, it does not retain the previous position. For ex.

  • Java Memory Management/Out of Memory

    Hi Guys, I have a few questions about java memory management Because i keep encounter a lot of out of memory error which i think java does not handle Vector/ArrayList re initialisation automatically Asumme i have 2 million record in database and , i

  • Pricing conditions

    Pricing conditions In my pricing procedure 1. Sales revenue            100000 2. Fright                             500 (Accruals) 3. Insurance                     1000 (Accruals) 4. Other expanses              200 (Accruals) Total                   

  • Anyone know how Delta Links are stored in a Clustered environment?

    We have a situation where we have a clustered EP6 production environment with 4 servers in the load balancer. However, we've found that on just one of the servers the Delta Link between one of our roles and its only workset is missing. Wanted to know