The information in this article applies to:
SYMPTOMS
A COM Transaction Integrator (COMTI) request may stop responding (hang) and
fail to complete if the host rejects SNA Server's BIND request. Although
this problem has been observed when using COMTI, this problem can occur
with any APPC or CPIC application that attempts to allocate a conversation
by setting rtn_ctl = AP_WHEN_CONWINNER_ALLOCATED (to request an LU6.2
conversation over a contention winner session). CAUSEThe SNA Server was failing to de-queue a client allocation request for a contention winner session when the remote system rejects the request. This occurs only when the host has also initiated LU6.2 sessions to SNA Server where SNA Server is the contention loser. RESOLUTIONSNA Server 4.0To resolve this problem, obtain the latest service pack for SNA Server version 4.0. For additional information, please see the following article in the Microsoft Knowledge Base:Q215838 How to Obtain the Latest SNA Server Version 4.0 Service Pack SNA Server 3.0To resolve this problem, obtain the latest service pack for SNA Server version 3.0. For additional information, please see the following article in the Microsoft Knowledge Base:Q184307 How to Obtain the Latest SNA Server Version 3.0 Service Pack WORKAROUNDThe problem can be avoided by correcting the host system configuration to prevent the SNA Server BIND request from being rejected. When this problem occurs, the host successfully establishes LU6.2 sessions where SNA Server is the contention loser, but rejects SNA Server requests to establish an LU6.2 contention winner session. STATUSMicrosoft has confirmed this to be a problem in SNA Server versions 3.0 and 4.0. This problem was first corrected in SNA Server version 3.0 Service Pack 4 and SNA Server version 4.0 Service Pack 3. Additional query words:
Keywords : sna3sp4fix sna4sp3fix |
Last Reviewed: September 29, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |