> I don't know how to understand this error, as my connections with the > component work in my tool (1)....
It's a Winsock 2 error code: WSASYSCALLFAILURE 10107 System call failure. "A system call that should never fail has failed. This is a generic error code, returned under various conditions. Returned when a system call that should never fail does fail. For example, if a call to WaitForMultipleEvents fails or one of the registry functions fails trying to manipulate the protocol/namespace catalogs." (http://msdn.microsoft.com/en-us/library/ms740668.aspx) It's possible that Winsock installation is corrupted? -- Arno Garrels Guillaume ROQUES wrote: > Hi, > I use the FTP Client Component in 2 of my applications : > 1-Just a tool to manage the FTP connections > 2-A window service which check, by FTP, if some defined files exists. > > In my Tool (1), I could test my connections and it work well (similar > to the FtpCLi example ;p) > In my service (2), the connection doesn't work. I've got error like > this : > > Request 1 Done. > StatusCode = 500 > LastResponse was : "500 ESocketException: Not a WinSock error (#10107 > in Connect)" > > I don't know how to understand this error, as my connections with the > component work in my tool (1).... > > regards, > Guillaume ROQUES > CANYON Technologies -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
