Knowledge Base

SocketTools includes several server components, including a multi-threaded HTTP server. Initial testing is often done with the client and server connecting to one another on the local system, rather than over the Internet. When using the Chrome, Firefox or Internet Explorer browsers, the connection to the local server is successful. However, connection attempts fail when […]

When attempting to manually register a control from the command line using the RegSvr32.exe utility, an error is displayed stating that the ActiveX control was loaded but the call to DllRegisterServer failed with error code 0x80040200.

There are a few important development considerations when exchanging binary data over a network connection. For most applications, strings should never be used to send or receive binary data; instead, applications should use byte arrays to exchange binary data.

When executing a program that uses an ActiveX control, the following error is returned: Run-time error 429: ActiveX component can't create object.

When attempting to install SocketTools, a message box is displayed with the error number 0x80040707 and the setup immediately terminates. Typically there is no description for the error code.

When attempting to register a SocketTools ActiveX control, an error is displayed indicating it is not an executable file and no registration helper is registered for this file type. This error typically occurs when registering a 32-bit control on a 64-bit version of Windows.

An application which uses the SocketTools SMTP client component to submit e-mail messages for delivery fails with error 0x8004274C (10060) or error 0x8004274D (10061). This indicates that the connection has timed out, or was refused by the remote host.

When attempting to run an application that uses one of the SocketTools .NET components, an InvalidOperation exception is generated. If the exception is not handled, a message box will be displayed that contains additional information about the error and then the program terminates.

When attempting to establish a connection using the Secure Shell (SSH) protocol to a server, the connection fails with an error indicating that the connection could not complete. This error affects both the SocketTools SSH component and file transfers using the SFTP (FTP+SSH) protocol.

Attempting to initialize a SocketTools .NET class, ActiveX control or library fails with an error indicating that the networking subsystem cannot be initialized. The application cannot establish a connection, and subsequent attempts to reinitialize the component also fails with the same error message.