Preventing Repeated APPC Session Activation Failures Event 18

Last reviewed: April 17, 1997
Article ID: Q150959

The information in this article applies to:

Microsoft SNA Server for Windows NT, versions 2.0, 2.1, and 2.11

SUMMARY

When SNA Server is configured with independent APPC LU6.2 sessions, SNA Server will automatically initiate LU6.2 session negotiation with the remote system for each configured LU/LU/mode pair when the connection is started. The independent LU6.2 LUs require an initial SNA Service Manager (SNASVCMG) mode BIND between the LUs in order for session limit (CNOS) negotiation to take place.

If a BIND error is received on this mode, SNA Server will log the following Event 18:

NOTE: It will continue to retry.

   Event 18

   APPC session activation failure: BIND negative response or UNBIND
   request received

   Sense data = <sense data>
   Connection = <connection name>
   LU alias = <local LU alias>
   PLU alias = <remote LU alias>
   Mode name = SNASVCMG

If the remote system is not currently active (for example, if the remote system is CICS though the CICS region has been brought down for maintenance), the Event 18 will be logged for each BIND failure.

The SNA Server NOINITCNOS registry setting can be set to prevent these repeated Event 18 errors.

MORE INFORMATION

SNA Server supports a registry entry that disables automatic LU6.2 session negotiation using the NOINITCNOS registry setting, as documented in the SNA Server “Reference Guide,” page 195 (in Appendix C). This will cause SNA Server to perform LU6.2 session negotiation only when an application requests a conversation over an LU/LU pair.

   HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/Snaservr
   /Parameters/

   NOINITCNOS: REG_SZ: YES

If this entry is not present in the registry, it defaults to No.

Additional query words:
Keywords : kbnetwork kbusage prodsna
Version : 2.0 2.1 2.11
Platform : WINDOWS

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