SNA Server RUI Application Unable To Send NSPE +RSP

Last reviewed: March 19, 1998
Article ID: Q174643
The information in this article applies to:
  • Microsoft SNA Server for Windows NT, versions 2.11, 2.11 SP1, 2.11 SP2,

        3.0, and 3.0 SP1
    

SYMPTOMS

If an RUI application receives a NSPE request (NS Procedure Error) from the host and submits a positive response, the SNA Server never sends the NSPE +RSP to the host. This problem was initially reported by an application developer writing to the SNA Server Win32 LUA RUI programming interface. When this problem occurs, no events are generated and there are no other problems encountered, except that the host does not receive a NSPE +RSP on the SSCP-LU session.

CAUSE

SNA Server did not support sending responses to Network Services (NS) RUs via the RUI library. NS RU responses each require a 3-byte NS Header, though the RUI library only accomodated a 1-byte command.

RESOLUTION

The SNA Server RUI interface has been enhanced to support 3-byte response RU's if the following conditions are met:

- the response is on the LU-SSCP session - the FI bit is set in the RH - the RU category is FMD

STATUS

Microsoft has confirmed this to be a problem in SNA Server version 2.11, 2.11 SP1, 2.11 SP2, 3.0, and 3.0 SP1. This problem has been corrected in SNA Server 3.0 SP2. 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:
Keywords : kbbug2.11 kbbug2.11.sp1 kbbug2.11.sp2 kbbug3.00 kbbug3.00.sp1 prodsna snalua snaprog kbfix3.00.sp2 kbnetwork kbprg kbbuglist
Version : 2.11 2.11.SP1 2.11.SP2 3.0 3.0.SP1
Platform : winnt
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 19, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.