Home > Socket Error > Windows Socket Error 10038 Socket Operation On Non-socket

Windows Socket Error 10038 Socket Operation On Non-socket


This error occurs if the sin_addr is INADDR_ANY (i.e. User suggestions: see WSAHOST_NOT_FOUND for details. Ping a host on the same subnet as the host you were connected to (if you know one). As we pointed out earlier, your application should be ready to encounter any error at any time. http://introbuilder.net/socket-error/windows-socket-error-10038.php

WinSock functions: send(), sendto(), setsockopt() Additional functions: Any function that does network I/O: recv(), recvfrom(), FD_READ, FD_WRITE See also: WSAECONNABORTED, WSAECONNRESET, WSAETIMEDOUT WSAENETUNREACH (10051) Network is unreachable. This is not a temporary error. WinSock description: No equivalent. I can see two stderr outputs in bin/tern, neither of which stops the server, and several logs, mostly for --verbose and for shutdown.

Socket Error 10054

Apparently, the Windows Sockets specification left this out by oversight. WinSock description: Similar to Berkeley. You cant have two servers using the same port number, as we have just found out! This is a very common timing bug in WinSock programming - the good news (and bad news, because it's hard to reproduce) is that you are not hitting it very often

If so, is there an older DLL in a directory in the path ahead of the directory containing the newer DLL? temporary file not found in sh script Why are spare wheels smaller than normal wheels? WSAENETDOWN (10050) Network is down A socket operation encountered a dead network. Socket Error 10049 User suggestions: Did you enter a destination hostname?

WinSock functions: the list of functions that explicitly list this error in the v1.1 Windows Sockets specification. Code: bool CSocketComm::ShutdownConnection(SOCKET sock){ shutdown(sock, SD_BOTH); return ( 0 == closesocket( sock )); } and this is what the thread proc runs. Such an error is always a bug, it's not related to the real network activity/state and etc. However, it also occurs when an application passes an invalid pointer value.

TCP/IP scenario: In BSD-compatible implementations, the local network system generates this error if there isn't a default route configured. Socket Error 11004 Perhaps the missing libs/plugins should be summarized on stdout, before the Listening on ...? If you are using a host table exclusively, you'll need to update it to add the destination hostname and address. Unfortunately, to find out what these errors mean you need to contact that WinSock provider.

  1. TCP/IP scenario: The local network system can generate this error if there is no a default route configured.
  2. Fortunately, if WSAStartup fails, it will return a Winsock error code.
  3. User suggestions: Try to ping the destination host, to see if you get the same results (chances are, you will).
  4. The specified socket parameter refers to a file, not a socket.
  5. For instance, this error will occur if you try to run two applications that have FTP servers.

Socket Error Codes Linux

For protocol and services resolution, the name or number was not found in the respective database. The specified socket parameter refers to a file, not a socket.WSAEDESTADDRREQ (10039) Destination address required A required address was omitted from an operation on a socket. Socket Error 10054 User suggestions: Either you went to the wrong host, or the server application you're trying to contact isn't executing. Socket Error 10053 Berkeley description: This is a temporary condition and later calls to the same routine may complete normally (also known as EAGAIN error in Berkeley Software Distribution version 4.3) WinSock description: Same

User suggestions: Chances are the network subsystem is misconfigured or inactive. navigate to this website Do you have a router configured? In your original post, you said that you received 10038 when calling the socket() function. WSAHOST_NOT_FOUND for details.WSANO_ADDRESS (11004)* No address, look for MX record The requested name is valid, but does not have an Internet IP address at the name server. Socket Error 10054 Connection Reset By Peer

If we modify our Winsock initialization code slightly... if ( bSmartAddressing && dwBytes == sizeof(SOCKADDR_IN)) { OnEvent( EVT_ZEROLENGTH, NULL ); } else if (dwBytes > 0L) { OnDataReceived( lpData, dwBytes); } //Sleep(0); } } i cant explicitly call stopcomm share|improve this answer answered Oct 16 '10 at 8:34 Mitch Wheat 216k28347443 1 downvoters please leave a comment. –Mitch Wheat Jan 30 at 0:00 Can you explain the http://introbuilder.net/socket-error/windows-socket-error.php On a datastream socket, some applications use this error with a non-blocking socket calling connect() to detect when a connection attempt has completed, although this is not recommended since some WinSocks

If you have more than one server configured, the hostname query fails only after the WinSock DLL has queried all servers. Windows Socket Error Windows 10 each connection is a separated thread: they start like this: Code: bool CSocketComm::WatchComm(){ if (!IsStart()) { if (IsOpen()) { HANDLE hThread; UINT uiThreadId = 0; hThread = (HANDLE)_beginthreadex(NULL, // Security attributes In your words: "why would the socket Function return INVALID_SOCKET and in the WSAGetLastError return 10038 " Now you are telling us that 10038 error is received "when I close socket+thread".

Note that the v1.1 Winsock specification does not explicitly state that this error occurs if the value you request is larger than the WSAData.iMaxUdpDg returned from WSAStartup.

when on the socket function documentation 10038 is not a valid error code for its call http://msdn.microsoft.com/en-us/libr...=vs.85%29.aspx may be regarded to the buffer i dont know what to think this is Reload to refresh your session. As you can see from the comprehensive list of WinSock functions, this error is the catch-all. Socket Error 10061 Connection Refused If you have a multi-threaded application - it's likely that you close the socket in one thread, whereas the other thread still trying to use it.

The WSAEAFNOSUPPORT is the likely substitute error for this in WinSock, although its Berkeley meaning is slightly different. You can attempt to avoid the error by calling WSAIsBlocking() before making any WinSock function calls. Some errors do not always mean death for the program. click site try to ping the server(s)).

However, some WinSocks fail with WSAEINVAL you call connect() a second time (or subsequent) on a non-blocking socket. and then on another thred i call manteniance it calls stop comms on all the sockets that had been marked as inactive. Assuming you have a name server configured instead of or as well as a host table, a hostname resolution request causes a WinSock DLL to send a DNS "A" record query You should now begining to see a pattern forming with our error checking.

But most of the times this is just a temporary error which will be solved simply restarting Windows. I agree that the complexity on this is ridiculous, but it appears the Python libs simply don't provide a sane way to do it. The error can occur when the local network system aborts a connection.