SNA Server APPC Returns AP_BAD_PARTNER_LU_ALIAS in Error

 Last reviewed: November 6, 1997
Article ID: Q170422
The information in this article applies to:
  • Microsoft SNA Server, versions 2.11 and 3.0

SYMPTOMS

If an APPC (or CPIC) application attempts to allocate a conversation using a Local APPC LU alias that is owned by an SNA Server that is not running, SNA Server incorrectly returns the following error to the APPC application: 

   primary_rc = AP_PARAMETER_CHECK (0x0001)
   secondary_rc = AP_BAD_PARTNER_LU_ALIAS (0x0000015B)
APPC should return primary_rc = AP_COMM_SUBSYSTEM_NOT_LOADED (0xF004), to indicate that the server is not running, instead of indicating that the partner LU alias is invalid.

CAUSE

This problem was introduced in SNA Server 3.0 as part of the new support for dynamic APPC LU partnering, where the wrong initial return code was being set.

RESOLUTION

An update to SNA Server 3.0 (post SP1) is available to correct this problem. The updated module is SNASERVR.EXE.

STATUS

Microsoft has confirmed this to be a problem in SNA Server version 3.0 and 3.0 SP1.

A supported fix is now available 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 Product Support Services for more information.

Additional query words: cedar
Keywords : prodsna snaappc snacpic snaprog kbbug kbnetwork kbprg
Version : 2.11 3.0
Platform : winnt

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: November 6, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.