SLI_OPEN May Fail With LUA_STATE_CHECK/LUA_NO_SLI_SESSIONLast reviewed: February 9, 1998Article ID: Q180708 |
The information in this article applies to:
SYMPTOMSWhen using the SNA Server Win32 SLI API interface, an SLI application may receive the following SLI_OPEN error when attempting to reopen a dependent session:
primary_rc = 0x0002 (LUA_STATE_CHECK) secondary_rc = 0x00000034 (LUA_NO_SLI_SESSION)The following API and message flow summarizes the behavior that may be observed in SNA Server API and 3270 message traces:
SLI Program SLI API RUI API SNA Server /Host =========== ======= ======= ================= <SLI program in session>SLI_BID -> SLI_SEND (send host logoff) -> <- SLI_SEND OK <- UNBIND <- SLI_BID (LUA_SESSION_FAILURE) RUI_TERM -> <- RUI_TERM OKSLI_OPEN -> <- SLI_OPEN ERROR: LUA_STATE_CHECK, LUA_NO_SLI_SESSION CAUSEThe SNA Server SLI interface was incorrectly locating an SLI control block based on the LU name, which is not always unique. Instead, SLI should have been checking the session ID which is always unique.
STATUSMicrosoft has confirmed this to be a problem in SNA Server 3.0, 3.0 Service Pack 1 (SP1), 3.0 SP2, and 4.0. A supported fix is now available, but has not been fully regression-tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Product Support Services for more information. Keywords : kbbug3.00 kbbug3.00.sp1 prodsna snalua snaprog kbbug3.00.sp2 kbbug4.00 Version : WINDOWS:3.0,3.0SP1,3.0SP2,4.0 Platform : WINDOWS Issue type : kbbug Solution Type : kbfix |
================================================================================
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |