Invalid Sense Code Returned In APPC Allocate Response

 Last reviewed: April 17, 1997
Article ID: Q148603
The information in this article applies to:
  • Microsoft SNA Server for Windows NT, versions 2.0, 2.1, 2.11 and 2.11 Service Pack 1

SYMPTOMS

If the SNA Server connection (supporting the APPC LU's being requested) does not start for any reason, the SNA Server returns an invalid sense code in the SENSE_DATA field. However, if the remote system receives an actual SNA sense code during the LU6.2 session activation, SNA Server returns the correct sense code in the [MC_]ALLOCATE response.

CAUSE

If a connection fails, the SNA Server service returns the value of an uninitialized variable to the APPC interface, instead of a valid sense code.

RESOLUTION

To correct this problem, apply the fix mentioned below.

STATUS

Microsoft has confirmed this to be a problem in SNA Server versions 2.0, 2.1, 2.11, and 2.11 Service Pack 1. This problem was corrected in the latest Microsoft SNA Server 2.11 U.S. Service Pack. For information on obtaining the service pack, query on the following word in the Microsoft Knowledge Base (without the spaces): 

   S E R V P A C K

Additional query words: prodsna SP1
Keywords : kbbug2.00 kbbug2.10 kbbug2.11 kbbug2.11.sp1 kbnetwork ntnetserv
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.