COMTI [MC_]ALLOCATE Hangs After Host Rejects SNA Server BIND Request

ID: Q218173

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).

NOTE: The COMTI feature included in SNA Server 4.0, 4.0 SP1, and 4.0 SP2 only requests contention winner sessions.


CAUSE

The 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.


RESOLUTION

SNA Server 3.0

To 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


SNA Server 4.0

File name Date Time
Snaservr.exe 02/16/99 16:06
Snaevent.dll 02/16/99 16:01
Trcservr.exe 02/16/99 16:06

NOTE: Trcservr.exe is only used for troubleshooting purposes as requested by Microsoft support personnel and does not need to be applied to the target system.

NOTE: Because of file dependencies, the most recent fix that contains the above files may also contain additional files.



NOTE: If this product was already installed on your computer when you purchased it from the Original Equipment Manufacturer (OEM) and you need this fix, please call the Pay Per Incident number listed on the above Web site. If you contact Microsoft to obtain this fix, and if it is determined that you only require the fix you requested, no fee will be charged. However, if you request additional technical support, and if your no-charge technical support period has expired, or if you are not eligible for standard no-charge technical support, you may be charged a non-refundable fee.

For more information about eligibility for no-charge technical support, see the following article in the Microsoft Knowledge Base:
Q154871 Determining If You Are Eligible for No-Charge Technical Support


WORKAROUND

The 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.


STATUS

Microsoft has confirmed this to be a problem in SNA Server 4.0, 4.0 SP1, 4.0 SP2. This problem was first corrected in SNA Server 3.0 Service Pack 4.

Additional query words: 


Keywords          : 
Version           : WINDOWS:4.0,4.0SP1,4.0SP2
Platform          : WINDOWS 
Issue type        : kbbug

Last Reviewed: July 8, 1999