Article ID: 259149
Article Last Modified on 11/24/2003
APPLIES TO
- 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
This article was previously published under Q259149
SYMPTOMS
If multiple dependent local APPC LUs are configured with the Member of default outgoing local APPC LU pool check box enabled, and an APPC or CPIC application specifies a blank Local LU alias when it attempts to allocate a conversation to a Remote APPC LU, the SNA Server computer may fail to locate an available local LU and reject the Allocate request. When this occurs, the SNA Server computer selects a local LU that is already being used, instead of choosing an available local APPC LU in the pool.
If this occurs with an APPC application, the [MC_]ALLOCATE fails with the following error message:
A CPIC application fails with the following error message:
This problem can occur when the dependent local APPC LU pool is used to access a single Remote APPC LU, or multiple Remote APPC LUs.
NOTE: There are other causes for these failures other that this specific problem. For example, if the host rejects the INITSELF request to activate a session, or there is a problem with the connection, these error messages may also occur.
Also, when the Default pool check box is selected on a local APPC LU, the LU may be used to access any remote APPC LU if a blank local LU alias is provided by the APPC application. Therefore, the remote APPC LU (on the remote system) must be enabled to support sessions from any pooled local APPC LU.
CAUSE
When opening a pooled-dependent local APPC LU, the SNA Server incorrectly selects an LU that
- has not fully completed the session activation process due to an allocate request by a different user (for example, waiting for an LUSTAT reply)
- is already in session with a different Remote APPC LU
- has been deactivated by a DACTLU command and has not received a new ACTLU
RESOLUTION
To resolve this problem, obtain the latest service pack for SNA Server 4.0. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
215838 How to Obtain the Latest SNA Server Version 4.0 Service Pack
STATUS
Microsoft has confirmed that this is a problem in Microsoft SNA Server version 4.0, 4.0 SP1, 4.0 SP2 and 4.0 SP3.
This problem was first corrected in SNA Server 4.0 Service Pack 4.
Keywords: kbbug kbfix kbsna400presp4fix kbqfe kbsna400sp4fix KB259149
