SNA APPC Event 93 Should Log Fully Qualified PLU Name

Last reviewed: March 11, 1998
Article ID: Q182266

The information in this article applies to:

Microsoft SNA Server versions 3.0, 3.0 Service Pack 1 (SP1), 3.0 SP2, and 4.0

SYMPTOMS

If a CPIC or APPC application attempts to allocate a conversation and specifies a fully qualified Primary (that is, Remote) APPC LU name (instead of the Remote LU alias), and the allocation attempt fails, the SNA Server APPC interface logs Event 93, but does not indicate the fully qualified PLU name in the event. For example:

   Event ID: 93
   Source:   SNA APPC Application
   Description:
   APPC local conversation start failed:
   Primary_rc   = <Return code>
   Secondary_rc = <Return code>
   TP_ID        = <Transaction program ID>
   Dest TP name = <Destination TP name>
   LU alias     = <Local APPC LU alias>
   PLU alias    = <Remote APPC LU alias>
   Mode name    = <APPC mode name>

   EXPLANATION%
   An attempt to start an APPC conversation locally using the verb
   [MC_]ALLOCATE failed.

CAUSE

The SNA Server Event 93 was not originally designed to log the fully qualified PLU name.

STATUS

Microsoft has confirmed this to be a problem in SNA Server 3.0, 3.0 Service Pack 1 (SP1), and 3.0 SP2. We are 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 4.0. A supported fix for SNA Server 4.0 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.

MORE INFORMATION

With this update applied, the SNA Server APPC DLL (Wappc32.dll) logs the

fully qualified PLU name, in addition to the other fields noted above.

Keywords          : kbbug3.00 kbbug3.00.sp1 snaappc snacpic snatp kbbug3.00.sp2 kbbug4.00
Version           : WINDOWS:3.0,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 11, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.