Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. FIX: A process that hosts a COMTI component may terminate unexpectedly after Event 102 messages are written to the Event log in Host Integration Server 2000

FIX: A process that hosts a COMTI component may terminate unexpectedly after Event 102 messages are written to the Event log in Host Integration Server 2000

View products that this article applies to.

Symptoms

In Microsoft Host Integration Server 2000, a process that hosts a Microsoft Component Object Model (COM) Transaction Integrator (COMTI) component may use an LU 6.2-type remote environment (RE). The process may terminate unexpectedly after the following messages are written to the Event log:
Event ID: 102
Source: COMTI
Description: (102) COM Transaction Integrator reported the following exception to the client:
Component: COMTI Component
Method: COMTI Method

Exception description: (1431) A RECEIVE_AND_WAIT verb received the following buffer, apparently USER_CONTROL_DATA. m_fLinkMode = 0. What_rcvd = 0000.

This may indicate an internal error in the runtime. Remove and reinstall COM Transaction Integrator. If the problem persists, contact Microsoft customer support.
Event ID: 102
Source: COMTI
Description: (102) COM Transaction Integrator reported the following exception to the client:
Component: COMTI Component
Method: COMTI Method

File: c:\depot1666\his2000_qfe\source\comti\runtime\tranlu62\tranlu62obj.cpp Line: 1078
EXPLANATION: COM Transaction Integrator detected an internal inconsistency and has terminated the process to avoid the risk of further corruption in this process. The problem may be caused by a bug in COM Transaction Integrator or by bugs in any other components running in the same package. This event will be followed in the log by an event from MTS, because of the exception generated by COM Transaction Integrator to force process termination.
Additionally, a Microsoft COM+ event that is similar to the following may be logged when the problem occurs:
Event ID: 4194
Source: COM+
Description: The system has called a custom component and that component has failed and generated an exception. This indicates a problem with the custom component. Notify the developer of this component that a failure has occurred and provide them with the information below.

Component Prog ID: Component Program ID
Server Application ID: Application ID
Server Application Name: Application Name

The serious nature of this error has caused the process to terminate.

Exception: Exception code
Address: Memory address
Call Stack: function call stack

↑ Back to the top

Cause

This problem occurs because COMTI incorrectly terminates its hosting process when it processes an APPC RECEIVE_AND_WAIT response that has the what_rcvd parameter set to 0x0000 (AP_NONE).

↑ Back to the top

Resolution

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   Date         Time   Version     Size     File name
   ---------------------------------------------------------
   04-Mar-2005  18:31  5.0.0.1031   37,136  Capture.dll      
   04-Mar-2005  18:31  5.0.0.1031  323,856  Cedrmsgs.dll     
   04-Mar-2005  18:31  5.0.0.1031   33,040  Comticontext.dll  
   04-Mar-2005  18:31  5.0.0.1031   28,944  Comtiperf.dll    
   04-Mar-2005  18:31  5.0.0.1031  147,728  Convert.dll      
   04-Mar-2005  18:31  5.0.0.1031   74,000  Convertprim.dll  
   04-Mar-2005  18:31  5.0.0.1031   33,040  Dpl1.dll         
   04-Mar-2005  18:31  5.0.0.1031  823,568  Dtcob390.dll     
   04-Mar-2005  18:31  5.0.0.1031  311,568  Mobase.dll       
   04-Mar-2005  18:31  5.0.0.1031   37,136  Playback.dll     
   04-Mar-2005  18:31  5.0.0.1031   78,096  Readlib.dll      
   04-Mar-2005  18:31  5.0.0.1031  123,152  Tadtlb.dll       
   04-Mar-2005  18:31  5.0.0.1031  119,056  Tagen.dll        
   04-Mar-2005  18:31  5.0.0.1031   82,192  Tranlu62.dll     
   04-Mar-2005  18:31  5.0.0.1031  114,960  Trantcp.dll      
   04-Mar-2005  18:31  5.0.0.1031   49,424  Turnaround.dll   
   04-Mar-2005  18:32  5.0.0.870   950,272  Componentbuilder.exe  
   29-Mar-2003  01:15              838,423  Comticb.chm
   29-Mar-2003  01:15              812,988  Resnapin.chm
Note Because of file dependencies, the most recent fix that contains these files may also contain additional files.

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

More information

After you apply this hotfix, COMTI no longer terminates its hosting process when it processes a RECEIVE_AND_WAIT response that has the what_rcvd parameter set to 0x0000 (AP_NONE).

If a RECEIVE_AND_WAIT response with the what_rcvd parameter set to 0x0000 (AP_NONE) is received, COMTI posts another RECEIVE_AND_WAIT verb to receive data from the IBM mainframe system. If the subsequent RECEIVE_AND_WAIT response returns with the what_rcvd parameter set to AP_NONE, COMTI logs the following message to the Event log instead of terminating the process:
Event ID: 102
Source: COMTI
Description: (102) COM Transaction Integrator reported the following exception to the client:

Component: COMTI Component
Method: COMTI Method

Exception description:
(1423) Unknown error, type 1; APPC error codes: Primary APPC Return Code, Secondary APPC Return Code; local LU Local LU Name ; host LU Remote LU Name ; remote TP TP Name. COM Transaction Integrator runtime encountered an unexpected communications error. Examine host logs for messages logged at the same time and contact Microsoft customer support.

↑ Back to the top

Keywords: KB895256, kbbug, kbfix, kbqfe, kbhotfixserver, kbautohotfix

↑ Back to the top

Article Info
Article ID : 895256
Revision : 6
Created on : 6/5/2006
Published on : 6/5/2006
Exists online : False
Views : 324