HIS End-User Client Install Fails with Internet Explorer 6.0 (308583)



The information in this article applies to:

  • Microsoft Host Integration Server 2000, when used with:
    • the operating system: Microsoft Windows NT 4.0
    • the operating system: Microsoft Windows Millennium Edition
    • the operating system: Microsoft Windows 98

This article was previously published under Q308583

SYMPTOMS

When installing the Host Integration Server (HIS) 2000 End-User Client on a Windows NT 4.0, Windows Millennium Edition (Me), Windows 98, you may receive the following dialog box error
Setup cannot continue, as Internet Explorer 5.0 is not installed.
followed by:
Installation ended prematurely because of an error.
The following event is posted in the application log of the Event Viewer:
Event 1000 - Source: MsiInstaller

Product Microsoft Host Integration Server 2000 End-User Client -- Setup cannot continue, as Internet Explorer 5.0 is not installed.
This problem is not seen on Windows 2000 systems.

CAUSE

During installation, the End-User Client checks the Internet Explorer registry key for version information. In this case, it only checks for version 5.0; any other version information causes setup to fail.

RESOLUTION

To resolve this problem, obtain the latest service pack for Host Integration Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

328152 How to Obtain the Latest Host Integration Server 2000 Service Pack

WORKAROUND

  1. Start Registry Editor (Regedt32.exe).
  2. Locate the Version value under the following key in the registry:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer

  3. On the Edit menu, click String, replace the first numeric value with the value 5, and then click OK.

    For example, if the version says 6.0.2600.0000, change it to 5.0.2600.0000.
  4. Quit Registry Editor.
NOTE: After installing the End-User Client, this registry value should be changed back to its original value.

STATUS

Microsoft has confirmed that this is a problem in Host Integration Server 2000. This problem was first corrected in Host Integration Server 2000 Service Pack 1.

Modification Type:MinorLast Reviewed:4/19/2005
Keywords:kbbug kbfix kbHostIntegServ2000preSP1fix kbHostIntegServ2000SP1fix KB308583