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.
Installation Runtime Error Read More »
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.
Unable to Register ActiveX Controls Read More »
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.
Unable to Establish SMTP Connection Read More »
One of the errors that developers occasionally ask about is the "Handle not owned by the current thread error"; what it actually means and the situations in which it can occur. This doesn't tend to be an error message that developers using the SocketTools ActiveX controls encounter. It is almost exclusively an issue related to
SocketTools and Multi-threading Read More »
SocketTools includes components for sending e-mail using SMTP, downloading and managing messages using POP3 or IMAP4 and a general purpose MIME component that can be used to parse messages and create new ones. However, one of the problems that developers often face is what to actually do with those messages once they have been sent
SocketTools Message Store Read More »
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.
InvalidOperationException Error Read More »
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.
Unable to Connect Using SSH Read More »
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.
Networking Subsystem Not Initialized Read More »
In older versions of Windows, it was common for regular users to run with administrative privileges. In fact, most Windows applications made the assumption that the user was a member of the Administrators group and therefore had unrestricted access to the entire system. This has changed with the User Account Control (UAC) system, which limits access to critical system resources,
User Account Control and User Virtualization Read More »
The Secure Shell protocol provides a secure, encrypted connection between the local host and a remote computer, ensuring that third-parties cannot decipher any intercepted network traffic. Originally SSH was used primarily on UNIX based systems as a secure alternative to the insecure TELNET protocol, in which private information such as passwords would be sent as
The Secure Shell Protocol Read More »
