TN3270 Server Disconnects Clients When a Popup Message Occurs

Last reviewed: March 19, 1998
Article ID: Q165148
The information in this article applies to:

- Microsoft SNA Server for Windows NT, version 3.0 - Microsoft SNA Server for Windows NT, version 3.0, Service Pack 1

SYMPTOMS

TN3270 Client disconnects from the TN3270 Server when a client receives a message. The message received by the client was sent by a host application from another user.

CAUSE

The TN3270E Server received an RQD message from the host that contained the EC (End Chain) indicator. The TN3270 server sent the data to the client, and changed its internal state to let the client have send-direction. The TN3270 server then receives data from the client before receiving a positive response from the client for the previous message. When the TN3270 server tries to send this data from the client across the RUI interface, it is rejected with the error LUA_RSP_BEFORE_SENDING_REQ.

RESOLUTION

The fix is to discard data received from the client if the client owes the server a positive response. The TN3270 Server service has been updated to correct this problem.

To resolve this problem, obtain the hotfix mentioned below. The updated file is:

   Tn3servr.exe

A further problem in this area has been corrected in an update since SNA Server 3.0 Service Pack 1 was released. A fix for this further problem is available from Microsoft.

STATUS

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

Microsoft has confirmed this to be a problem in SNA Server version 3.0 Service Pack 1. For a fix to SNA Server 3.0 Service Pack 1, please contct Microsoft.
Keywords          : kbbug3.00 kbfix3.00.sp1 prodsna snatn3270 kbfix3.00.sp2 kbnetwork
Version           : 3.0
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.