ACTIVATE_SESSION Event Not Signaled When the Session Ends (263096)

SYMPTOMS

When an APPC application calls the ACTIVATE_SESSION function to start a dependent LU6.2 session, the deactivation_event handle may not be signaled when the session ends. Specifically, if the APPC application starts two dependent LU6.2 sessions using the ACTIVATE_SESSION function, the wrong deactivation_event handle may be signaled when an UNBIND is received on one of the sessions. This problem does not occur with independent LU6.2.

NOTE: The ACTIVATE_SESSION API feature was added in Microsoft SNA Server 4.0 Service Pack 2. For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

195010 Activate_session/Deactivate_session Unavailable in SNA Server

CAUSE

This problem is caused by a bug in the ACTIVATE_SESSION function in the Winmgt32.dll file. When the client Winmgt32.dll receives the UNBIND notification from SNA Server, it searches its control blocks for a match on the session ID to determine which event to signal. Unfortunately, with dependent LUs the session ID is always zero (the same for both sessions). Therefore, the wrong event handle (associated with a different session) can be signaled.

RESOLUTION

To resolve this problem, obtain the latest service pack for SNA Server 4.0. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

215838 How to Obtain the Latest SNA Server Version 4.0 Service Pack

STATUS

Microsoft has confirmed that this is a problem in Microsoft SNA Server 4.0 SP2 and SP3.

This problem was first corrected in SNA Server 4.0 Service Pack 4.