Knowledge Base

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.

When attempting to install SocketTools, an error message is displayed that states IKernel.exe could not be installed. This error typically occurs when an instance of the InstallShield engine is already running or one of the InstallShield components are flagged as read-only.

When attempting to resolve an IPv6 address, either explicitly or by specifying an IPv6 address as the host address when establishing a connection, the method or function fails with an error indicating that the address is invalid. This occurs most commonly on a Windows XP or Windows Server 2003 systems, where the same address can be

When attempting to open a SocketTools example project for Visual Basic 6.0, the error "Class MSComctlLib.ClassName of control ControlName was not a loaded control class" is displayed.

Submitting an e-mail message to a Microsoft Exchange Server is significantly slower than expected, where each message submission can take up to 10 seconds to complete. This problem does not occur when submitting messages to other types of mail servers, including earlier versions of Exchange Server.

The total number of sockets that can be created using the SocketTools controls or libraries varies, based on the version of Windows and the amount of physical memory that is available. It is also important to distinguish between the number of sockets that can be allocated by a client application and the number of inbound connections

When attempting to upload a file to an IIS web server using the HTTP PUT command, the transfer fails with a 404 error. The server administrator had used the IIS Lockdown Tool to secure the server.

When you create an application using the SocketTools Library Edition DLLs and you're ready to deploy it, you must ensure the libraries you're using are initialized correctly. This is done by providing a runtime license key to the initialization function for each of the SocketTools APIs you are using. It is important to note your

When you create an application using the SocketTools ActiveX Edition controls and you're ready to deploy it, you must ensure the controls you're using are initialized correctly. If you are developing with Visual Basic 6.0, and you've placed the controls on a form, it will automatically initialize the controls when the form is loaded.

When you create an application using the SocketTools .NET Edition components and you're ready to deploy it, you must ensure it is initialized correctly. This is done by either providing a runtime license key to the Initialize method, or setting the RuntimeLicense attribute for the executable assembly. It is important to note your runtime license