Article ID: 2771292 - View products that this article applies to.
When you install Microsoft Host Integration Server 2010, the PermanentServers registry value is created in the following location:
The Setup process creates the PermanentServers value by using the correct value type of REG_MULTI_SZ (Multi-String Value).
However, when you use the Host Integration Server 2010 Configuration tool to configure a Host Integration server, the PermanentServers registry value is changed to use a value type of REG_EXPAND_SZ (Expandable String Value).
The SnaBase service cannot read the value data that is added to the PermanentServers value when it is defined by using a value type of REG_EXPAND_SZ. This causes the SnaBase service not to service the Host Integration Service updates to the TCP/IP addresses or the NetBIOS name updates that you add to the PermanentServers registry value.
This problem occurs because the Host Integration Server 2010 Configuration Tool (configuration.exe) incorrectly changes the value type of the PermanentServers registry value.
Cumulative update informationThe fix that resolves this issue is included in cumulative update package 6 for Host Integration Server 2010. For more information about how to obtain the cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/2752426/ )Cumulative update package 6 for Host Integration Server 2010
To work around this problem, run a repair of the Host Integration Server installation to reset the PermanentServers registry value type to REG_MULTI_SZ. To do this, follow these steps:
Note The Repair process does not change the Host Integration Server configuration. If the Configuration Tool is used to make configuration changes at a later date, the PermanentServers registry value type will be changed to the incorrect setting. Therefore, you may have to run the repair process again.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
The SnaBase service dynamically maintains a list of services that are running on all Host Integration Servers in its Host Integration Server sub domain. This list of services is called the Service Table. The SnaBase service on each Host Integration Server periodically communicates with other Host Integration Servers in the sub domain. The SnaBase service notifies other servers about the SNA services that are supported by the server and whether the services are running. This communication process keeps all Host Integration Servers updated about any configuration change that is made or any action that is being taken in the Host Integration Server sub domain.
For example, when the SNA Server service (snaservr.exe) is stopped on a Host Integration Server system, this is a change that the other Host Integration Servers have to know about. The Host Integration Servers also send these updates at set intervals even if no changes occur. The interval is configurable by using the Mean time between server broadcasts option in the SNA Server Manager (this option is under the Host Integration Sub domain properties). The default time value of the Mean time between server broadcasts option is 70 seconds. If a Host Integration Server does not receive periodic updates from the other Host Integration Servers in the sub domain, the Host Integration Server will age-out the service table entries for the Host Integration Servers from which it is not receiving updates.
Under typical scenarios, each Host Integration Server sends the status updates to all the other Host Integration Servers without using the PermanentServers registry value. However, there are scenarios in which these updates are not always sent to all the Host Integration Servers. In these scenarios, you can update the PermanentServers registry value. Your update must include the TCP/IP addresses or NetBIOS names of the Host Integration Servers to which you want the local SnaBase service always to send updates. Your updates are sent even if the periodic status updates are not being sent as expected.
Article ID: 2771292 - Last Review: November 28, 2012 - Revision: 1.0