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
Similar Messages
-
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
NaveenHi 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 -
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!
regardsHi!
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! -
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 -
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!
regardsSAP-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 -
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
RenaldIn 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 -
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 MajchrowskiWolfgang,
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 -
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 -
How to install and configure SAP Router
Dear SAP Expert !
I want to install SAP Router but i dont know the SAP router package is allocated on DVD ? what is the DVD number ?
If you already configure SAP router please let me know how to configure ?Hello Thao
what is th exact issue that are u facing.
The account must be the administartor of the machine where u are installing SAPROUTER.Make sure you are following the correct steps as follows:
Downloading necessary software components from SAP Service Marketplace
1. Login to the SAP Service Marketplace with the Service Marketplace at using
the USERID/PASSWORD which was assigned for your installation.
2. Change the alias to www.service.sap.com/tcs to downloaded the SAP
cryptographic software. Select the correct SAPcrptographic software
depending on your saprouter operating system as shown below.
3. You must have the sapcar.exe in order to extract the SAP cryptographic
software file.
4. With the command of u201Csapcar -xvf xxxxxxx.saru201D, /ntintel directory would be
created and the following files would be extracted.
(Example C:/saprouter/ntintel)
( when the Microsoft Windows NT Intel version is downloaded)
C:/saprouter/ntintel/sapcrypto.dll
C:/saprouter/ntintel/sapgenpse.exe
C:/saprouter/ticket
Issue of Electronic Certificate
5. It is necessary to define the environment variable for u201CSECUDIRu201D and
u201CSNC_LIBu201D under system account.
Window NT environment variable setup :
Right-clicked the icon of you computer
Property -> details -> environment variable
SECUDIR = < Directory name >
Example. Variable name : SECUDIR
Variable value
: C:/saprouter/SNC_LIB = < Directory name >
Example. Variable name : SNC_LIB
Variable value : C:/saprouter/ntintel/sapcrypto.dll
UNIX
<path_to_libsecude>/<name_of_sapcrypto_library>
Windows
NT,
<drive>:/<path_to_libsecude>/<name_of_sapcrypto_library>
Windows
2000
6. Check if the environment of the user running saprouter contains the
environment variable SNC_LIB.
UNIX
Printenv
Windows NT
System environment Variable
7. You may now apply for a SAProuter certificate from the SAP Trust Center
Service of SAP service marketplace
http://service.sap.com/tcs
> SAP Trust Center Service in Detail
> SAProuter Certificates
SAProuter Certificate "Apply Now"
Click the button.
8. Please take note of your "Distinguished Name"
Please refer to the example above
-SAPRouter Name
: JPL50020586
-Distinguished Name
CN=JPL50020586, OU=0000036946, OU=SAProuter, O=SAP, C=DE
Then, clicked the "Continue" button.
9. Execute the following command in the /saprouter/ntintel
directory in order to generate your certificate to be exchanged with SAP.
sapgenpse get_pse -v -r certreq -p local.pse "Distinguished Name"
Example
sapgenpse get_pse u2013v -r certreq -p local.pse "CN=JPL50020586, OU=0000036946,
OU=SAProuter, O=SAP, C=DE"
Enter the PIN number. (you may enter any PIN Number you wish.)
Please enter PIN :
Please re-enter PIN :
<- you must use the same PIN Number as the above.
10. The "certreq" file is created in the /saprouter/ntintel directory.
11. Use a notepad to open the "certreq" file and copy the displayed information
(From the -BEGIN .to the END -)
12.You now have to paste the above copy content into the space provided
shown below. After you have pasted the text, click the u201CRequest certificateu201D
button to submit your request.
13. Once you click on the u201CRequest Certificateu201D a new screen will be displaying
your certificate issued by SAP CA (Certification Authority).
14. Using a notepad to copy the content (From u2013Beingu2026 to -END) and save it
as u201Csrcertu201D into /saprouter/ntintel/srcert.
Note :
- Please rename srcert.txt into srcert without any extension.
15. You then need to import this certificate into SAProuter using the following
command.
Please run on /saprouter/ntintel directory.
sapgenpse import_own_cert -c srcert -p local.pse
Please enter PIN : (same as point 9)
16. Execute the following command in the /saprouter/ntintel directory.
sapgenpse seclogin -p local.pse
Please enter PIN : (same as point 9)
This will create a file "cred_v2" in the same directory.
17. Please check whether the certificate has been imported correctly.
Execute this command in /saprouter/ntintel directory.
sapgenpse get_my_name -v -n Issuer
The result should be "CN=SAProuter CA, OU=SAProuter, O=SAP, C=DE".
18. When the above results are not obtained , please delete local.pse and
cred_v2 and work again from steps 9. Please seek the assistance from your
local SAP helpdesk or create an OSS message via component XX-SER-NET-
OSS, if you are not able to obtain the above-mentioned result after you have
repeated the above steps.
Route permission table (saprouttab)
19. The corresponding file ./saprouttab should contain at least the following
entries.
Example : by SNC connection, when connecting to sapserv2
(194.39.131.34) the following entries need to be indicated by saprouttab.,
SNC-connection to SAP
KT "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 194.39.131.34
SNC-connection from SAP to local R/3-System for Support
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" <R/3-Server> <R/3-Instance>
SNC-connection from SAP to local R/3-System for pcANYWHERE, if it is needed
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" <R/3-Server> 5631
SNC-connection from SAP to local R/3-System for NetMeeting, if it is needed
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" <R/3-Server> 1503
SNC-connection from SAP to local R/3-System for saptelnet, if it is needed
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" <R/3-Server> 23
Access from the local Network to SAPNet - R/3 Frontend (OSS)
P <IP-addess of a local PC> 194.39.131.34 3299
deny all other connections
D * * *
Start the SAProuter with the following command.
Saprouter -r -S <port> -K
"p: <Your Distingiushed Name>"
-K tells the saprouter to start with loading the SNC library.
Example: saprouter -r -S 3299 u2013K "p:CN=JPL50020586, OU=0000036946,
OU=SAProuter, O=SAP, C=DE"
Additional Note
-You may refer to SAP note: 30289 in the SAP service marketplace for detail
information with regards to SAProuter
http://www.service.sap.com/note -
Reg : SAP Router Configuration
Dear Friends,
How to configure the SAP router? If anybody have configuration details pls help me.
Our System is ECC 6.0
OS - 2003 Server
DB : MS SQL Server
Then How to Communicate to SAP.
Regards
kesavHi,
> How to configure the SAP router? If anybody have configuration details pls help me.
1) Download the latest SAP Router files (saprouter.car, nipping, cryptographic library) from SAP Service Market Place --- Patches.
2)Create a user called sncadm as a member of Administrator. Log off administrator and login as sncadm. Create the following environment variables for this user.
SECUDIR = c:\usr\sap\saprouter
SNC_LIB = c:\usr\sap\saprouter\sapcrypto.dll
3) Create folder c:\usr\sap\saprouter and copy the downloaded files into that folder. Extract all the compressed files. Now typically this folder will have the following files.
Sapcrypto.dll
Sapgenpse.exe
Ticket
Ntscmgr.exe
Nipping.exe
Saprouter.exe
(other required files can be copied from kernel directory of other SAP Systems)
4) Go to http://service.sap.com/saprouter-sncadd. Click on u201CApply Nowu201D
You will get information like this (on first screen):
Click on Continue. Now we have to create the request for SAProuter which is to be given as input in the next screen u201CRequest Certificate for SAProuteru201D.
5)Open a command prompt and execute the following commands.
Cd \usr\sap\saprouter
sapgenpse get_pse u2013r sap-router.p10 u2013p sap-router.pse u201CCN=SAP-ROUTER, OU=0000733879, OU=SAProuter, O=SAP, C=DEu201D
You will be asked for a PIN: input any (but do not forget!!!!!) No Password is given in this installation.
This command will create the file sap-router.p10 and sap-router.pse.
Open the file sap-router.p10 with notepad, copy & paste this certificate request to the text area of the u201CRequest Certificate for SAProuteru201D page.
Click on Request Certificate
In response you will get certificate signed by CA.
Copy & paste the text into a text file including the header & footer (saprt.txt is the file created here)
6)Now install the certificate as follows
Sapgenpse import_own_cert u2013c saprt.txt u2013p sap-router.pse
7)Now create credentials for saprouter
Sapgenpse seclogin u2013p sap-router.pse u2013O sncadm
This will create a file called cred_v2 in c:\usr\sap\saprouter
8)Now Check whether certificate has been imported correctly or not
Sapgenpse get_my_name u2013v u2013n Issuer
The name of issuer should be: CN=SAProuter CA, OU=SAProuter, O=SAP, C=DE. If the name is not correct, then delete the file cred_v2 and start all over again from Step u2013 4.
9)Now create a file u201Csaprouttabu201D in the folder c:\usr\sap\saprouter and make the following entries in that.
SNC connection to SAP
KT "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 194.39.131.34 *
Access from your local Network to SAPNet - R/3 Frontend
P 172.16.. 194.39.131.34 3299
P 172.17.. 194.39.131.34 3299
P 172.18.. 194.39.131.34 3299
P 172.19.. 194.39.131.34 3299
D * * *
Save the file and close
10) Make the following changes in the hosts file and services file (under windows\system32\drivers\etc folder ) SAP-ROUTER system
hosts file:
172.18.9.8 SAP-ROUTER
194.39.131.34 sapserv2
services file:
sapdp99 3299/tcp
sapgw99 3399/tcp
sapmsO01 3601/tcp
11) Now check the entry in the services files for all servers and all front-end PCs under %winnt%/system32/drivers/etc/ there should have:
sapdp99 3299/tcp
sapmsO01 3601/tcp
12) Now start the sap router using the command (from the saprouter directory)
Saprouter u2013r u2013V 3 u2013K u201Cp:CN=SAP-ROUTER,OU=0000733879,OU=SAProuter,O=SAP,C=DEu201D
13)Connection to SAP can tested using the command
lgtst u2013H /H/172.18.9.8//H/194.39.131.34/S/sapdp99/H/oss001/S/sapmsO01 u2013S x u2013W 30000
Note : The file lgtst.exe can be copied from other SAP systemu2019s kernel directory.
The output should look like these:
Using trcfile: dev_lg
List of reachable application servers
u2026.
u2026..
u2026u2026.
u2026u2026u2026.
If the lgtst command does not display the list of reachable application servers, then the connection to SAP could not be established. Troubleshoot the error and rectify.
For more info see the following sapnote
note 30289 : SAProuter documentation
note 525751: Installation of the SNC-SAPRouter as NT Service
note 46902 : Security aspects in remote access
note 48243 : Integrating SAProuter into a firewall
note 33135 : Guidelines for OSS1 (Version for SAPSERV3).
note 35010 : Service connections: Composite note (overview) -
SAP Router configuration on Linux platform (error in start script)
Hello gurus,
I´m trying to setup the saprouter on Fedora v14 (32 bits).
I did all the configure with root user. The problem is when I run the script that starts the saprouter service, it show me the following error:
[root@saprouter sap]# pwd
/usr/sap/saprouter
[root@saprouter saprouter]# saprouter_start
/usr/sap/saprouter/saprouter_start: line 12: syntax error near unexpected token `|'
'usr/sap/saprouter/saprouter_start: line 12: ` | tee -a $LOGFILE &
The content of this script, has the following sintaxes:
# Start saprouter
# You can automatically start SAProuter when you start the system. In UNIX for example, you would change file /etc/rc.
# saprouter CN=saprouter, OU=0001214237, OU=SAProuter, O=SAP, C=DE sapserv2
SRDIR=/usr/sap/saprouter
LOGFILE="usr/sap/saprouter/saprouter_log"
if [ -f $SRDIR/saprouter ] ; then
echo "Starting SAP Router" | tee -a $LOGFILE
$SRDIR/saprouter -r -R $SRDIR/saprouttab -G $LOGFILE -W 60000 -K "p:CN=saprouter, OU=0001214237, OU=SAProuter, O=SAP, C=DE"
| tee -a $LOGFILE &
fi
The strange of this is I already did this type of configuration on Linux with the same scripts... but in red hat enterprise linux x86_64 and in there it works perfectly!
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/4f/992ce8446d11d189700000e8322d00/frameset.htm
Can you help me please in way to solve this problem...?!
Best regards,
João Dimas - PortugalHello Clebio,
First al all, please don´t forget to read my previous message.
I´m writing again because I made other tests that I would like to show you...!
1- In my previous message I mentioned an error when I ran directly the command # saprouter -r... and as you recomend, I typed the "ldd saprouter", the output of this show that libstdc+.so.5: was not found! I already solve this issue, I installed the compat-libstdc+ with # yum install compat-libstdc++. So... now when I run that "ldd saprouter" the result is:
[root@saprouter saprouter]# ldd saprouter
linux-gate.so.1 => (0x003a9000)
libdl.so.2 => /lib/libdl.so.2 (0x00911000)
librt.so.1 => /lib/librt.so.1 (0x00918000)
libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0x00110000)
libm.so.6 => /lib/libm.so.6 (0x00923000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00966000)
libpthread.so.0 => /lib/libpthread.so.0 (0x008f4000)
libc.so.6 => /lib/libc.so.6 (0x00768000)
/lib/ld-linux.so.2 (0x00747000)
It seems that is solved! Is not it?
2- After that correction, I ran again the # saprouter -r but now it show me the following error:
[root@saprouter saprouter]# saprouter -r
trcfile dev_rout
no logging active
*** ERROR => invalid lines in './saprouttab', see 'dev_rout' [nirout.cpp 8006]
... next, what I did was, I opened the dev_rout:
trc file: "dev_rout", trc level: 1, release: "700"
Thu Aug 11 13:10:49 2011
SAP Network Interface Router, Version 38.10
command line arg 0: saprouter
command line arg 1: -r
main: pid = 9808, ppid = 2038, port = 3299, parent port = 0 (0 = parent is not a saprouter)
reading routtab: './saprouttab'
*** ERROR => SNC field without SNC active, skip line 2 [nirout.cpp 7775]
*** ERROR => SNC field without SNC active, skip line 3 [nirout.cpp 7775]
*** ERROR => SNC field without SNC active, skip line 8 [nirout.cpp 7775]
... and I also checked my saprouttab in there I see...:
1. vim saprouttab
# SNC connection to and from SAP
KT "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 194.39.131.34 *
KT "p:CN=saprouter, OU=000121987, OU=SAProuter, O=SAP, C=DE" 81.193.132.663 3299
# SNC connection to local system for R/3-Support
# R/3 Server: 192.168.34.178
# R/3 Instance: 00
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 192.168.34.178 3200
# Access from the local Network to SAP
P * 194.39.131.34 3299
# Deny all other connections
#D * * *
What´s the problem!??! I don´t get it!! My God... I don´t understand, all the entries in saprouttab seems well to me! Can you verify this please?! It´s correct, isn´t it?
Can you help me!?
Thank you
João Dimas - Portugal -
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,
Robinpls 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
ThomSame answer as in the other forum where you cross posted....
-
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.NatarajanHi
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
Maybe you are looking for
-
Outgoing mail service offline charter
I cannot send email from my imac. Out going mail service shows offline with no other options. I can send email from my iphone. Help?
-
I click on a photo in events and keeping the mouse button depressed I drag the photo to the folder of the left, but a new folder opens with the photo. It doesn't place the photo into the folder that I have already created. What am I doing wrong? I se
-
How do I get my DAQ to have frequency resolution of 0.5 hz after FFT ?
Hi all, I was just wondering how do I get a frequency resolution of 0.5hz after the FFT from this VI. Or perhaps there can be some advice on where I must improve it. Appreciate all advice, thanks! -How81 as of now, the waveform graph i obtained, I wa
-
Apple TV - is this stopping my MacBook volume working?
Linked to my previous question, I realise that the problem of my MacBook not playing sound started after we bought an Apple TV. When we use the AppleTV controller, the MacBook screen presents images for Front Row, event though the TV screen shows sel
-
Multiple loops in one loop for text variables
Dear experts, Please find the code below.This is text variable customer exit.Can u ple help me to put these multiple loops into one loop.Do u suggest this code is ok? Appreciate your help. WHEN 'ZSTXTPE01AA'or 'ZSTXT0FISCPER305AA'or 'ZSTXT0FISCYEAR01