Print Server May Log Event 18 Errors After SP1 Installed on Host Integration Server 2000

After you install Host Integration Server 2000 Service Pack 1 (SP1), the following errors may be logged in the Application Event log:

During the installation of Host Integration Server 2000 SP1, the National Language Support (NLS) Code Page registry parameter may be removed. The removal of these registry parameters cause the event 18 errors to be logged when host print sessions are activated.

To work around this problem, follow these steps:

1. Save the following NLS Code Page registry key on a similar system:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nls\CodePage
   Restore the registry key on the system that is experiencing the problem.
2. Restore the registry key on the system that is experiencing the problem.

For additional information about how to save and restore registry parameters on Windows 2000 (and for links to articles about how to do this on other operating systems), click the article number below to view the article in the Microsoft Knowledge Base:

Microsoft has confirmed that this is a problem in Microsoft Host Integration Server 2000 SP1.

You may receive the error listed in "Symptoms" if you follow the steps in this scenario:

1. Install Host Integration Server 2000 SP1.
2. Microsoft Windows Installer (Msiexec.exe) detects an error during the installation process and stops the installation of SP1.
3. Try again to install Host Integration Server 2000 SP1.

The error that Windows Installer detects during the first attempt to install SP1 may occur when Windows Installer cannot stop the SNA services (that is, SNA Server service and SnaBase service) that are running on the Host Integration Server 2000 system. This also includes any third-party or customer written services that are dependent on the installed SNA services.

During the initial installation of Host Integration Server 2000 SP1, Windows Installer may experience an error that results in the NLS Code Page registry parameters being removed, and the following error may appear in the System Event Log: