Article ID: 281507
Article Last Modified on 2/22/2007
APPLIES TO
- Microsoft SNA Server 4.0
- Microsoft SNA Server 3.0 Service Pack 2
- Microsoft SNA Server 3.0 Service Pack 3
- Microsoft SNA Server 3.0 Service Pack 4
- Microsoft SNA Server 4.0
- Microsoft SNA Server 4.0 Service Pack 1
- Microsoft SNA Server 4.0 Service Pack 2
- Microsoft SNA Server 4.0 Service Pack 3
- Microsoft SNA Server 4.0 Service Pack 4
- Microsoft Host Integration Server 2000 Standard Edition
This article was previously published under Q281507
SYMPTOMS
If multiple, dependent local Advanced Program-to-Program Communications (APPC) LUs are configured with the Member of default outgoing local APPC LU pool check box enabled, and an APPC or Common Programming Interface for Communications (CPIC) application specifies a blank Local LU alias when it attempts to allocate a conversation to a Remote APPC LU, the APPC or CPIC application may fail to get a LU 6.2 session.
The exact symptoms depend upon the APPC or CPIC application. If the application is designed to wait until an LU 6.2 (APPC) session is available, the application may appear to stop responding (hang) while it waits for an available LU 6.2 session. If the application is designed to time out when a session is not available within a certain period of time, the underlying APPC [MC_]ALLOCATE may fail with the following error message:
A CPIC application may fail with the following error message:
CAUSE
The SNA Server may choose a pooled, dependent Local APPC LU that is defined on a host connection where the requested Remote APPC LU is not explicitly defined. This occurs even though there is a pooled Local APPC LU available on another host connection where the requested Remote APPC LU is explicitly defined.
This can only occur if the host connection where the Remote APPC LU is not explicitly defined has the Supports Dynamic Remote APPC LU Definition option selected in its connection properties in SNA Manager.
RESOLUTION
SNA Server 4.0
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Microsoft SNA Server version 4.0 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this fix should have the following file attributes or later:
| File name | Date | Time |
|---|---|---|
| Snaservr.exe | 12/05/2000 | 11:24AM |
NOTE: Because of file dependencies, the most recent fix that contains the preceding files may also contain additional files.
Host Integration Server 2000
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
The English version of this fix should have the following file attributes or later:
| File name | Date | Time |
|---|---|---|
| Snaservr.exe | 12/05/2000 | 11:24AM |
NOTE: Because of file dependencies, the most recent fix that contains the preceding files may also contain additional files.
WORKAROUND
If there is no need to dynamically create remote APPC LUs, disabling Supports Dynamic Remote APPC LU Definition in the connection properties prevents this problem from occurring.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Host Integration Server 2000 Service Pack 1.
Additional query words: Snaservr exe sp1 sp2 sp3 sp4 his service pack 1 2 3 4 HIS 2000
Keywords: kbbug kbfix kbhostintegserv2000sp1fix kbhostintegserv2000presp1fix KB281507
