procedure TForm1.Button1Click(Sender: TObject); var StreamFiles: TIdMultiPartFormDataStream; path : string; begin StreamFiles := TIdMultiPartFormDataStream.Create; path := 'D:\example.doc' ; try StreamFiles.AddFile('upload_file', path, 'text/plain'); try IdHTTP1.Post('http://myserver.com/upload/files', StreamFiles); except on E: Exception do ShowMessage('Error encountered User suggestions: see WSAHOST_NOT_FOUND for details. This means another type of request to the name server will result in an answer. ChoAnderson Administrator A.2 Windows Sockets error code extensions described Here are WSAGetLastError () function returns a list of possible error codes in alphabetical order , and gives a brief description of his comment is here
Too many open sockets. This is not a soft error, another type of name server request may be successful. A couple functions that the v1.1 specification missed are WSASetLastError() and WSAUnhookBlockingHook(). Developer suggestions: WSAStartup() failed, and you didn't detect it, or it wasn't called for the current task at all, or you called WSACleanup() too many times. https://msdn.microsoft.com/en-us/library/windows/desktop/ms740668(v=vs.85).aspx
Developer suggestions: If you don't detect it beforehand (e.g. Developer suggestion: are you trying to use an optional feature? 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 No more results can be returned by the WSALookupServiceNext function.
WSAESHUTDOWN 10058 Cannot send after socket shutdown. This has no network-relevant analog (although the "inode" reference could refer to a network file system entry). It is a nonfatal error, and the operation should be retried later. Socket Error 11004 If the hostname resolution uses a local host table, it's possible you resolved to an obsolete address.
When it occurs, it could indicate a serious failure of your network system (i.e. User suggestions: see WSAHOST_NOT_FOUND for details. The option is unknown or unsupported.WSAEPROTONOSUPPORT (10043) Protocol not supported The protocol has not been configured into the system, or no implementation for it exists. RECOMMENDED Click the "Scan Now" Button.
Winsock description: Winsock doesn't support the sendmsg() function, and some Winsock implementations are not so strict as to require an application with a datagram socket to 'disconnect'--by calling connect with a Windows Socket Error Windows 10 WinSock function: gethostbyaddr(), gethostbyname(), WSAAsyncGetHostByAddr(), WSAAsyncGetHostByName(), WSAAsyncGetProtoByName(), WSAAsyncGetProtoByNumber(), WSAAsyncGetServByName(), WSAAsyncGetServByPort() See also: WSANO_DATA, WSANO_RECOVERY, WSATRY_AGAIN WSAVERNOTSUPPORTED (10092) WINSOCK.DLL version out of range Berkeley description: No equivalent. Detailed description: send() & sendto(): the requested address is a broadcast address, but the appropriate flag was not set (i.e. It would also timeout if a (FIN)ish TCP packet is not ACK'd (and even if the FIN is ACK'd, it will eventually timeout if a FIN is not returned).
For example, the ARPA Internet UDP protocol cannot be specified with a socket type of SOCK_STREAM. this content An operation was attempted on a nonblocking socket with an operation already in progress—that is, calling connect a second time on a nonblocking socket that is already connecting, or canceling an But most of these function-less errors are simply out of place; they are inappropriate to the Windows Sockets API as it exists in the v1.1 specification. WSAECONNABORTED (10053) Software caused connection abort. Socket Error 10053
WinSock description: The 'address' they refer to, typically refers to the local 'socket name', which is made up of the 3-tuple: protocol, port-number and IP address. Whether to handle it as a fatal error or non-fatal error depends on the application and the context, so it's up to you to decide. If you have more than one WINSOCK DLL on your system, be sure the first one in the path is appropriate for the network subsystem currently loaded. http://phabletkeyboards.com/socket-error/socket-error-10004-interrupted-function-call.php Review by : Vera King Awesome, fast fix!
WSAHOST_NOT_FOUND for details. WSAEAFNOSUPPORT 10047 Address family not supported by protocol family. the protocol stack that the WinSock DLL runs over). Socket Error 10061 Connection Refused For example, the value given for the origin when positioning a file pointer (by means of a call to fseek) is before the beginning of the file.WSAEMFILE (10024) Too many open
A request to send or receive data was disallowed because the socket had already been shut down in that direction with a previous shutdown call. Windows Sockets code Error Description ------------------------------------------------------------------------ WSAEINTR 10004 Interrupted system call. Applications that use WSAGetOverlappedResult (with the fWait flag set to FALSE) in a polling mode to determine when an overlapped operation has completed, get this error code until the operation is check over here WSA_QOS_GENERIC_ERROR 11015 QoS generic error.
The file's permission setting does not allow the specified access. WinSock description: Same as Berkeley. There are no QoS senders. WSAEHOSTUNREACH 10065 No route to host.
WSAEADDRNOTAVAIL 10049 Cannot assign requested address. User suggestions: Some network systems have commands to report statistics. WinSock functions: accept(), listen(), recv(), recvfrom(), send(), sendto() WSAEPFNOSUPPORT (10046) Protocol family not supported. Berkeley description: The quota system ran out of table entries.