MC_CONFIRMED Stops Following what_rcvd=AP_CONFIRM_DEALLOCATE

• Microsoft SNA Server, versions 3.0, 3.0 SP1, 3.0 SP2, 4.0

SYMPTOMS

If an APPC application is using confirmation processing on an LU6.2 conversation and receives an MC_RECEIVE_AND_WAIT response with a what_rcvd value of AP_CONFIRM_DEALLOCATE (0x0400), the application's call to MC_CONFIRMED may stop responding.

CAUSE

The SNA Server was not resetting an error indicator on an internal LU6.2 control block between reuses of the control block. So, if an error occurs on a prior conversation over a session (for example, following an APPC application issuing an [MC_]SEND_ERROR), the current conversation may fail unexpectedly when the current session is brought down incorrectly.

STATUS

Microsoft has confirmed this to be a problem in SNA Server versions 3.0, 3.0 SP1, and 3.0 SP2. Microsoft is researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Microsoft has confirmed this to be a problem in SNA Server version 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 Technical Support for more information.

Keywords          : prodsna snaappc snacpic snaprog snaserverservice
Version           : WINDOWS:3.0,3.0SP1,3.0SP2,4.0
Platform          : WINDOWS
Issue type        : kbbug
Solution Type     : kbfix