Article ID: 180708
Article Last Modified on 3/16/2005
APPLIES TO
- Microsoft SNA Server 3.0 Service Pack 4
- Microsoft SNA Server 4.0
- Microsoft SNA Server 3.0 Service Pack 2
- Microsoft SNA Server 4.0
This article was previously published under Q180708
SYMPTOMS
When 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:
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 OK
SLI_OPEN ->
<- SLI_OPEN ERROR: LUA_STATE_CHECK, LUA_NO_SLI_SESSION
CAUSE
The 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.
STATUS
Microsoft has confirmed this to be a problem in SNA Server 3.0, 3.0 Service Pack 1 (SP1), 3.0 SP2, and 4.0.
This problem was corrected in the latest SNA Server versions 3.0 and 4.0 U.S. Service Packs. For information on obtaining these Service Packs, query on the following word in the Microsoft Knowledge Base (without the spaces):
S E R V P A C K
Keywords: kbbug kbfix KB180708
