FIX: The SnaBase service logs Event ID 1006, and the SnaBase service does not start when a user logs on to a system that was upgraded from the Host Integration Server 2000 End-User Client to the Host Integration Server 2004 Client

When a user logs on to a system that was upgraded from the Microsoft Host Integration Server 2000 End-User Client to the Microsoft Host Integration Server 2004 Client, the SnaBase service logs the following event:

Event ID: 1006
Source: SNA Base Service
Description: Unable to access configuration information
Action: The SnaBase service was either unable to open the configuration file or unable to initialize SNACFG.DLL. The error code from SNACFG.DLL is 2. An error code of 0 means that the SnaBase service was unable to initialize SNACFG.DLL.

Additionally, the SnaBase service does not start.

This problem only occurs when multiple users log on to the Host Integration Server 2004 Client system. This includes terminal services environments and environments where multiple users share a client workstation.

Additionally, this problem does not occur for the user who initiated the Host Integration Server 2004 Client installation to upgrade the existing Host Integration Server 2000 End-User Client. This problem only occurs for subsequent users who log on to the system and try to run the Host Integration Server 2004 Client.

The Host Integration Server 2004 Client does not correctly copy the required registry parameters from the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SnaBase\Parameters registry subkey to the HKEY_CURRENT_USER\Software\Microsoft\SnaBase\Parameters registry subkey when the SnaBase service starts. This problem occurs when users who did not perform the upgrade log on to the system.

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.Note Because of file dependencies, the most recent fix that contains these files may also contain additional files.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

When the SnaBase service starts, the SnaBase service determines the Host Integration Server Client type. To do this, the SnaBase service examines the ClientType registry value in the following registry subkey:If the ClientType registry value is set to Microsoft Windows 95, the SnaBase service does not copy the SnaBase registry parameters from the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SnaBase\Parameters registry subkey to the HKEY_CURRENT_USER\Software\Microsoft\SnaBase\Parameters registry subkey. Therefore, this problem occurs for any user who logs on to the Host Integration Server 2004 Client system after the user who performed the upgrade.

The Host Integration Server 2000 End-User Client sets the ClientType registry value to Windows 95 in the following registry subkey:Then, the ClientType registry value is copied to the HKEY_CURRENT_USER registry subtree for each user who logs on to the Host Integration Server 2000 End-User Client system when the user first starts the SnaBase service.

The Host Integration Server 2004 Client Setup and configuration processes do not remove any part of the previous Host Integration Server 2000 End-User Client settings that exist under the HKEY_CURRENT_USER registry subtree. Therefore, the incorrect ClientType registry value exists for any user who logs on to the Host Integration Server 2004 Client who had previously used the Host Integration Server 2000 End-User Client. However, the incorrect ClientType registry value does not exist for the user who installed the Host Integration Server 2004 Client on the system.

If the ClientType registry value is set to Microsoft Windows NT, the SnaBase service copies the SnaBase registry parameters from the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SnaBase\Parameters registry subkey to the HKEY_CURRENT_USER\Software\Microsoft\SnaBase\Parameters registry subkey. This problem does not occur in this case.

After you apply this hotfix, the SnaBase service first examines the ClientType registry value in the following registry subkey:The ClientType registry value in this registry subkey is updated to Windows NT when the Host Integration Server 2004 Client is installed. Therefore, the ClientType registry value will always have the correct value for the Host Integration Server 2004 Client. This prevents the problem.