Socket Error 10038 using Rebex.Net.Ftp.PutFile()

0 votes
asked Oct 15, 2018 by Saphymo (160 points)

Hello Rebex Community,
I use Rebex.Net.Ftp.PutFile () and get the following error message:
Rebex.Net.FtpException: Socket error 10038 occured.
Can it be that I use the library incorrectly or what can be the mistake?
Thank you very much.
Yours sincerely

Applies to: Rebex FTP/SSL

1 Answer

0 votes
answered Oct 15, 2018 by Lukas Pokorny (123,810 points)

Socket error code 10038 is WSAENOTSOCK, which indicates that "an operation was attempted on something that is not a socket". This error is known to occur on .NET Compact Framework when a connection to a network has been lost. Does this apply to your situation?

commented Oct 16, 2018 by Saphymo (160 points)
Good day,
a disconnect can happen in my case. Normally the application then goes into the timeout. I thought that the socket error code has something to do with improper programming of rebex pages. That's why I asked for a precaution ...
commented Oct 16, 2018 by Lukas Pokorny (123,810 points)
The error code is actually contradictory (an operation on a .NET socket failing with "not a socket" error), but that's what the underlying OS reports. However, we'll at least try enhance our library to raise an exception with a more meaningful message in this case.
commented Jan 3, 2019 by Lukas Pokorny (123,810 points)
Rebex FTP 2018 R3 and later report this as "Connection has been lost."