Skip to Content

Semi-random 20 seconds "WSAETIMEDOUT: Connection timed out" on invalid system number

Mar 08 at 11:08 PM


avatar image

I do have the right bit-ness of assemblies installed. I am able to reach SAP and do RFCs, BAPIs, iDOCs with a correct connection configuration. When the provided system number is incorrect, I expect a "

100 is not a valid system number

" or a "

WSAECONNREFUSED: Connection refused

" (system number -> 0). And sometimes I do get exactly those responses, sometimes I get 20 seconds timeout instead. I noticed the following old thread with a similar question but no helpful answer:

LOCATION CPIC (TCP/IP) on local host daviburg-bizapi with Unicode
ERROR partner '' not reached
TIME Thu Mar 08 14:49:30 2018
COMPONENT NI (network interface)
RC -10
MODULE nixxi.cpp
LINE 3289
DETAIL NiPConnect2:
ERRNO 10060
ERRNO TEXT WSAETIMEDOUT: Connection timed out

You may ask why I am knowingly providing an invalid system number. This is because our application permits its users to input their connection configuration parameters. When they make a mistake, we need to display for them an actionable and helpful error messages that guides them to correct the configuration mistake rather than call tech support. For that, "

100 is not a valid system number

" is a very helpful response from SAP. "

WSAECONNREFUSED: Connection refused

" is not as helpful but at least comes quickly. Random "

WSAETIMEDOUT: Connection timed out

" with 20 seconds delays... Not helpful and quite painful.

Furthermore once such timeout error occurs, even with the customer providing a corrected system number the new connection attempts to SAP fail with the same error until we recycle our application process.

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

0 Answers