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. COMTI 102 (2169) Error May Occur if the CSM Message Is Split Across Two Frames

COMTI 102 (2169) Error May Occur if the CSM Message Is Split Across Two Frames

View products that this article applies to.

Symptoms

When you use an information management system (IMS) open transaction management architecture (OTMA) remote environment type, you may receive the following error from the COM Transaction Integrator (COMTI) feature of Host Integration Server 2000:

Event Type: Error
Event Source: COMTI
Event Category: General
Event ID: 102

Description: (102) COM Transaction Integrator reported the following exception to the client:

Component: IMS_OTMA.Cedarbank.1
Method: getaccts

Exception description: (2169) The TCP transport encountered an unexpected error when checking for special IMS Connect or OTMA segments. Segment type=CSM message, Transaction CEDRBANK. IP Address: 169.4.14.11, port: 5005.

↑ Back to the top

Cause

When COMTI communicates with an IMS system by using OTMA or IMS Connect, COMTI expects a completion status message (CSM) to be sent from IMS that contains the response data from the host. This CSM message has a header and a footer that contain the string "*CSMOKY*" (without the quotation marks). If the CSM footer is split across two TCP/IP frames, a timing condition exists that may cause COMTI to incorrectly return the 102 (2169) error.

↑ Back to the top

Resolution

Service pack information

To resolve this problem, obtain the latest service pack for Microsoft Host Integration Server 2000. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
328152� How to obtain the latest service pack for Host Integration Server 2000

Hotfix information

The English version of this fix has the file attributes (or later) 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
   --------------------------------------------------------------
   24-Jun-2003  17:51  5.0.0.921          37,136  Capture.dll      
   24-Jun-2003  17:51  5.0.0.921         323,856  Cedrmsgs.dll     
   24-Jun-2003  17:51  5.0.0.921          33,040  Comticontext.dll  
   24-Jun-2003  17:51  5.0.0.921         147,728  Convert.dll      
   24-Jun-2003  17:51  5.0.0.921          74,000  Convertprim.dll  
   24-Jun-2003  17:51  5.0.0.921          33,040  Dpl1.dll         
   24-Jun-2003  17:51  5.0.0.921         823,568  Dtcob390.dll     
   24-Jun-2003  17:51  5.0.0.921          37,136  Playback.dll     
   24-Jun-2003  17:51  5.0.0.921          78,096  Readlib.dll      
   24-Jun-2003  17:51  5.0.0.921         123,152  Tadtlb.dll       
   24-Jun-2003  17:51  5.0.0.921         114,960  Tagen.dll        
   24-Jun-2003  17:51  5.0.0.921          82,192  Tranlu62.dll     
   24-Jun-2003  17:51  5.0.0.921         110,864  Trantcp.dll      
   24-Jun-2003  17:51  5.0.0.921          49,424  Turnaround.dll   
   24-Jun-2003  17:51  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 the preceding 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 at the beginning of this article. This problem was corrected in Microsoft Host Integration Server 2000 Service Pack 2.

↑ Back to the top

More information

A COMTI tracebits trace that captures this problem contains the following lines:
TCP Transport CheckForCSMMsgs Failed in recv with MSG_PEEK for an CSM.
TCP Transport ReceiveOTMA exited abnormally at point=11, hr=0x80040879
TCP Transport Receive exited abnormally at point=-2147219335, hr=-2147219335

↑ Back to the top

Keywords: KB822887, kbhotfixserver, kbqfe, kbfix, kbbug

↑ Back to the top

Article Info
Article ID : 822887
Revision : 3
Created on : 10/26/2005
Published on : 10/26/2005
Exists online : False
Views : 478