Knowledge Base

FIX: InternetOpenUrl Does Not Work When Called Asynchronously

Article ID: 176176

Article Last Modified on 8/29/1999

Microsoft Internet Explorer 4.0 128-Bit Edition

This article was previously published under Q176176

SYMPTOMS

When InternetOpenUrl is called asynchronously, the callback function may still report error 997 (ERROR_IO_PENDING) even on the INTERNET_STATUS_REQUEST_COMPLETE notification.

Note that the same code works in Internet Explorer 3.02

CAUSE

The above behavior takes place when all the following conditions occur:

A direct connection to the Internet is used (no proxy is configured in Internet Explorer).
InternetOpen is called with the INTERNET_OPEN_TYPE_PRECONFIG option.
InternetOpenUrl is called asynchronously.

RESOLUTION

Installing Internet Explorer 4.01 will resolve the problem.

As temporary workaround for Internet Explorer 4.0, you can configure proxy in Internet Explorer and use INTERNET_OPEN_TYPE_PRECONFIG access type, but configure Internet Explorer to use a nonexistent proxy name. To make sure that this proxy does not interfere with WinInet operations, check "Bypass proxy server for (intranet) address" in the Connection tab of Internet Options in Internet Explorer 4.0.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. This bug was fixed in the WinInet.dll included with Internet Explorer 4.01.

Keywords: kbbug kbfix KB176176