#ABAP_Trial, GUI-Logon Error: 10035 WSAEWOULDBLOCK: Resource temporarily unavailable

[DirkO]

Dear all,

I´m facing an issue when trying to logon with GUI (or eclipse) from a laptop to a ABAP trial 1909 running on a second system in my network.

Current setup:
ABAP trail 1909 is running in a docker container on openSuse Leap15.2.
No problem to log on to "vhcala4hci" with java GUI or Eclipse on the openSuse box.
SAP GUI installed on laptop (Windows 10).
Issue: No logon possible from laptop.

Error messages when trying to log on with laptop:
Error: 10035 WSAEWOULDBLOCK: Resource temporarily unavailable
Partner '172.17.0.2:3200' not reached

The following notes has been checked (with limited understanding and no success of course):
2499735 - WSAEWOULDBLOCK error: Resource temporarily unavailable
124562 - Hostname resolution problems (DNS timeouts)

Please note:

No successful ping of 172.17.0.2 from the laptop to this IP-adress.
No difference w.r.t. the message even the network cable is plugged in or not. ...
No difference if firewall is active or not on laptop.

Port 3200 is exposed by the container.
"ExposedPorts": {
..
"3200/tcp": {},
"3300/tcp": {},
..

Even that MS states: Resource temporarily unavailable.
This error is returned from operations on nonblocking sockets that cannot be completed immediately,
for example recv when no data is queued to be read from the socket.
It is a nonfatal error, and the operation should be retried later.
It is normal for WSAEWOULDBLOCK to be reported as the result from calling connect on a nonblocking SOCK_STREAM socket, since some time must elapse for the connection to be established.

It is somehow like waiting for Godot, because even a retry later does not help.
Initially I just wanted quickly create a calculation view with a hierarchy....

Could someone please give me a useful hint how to solve the issue?
Thanks in advance & kind regards

[FredericGirod]

No successful ping of 172.17.0.2 from the laptop.

You mean, you cannot ping this IP from your laptop ?

[FredericGirod]

Instead of using ping (some basic firewall are locking ICMP). You could try to telnet the socket.

If you do not have telnet client on your computer, you could download putty :

https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html

Otherwise, telnet ip:port_number (syntax could depend of the system)

[DirkO]

Hi Frederic,

yes, you are rigth.

I can´t ping this IP from my laptop (successfully).

[FredericGirod]

so you need to check your network.

- Is your laptop in the same network ? IP starting with 172.17.0 ?

[Sandra_Rossi]

Or less weird URL for Putty 😉 : https://www.putty.org/

[Sandra_Rossi]

You can't ping the IP address, so it's not a problem of port right now and not a problem of DNS (used for host resolution).

Do you have a firewall? If yes, could you temporarily deactivate it and try again? If it works, you should adjust the firewall rules to accept the IP, protocol, ... (don't forget to reactivate the firewall)

[FredericGirod]

sandra.rossi my url was nice, not too long, funny name ... nothing to say

😉

[DirkO]

Thanx.

Telnet 172.17.0.2:3200 No connection to host via port 23

[FredericGirod]

dirk.obert I need to go to the swimming pool (sorry it is my second job)

So your both system should be on the same IP class. Otherwise, you have to create an alias, create an IP route .... better is to have the both address starting with the same number.

Second check the firewall of the Suse. Maybe it is also in Yast on Open-Suse, check the documentation.

[DirkO]

Hi,

no, my network is not in the range of 172.17.0.2., like most of us in a private network it is starting with 192.XX This IP-Adress is given by the container provided by SAP of the ABAP Trial 1909.

I will try to find out how to create an alias / IP route.

Thanks

[FredericGirod]

Change your IP address using YAST

https://forums.opensuse.org/showthread.php/512874-how-to-configure-static-ip-address-on-opensuse

Do not forget to edit the file /etc/hosts

the host of the SAP server must correspond to the IP address

[DirkO]

Salute Frederic!

thanks for your information.

As per my understanding in a docker container the IP is generally 172.xxx.xxx.xxx

I don´t have access to the network setting for the underlying OS of the SAP System in the docker container.

The ABAP Trial 1909 is provided as a docker container and due to this it seems to me that I can´t manipulate settings on OS level.

Or do you mean to change network settings of the host? Tried it, without any effect.

BR

[FredericGirod]

By container you mean Virtual system. If yes, your virtual system is doing the DHCP for your local system. You have to change in the virtua system the DHCP config, to switch the IP Class.

[DirkO]

Dear Frederic,

thanks for your effort. I´m refering to a docker not a VM.

KR

[DirkO · Accepted solution]

Issue is solved.

Background: If you expose a port from a container (say: -p 3200:3200) you will bind this port to the network interface of the HOST the container is running.

As a result of this you need to use the IP adress of your HOST and not the IP-adress of the container in the SAP GUI on the windows client.

[julieplummer20]

Hi, I'm glad this worked out. Can you please mark the question Answered. You can mark your own answer as Correct - it may be necessary to convert to an Answer.

This is really helpful, when I try to monitor open questions.

Thanks and best wshes,
Julie.

[FredericGirod]

I think the solution of your problem is here :

https://blogs.sap.com/2020/04/07/sap-as-abap-running-inside-docker.-part-i/

[Sriram2009]

Hi Di

1. In the SAP ABAP trial version system started? In the server check, was the firewall service started or not?

2. In the server are you able to ping the IP & hostname of the SAP system?

3. Is the ABAP trial version duration period expired?

Regards

SS

[DirkO]

Hi SS,

#1. Of course it was started & FW were not accessable because OS settings are not accessable in a docker.

#2. On the host the docker container is running I can ping the SAP System. The problem is, that this is not feasiable from windows.

#3. Nope, licence is valid.

KR