TN3270: Unbind Hold Causes TN3270 Client 505 ErrorLast reviewed: April 17, 1997Article ID: Q151201 |
The information in this article applies to:
SYMPTOMSWhen you log onto a host system through the SNA Server version 2.11sp1 TN3270E service, the TN3270 user may receive a 505 error and lose his or her session. If this occurs, the SNA Server TN3270E service will log the following events into the Microsoft Windows NT application event log:
CAUSEWhen a 3270 user tries to access a host application through a host session manager, the session manager typically sends an UNBIND(bind forthcoming, or 0x02) followed by a BIND from the host application that was requested. The TN3270 server was not properly handling the UNBIND, which was causing its LUA RUI_WRITE call to fail. Therefore, it caused the TN3270 server to end the session. However, the TN3270 server now correctly ignores this error.
STATUSMicrosoft has confirmed this to be a problem in SNA Server versions 2.11 and 2.11.sp1. 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 MORE INFORMATIONThe host sends a data message, followed by an UNBIND (bind forthcoming). The TN3270 Server issues a response to the data message. However, by that point the RUI library has received the UNBIND (bind forthcoming) request, and has switched states to Session Terminating state. In this state it rejects the response message from the TN3270 Server, with the error LUA_STATE_CHECK / LUA_MODE_INCONSISTENCY.
|
Additional query words: prodsna sp1
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |