SNA Server Incorrectly Flips Sense Code Sent by RUI App.

Last reviewed: February 1, 1996
Article ID: Q138855
The information in this article applies to:
  • Microsoft SNA Server for Windows NT, version 2.11

SYMPTOMS

Sense codes from a BIND negative response sent by an RUI application are sent incorrectly by SNA Server. For example, if an RUI application rejects a BIND request with a sense code of 0821000E, a SNA trace shows SNA Server sending a sense code of 2108000E instead.

For LUA applications, the primary sense code is flipped and the secondary sense code stays in the correct format.

For 3270 Emulator Interface Specification (3270EIS) applications, the primary sense code stays in the correct format and the secondary sense code is flipped.

CAUSE

When an RUI application closes a session with a BIND negative response, or an UNBIND request and attaches sense codes, the primary sense code is flipped when it is sent out by SNA Server.

RESOLUTION

Microsoft has modified the files, SNASERVR.EXE and WINRUI32.DLL, with the updated versions that correct this problem.

STATUS

Microsoft has confirmed this to be a problem in SNA Server for Windows NT. This problem was corrected in the latest SNA Server for Windows NT, 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


KBCategory: kbnetwork kbbug2.11
KBSubcategory: ntnetserv
Additional reference words: prodsna 2.11


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: February 1, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.