Dependent LU6.2 sessions may use the wrong LUs when multiple Remote LUs have the same LU alias (837314)


The information in this article applies to:

  • Microsoft Host Integration Server 2000
  • Microsoft Host Integration Server 2000 SP1

SYMPTOMS

When you use dependent LU6.2 sessions and you configure multiple remote LUs with the same name on different connections, the Microsoft SNA Server service (Snaservr.exe) may use the wrong remote LU and may try to establish a session by using the wrong connection.

CAUSE

This problem occurs because the resource location mechanism incorrectly allows an incorrect LU to be chosen when the local LU name is not blank in the ALLOCATE verb.

RESOLUTION

Service pack information

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

328152 How to obtain the latest service pack for Host Integration Server 2000

Hotfix information

The English version of this hotfix has the file attributes (or later) 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. 
   Date         Time   Version    Size       File name
   ------------------------------------------------------
   03-Mar-2004  22:37  5.0.0.966    471,312  Snaservr.exe
   03-Mar-2004  22:37  5.0.0.966  1,061,136  Trcservr.exe
Note Because of file dependencies, the most recent fix that contains these files may also contain additional files.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was corrected in Microsoft Host Integration Server 2000 Service Pack 2.

MORE INFORMATION

An application that uses the Advanced Program-to-Program Communications (APPC) programming interface issues an ALLOCATE verb to a dependent local LU. If Host Integration Server is configured to use multiple remote LUs with the same name on different connections, the node sends the INIT-SELF command from a different local LU on a different connection.

This problem was introduced after new support for load balancing of APPC sessions was added in Host Integration Server 2000. That code incorrectly allows a different LU to be chosen. However, this behavior should only occur if the ALLOCATE verb is issued with a blank local LU name (default LU pool).
Modification Type:MinorLast Reviewed:10/26/2005
Keywords:kbHotfixServer kbQFE kbHotfixServer kbQFE kbHostIntegServ2000sp2fix kbQFE kbfix kbbug KB837314 kbAudEndUser
©2004 Microsoft Corporation. All rights reserved.