I am trying to open a service connection to SAP via the Service marketplace and continue getting Host did not respond error message.
The dev_route file shows this:
trc file: "dev_rout", trc level: 1, release: "710"
Wed Feb 08 22:25:58 2012
SAP Network Interface Router, Version 39.3 (SP4)
command line arg 0: saprouter
command line arg 1: -r
command line arg 2: -R
command line arg 3: D:\usr\sap\saprouter\saprouttab
command line arg 4: -K
command line arg 5: p:CN=office.xxxx.com, OU=0000715836, 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)
SncInit(): Trying environment variable SNC_LIB as a
gssapi library name: "D:\usr\sap\saprouter\nt-x86_64\sapcrypto.dll".
File "D:\usr\sap\saprouter\nt-x86_64\sapcrypto.dll" dynamically loaded as GSS-API v2 library.
The internal Adapter for the loaded GSS-API mechanism identifies as:
Internal SNC-Adapter (Rev 1.0) to SECUDE 5/GSS-API v2
main: pid = 3876, ppid = 0, port = 3299, parent port = 0 (0 = parent is not a saprouter)
reading routtab: 'D:\usr\sap\saprouter\saprouttab'
Wed Feb 08 22:27:39 2012
***LOG Q0I=> NiIRead: P=192.168.1.101:61800; L=192.168.1.101:3299: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4931]
ERROR => NiIRead: SiRecv failed for hdl 9/sock 284
(SI_ECONN_BROKEN/10054; I4; ST; P=192.168.1.101:61800; L=192.168.1.101:3299) [nixxi.cpp 4931]
running a niping command of
D:\usr\sap\saprouter>niping -c -H /H/192.168.1.101/H/22.214.171.124/H/126.96.36.199
After 10 unsuccessful service connection attempts the connection is cancelled.
Can anyone please help with resolving this issue?
The Return code 10054 means "connection reset by peer" is a clear indication for a network problem as this error is thrown by the operating system.
On Windows this can be caused by:
- a physicaly interupted connection (network cable pulled out or a
defective NIC/switch/bridge/router) or
- a network timeout caused by a firewall dropping packets (e.g. after an
- a black hole router
I have however seen a case where, the issue occurred due to a problem
Can you please check if you see an error similar to the following
in the Event log:
Faulting application name: saprouter.exe, version: 7188.8.131.52443,
time stamp: 0x4bfae3ce
Faulting module name: saprouter.exe, version: 7184.108.40.206443, time
Exception code: 0xc0000005
Fault offset: 0x000000000000c1f3
Faulting process id: 0xe60
If you see an exception code "0xc0000005" the issue may be related to the bug in note 1486956. Please download the latest version of saprouter and see if this resolves the issue.
Guilherme de Oliveira.
I have checked the event log and found no reference to the saprouter nor that exception code. I had already replaced the saprouter with the latest version from servicemarketplace and am now running version 39.3 (SP4) but still get the error.
I have looked in all likely places where a network issue may occur checking windows firewalls, external routers firewall and these are all okay. As I am getting successful returns from niping and my OSS1 connection is also working fine I am struggling to determine the problem here.
You can try to get more information about your issue doing:
1. Stop the saprouter process (saprouter -s).
2. Start the saprouter process with "-V 2" option in the command line.
3. Test the RFC connection to SAPOSS (SM59 -> R/3 Connections -> SAPOSS).
Then, the dev_rout trace should have more information that may help you here.
Hope it helps.
Guilherme de Oliveira.
Please ensure all the required entries are maintained in the System data before opening the connections.
For Ex- Hostaname/Ip of the machine, Instance number, SAP Router details Hostname, IP address and port 3299 are maintained under the system tab and not the application server tab.
In the application server tab, create the App server with details like hostname, ip address and instance number.
Then Sapouttab file is maintained with required details.