Article ID: 174643
Article Last Modified on 7/16/2004
APPLIES TO
- Microsoft SNA Server 3.0, when used with:
- Microsoft Windows NT 4.0
- Microsoft SNA Server 2.11 Service Pack 1, when used with:
- Microsoft Windows NT 4.0
- Microsoft SNA Server 2.11 Service Pack 2, when used with:
- Microsoft Windows NT 4.0
- Microsoft SNA Server 3.0 Service Pack 4, when used with:
- Microsoft Windows NT 4.0
- Microsoft SNA Server 4.0, when used with:
- Microsoft Windows NT 4.0
This article was previously published under Q174643
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
Keywords: kbbug kbfix kbnetwork kbprogramming KB174643
