This article was previously published under Q300179
This article has been archived. It is offered "as is" and will no longer be updated.
When you attempt to start a program, or a program attempts to start when you log on the computer, you can receive the following error message:
Entry Point Not Found: The procedure entry point SetHandleContext could not be located in the dynamic link library: Kernel32.dll.
This error can persist regardless of the computer that you log on to. The re-installation of the program does not correct the error.
This behavior can occur because a function that is contained in a dynamic-link library (.dll) file, which is typically meant for use in Microsoft Windows 95, Microsoft Windows 98, or Microsoft Windows Millennium Edition (Me), attempts to call the SetHandleContext() application programming interface (API). However, this API does not exist in the Windows 2000 version of the Kernel32.dll file, which results in the error that is described in the Symptoms section of this article.
To work around this behavior, examine your home drive (the drive letter of your local workstation) and the entries in the path variable until you locate the incorrect versions of the .dll files. Then, delete the problem .dll files.
If the .dll files are found in your home drive, you can disconnect the drive as a temporary workaround.
This behavior is by design.
For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
142606 ErrMsg: Procedure Entry Point Could Not Be Located
In some situations, the problem files are not contained on the local computer. When you start a program, or if the start of a program is based on your logon session, the default starting folder for this process is your home drive. If this home drive contains the older versions of the files that are called by the starting program, the older versions of the files are used, even if newer files are present on the computer. If the files are not found on your home drive, the programs attempt to access the folders that are defined in the file path to locate the files that are needed to start the programs.
Typically, the error that is described in the Symptoms section of this article occurs when a process that accesses Windows Sockets (Winsock) attempts to start. The incorrect file versions that can lead to this error can include, but are not limited to:
Typically, if this problem exists, it can occur with any product that makes use of Winsock, such as, Microsoft Internet Explorer, Microsoft Outlook Express, and MSN Messenger.