APPC or CPIC Programs Stop Working

 Last reviewed: March 10, 1998
Article ID: Q178315
The information in this article applies to:
  • Microsoft SNA Server version 4.0

SYMPTOMS

An APPC or CPIC application that attempts to use a fully qualified Remote APPC LU name instead of a Remote APPC LU alias will not work on the initial retail release of SNA Server 4.0. The following symptoms occur when an APPC or CPIC application attempts to use a fully qualified Remote APPC LU name:

  • An APPC application's [MC_]ALLOCATE request fails with primary_rc = AP_COMM_SUBSYSTEM_NOT_LOADED (0xF004)
  • A CPIC application's CMALLC request fails with CM_PRODUCT_SPECIFIC_ERROR (rc = 20).

This problem does not occur if the APPC or CPIC application specifies a Remote APPC LU alias in its [MC_]ALLOCATE or CMALLC request.

CAUSE

SNA Server 4.0 implements the ability to limit user access to Remote APPC LU's. However, during implementation of this feature, APPC or CPIC application access to fully qualified Remote APPC LU names was inadvertently disallowed, even if Remote APPC LU security is not enabled using SNA Server Manager.

WORKAROUND

A fix to this problem is available from Microsoft. To work around this problem without obtaining this fix, do one of the following:

  • Modify the APPC application to use a Remote APPC LU alias.

-OR-
  • Change the CPIC side information name to use a Remote APPC LU alias instead of using a fully qualified Remote APPC LU name.

STATUS

Obtain the following fix or wait for the next SNA Server 4.0 service pack.

This fix should have the following timestamp: 

   12/15/97  12:00a      214,816  <snaroot>\system\snabase.exe
   12/15/97  12:00a      191,120  <ntroot>\symbols\exe\snabase.dbg

   NOTE: SNAVER internal build number for snabase.exe is 4.0.0.501. The
   internal build number for all retail SNA Server 4.0 modules is
   4.0.0.500.
Microsoft has confirmed this to be a problem in SNA Server version 4.0. 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 Technical Support for more information. 
Keywords          : snaappc snacpic snaprog kbbug4.00
Version           : WINDOWS: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 10, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.