Unused Dependent LU6.2 Session Not Deactivated

Last reviewed: March 19, 1998
Article ID: Q168775

The information in this article applies to:

  • Microsoft SNA Server for Windows NT, versions 3.0 and 3.0 SP1

SYMPTOMS

After SNA Server initiates a dependent LU6.2 session for use by an SNA Server APPC or CPIC application, the dependent LU6.2 session remains active even after the LU6.2 conversation is de-allocated. This problem started occurring with SNA Server 3.0; this problem did not occur with SNA Server 2.x.

CAUSE

The SNA Server dependent APPC mode entry is configured with "Contention Winner Limit = 1;" SNA Server 3.0 is failing to override the contention winner status of a session when responding to a host BIND request. Because SNA Server is not negotiating to be the contention winner on the LU6.2 session, SNA Server does not initiate session shutdown after the LU6.2 conversation is de-allocated.

This problem was introduced in SNA Server 3.0 as a side effect of implementing support for dynamic partnership for APPC LUs.

WORKAROUND

To work around this problem:

  • Configure the host subsystem to be the contention loser.

STATUS

Microsoft has confirmed this to be a problem in SNA Server versions 3.0 and 3.0 SP1. This problem was corrected in the latest SNA Server version 3.0 U.S. Service Pack. For information on obtaining this Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K
Keywords          : prodsna snaappc snacpic snaserverservice kbfix3.00.sp2 kbnetwork
Version           : 3.0
Platform          : winnt
Issue type        : kbbug
Solution Type     : kbfix


================================================================================


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: March 19, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.