cancel
Showing results for 
Search instead for 
Did you mean: 

Connectivity error when test with consumer proxy and HCI

Wanling
Associate
Associate
0 Kudos

Hi,

I try to test the connection between consumer proxy(running on S/4 HANA Clould) and HCI nenant. The test using SOAPUI is fine, but when I try to run Ping Web Service(SOAMANAGER), the following exception is raised:

SRT Framework exception: Service Ping ERROR: Error when calling SOAP Runtime functions: SRT: Processing error in Internet Communication Framework: ("Connect to v0505-iflmap.avtsbhf.us1.hana.ondemand.com:443 failed: NIECONN_REFUSED(-10)")

Go through SAP Note 1947516 on how to test the Web Service, and can't find further information about NIECONN_REFUSED error. Any clue on what goes wrong?

Best regards,

Wanling


Accepted Solutions (0)

Answers (2)

Answers (2)

dirugadr
Participant
0 Kudos

Hi! Did you solve your issue? I'm facing the same right now, and I don't know how to solve it.

Former Member
0 Kudos

Hello Wanling,

Are there any empty message appearing in HCI message monitoring when you do ping Web service?

reg, avinash

Wanling
Associate
Associate
0 Kudos

I don't see any message reaches HCI side at all. I do another connection test using SM59. The same error NIECONN_REFUSED(-10) is raised as well. In SMCIM trace, the fellow information:

[Thr 140622463891200] NiICheckPendConnection: connection of hdl 1043 to 206.112.73.110:443 still in progress (5000)

[Thr 140622463891200] NiIConnect: hdl 1043 took local address 10.96.188.33:63315

[Thr 140622463891200] NiIConnect: state of hdl 1043 NI_CONN_WAIT

[Thr 140622463891200] *** ERROR => NiBufIConnect: non-buffered connect pending after 5000ms (hdl 1043;206.112.73.110:443) [nibuf.cpp    4598]

[Thr 140622463891200] NiICloseHandle: called for hdl 1043 while waiting for connection

[Thr 140622463891200] NiICloseHandle: shutdown and close hdl 1043/sock 36

[Thr 140622463891200] IcmIConnConnect: Connect to host: v0505-iflmap.XXX.hana.ondemand.com, service: 443, NIECONN_REFUSED(-10)

There is another cloud used for pre-test purpose, which works fine with the exactly same communication configuration.I suspect that it could be an setup issue in the cloud side.