Dynamic Definition of Dependent APPC LUs Doesn't Work Properly

Last reviewed: March 18, 1998
Article ID: Q182577
The information in this article applies to:
  • Microsoft SNA Server, versions 3.0, 3.0 SP1, 3.0 SP2, 4.0

SYMPTOMS

If a dependent Local APPC LU is defined on two different connections (where each connection is configured to support Dynamic Definition of Remote APPC LUs), and the APPC application attempts to allocate a conversation over each Local LU to the same Remote APPC LU, the SNA INITSELF command for both dependent sessions flows over the first connection only.

CAUSE

Dynamic definition of dependent APPC LUs is not working correctly. If two remote APPC LUs are given the same name but defined to use different connections, the allocate to the second APPC LU causes the initself command to be sent across the wrong connection.

STATUS

Microsoft has confirmed this to be a problem in SNA Server versions 3.0 SP1 and 3.0 SP2. Microsoft is researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Microsoft has confirmed this to be a problem in SNA Server versions 3.0 and 4.0. A supported fix is now available for SNA Server versions 3.0 and 4.0, but has not been fully regression-tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Technical Support for more information.

Keywords          : prodsna snaappc snacpic snaprog snaserverservice
Version           : WINDOWS:3.0,3.0SP1,3.0SP2,4.0
Platform          : WINDOWS
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 18, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.