FIX: A COM Transaction Integrator call may fail intermittently, and a "(2116) The parameters passed in the ITransport::Connect method were not valid for TCP transport" error message may be written to the application event log in Host Integration Server (894548)


The information in this article applies to:

  • Microsoft Host Integration Server 2000
  • Microsoft Host Integration Server 2000 SP1
  • Microsoft Host Integration Server 2000 SP2
  • Microsoft Host Integration Server 2004

SYMPTOMS

In Microsoft Host Integration Server 2004 and in Host Integration Server 2000, a COM Transaction Integrator (COMTI) call may fail intermittently, and the following error message may be written to the application event log:
Event Type: Error
Event Source: COMTI
Event Category: General
Event ID: 102
Date: Date
Time: Time
User: UserName
Computer: ComputerName
Description:
(102) COM Transaction Integrator reported the following exception to the client:

Component: ComponentName
Method: MethodName

Exception description:
(2116) The parameters passed in the ITransport::Connect method were not valid for TCP transport. The RemoteTp parameter contained the data: MethodName. Contact Microsoft customer support.

CAUSE

The COMTI runtime examines the GUID for the COMTI Remote Environment to determine the transport to use. This GUID check is case sensitive. The problem that is mentioned in the "Symptoms" section occurs when this GUID check fails because of case sensitivity.

RESOLUTION

Host Integration Server 2000

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Host Integration Server 2000 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

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
   -----------------------------------------------------
   22-Apr-2005  01:23  5.0.0.2061  323,856  Cedrmsgs.dll     
   22-Apr-2005  01:23  5.0.0.2061  311,568  Mobase.dll       
   22-Apr-2005  01:23  5.0.0.2061  119,056  Tagen.dll        
   22-Apr-2005  01:23  5.0.0.2061   82,192  Tranlu62.dll     
   22-Apr-2005  01:23  5.0.0.2061  114,960  Trantcp.dll
Note Because of file dependencies, the most recent fix that contains these files may also contain additional files.

Host Integration Server 2004

No hotfix is currently available.

STATUS

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

MORE INFORMATION

When you use Tracebits.exe to conduct an internal Host Integration Server 2000 trace, the trace contains the following information:
14:53:26.400 12000 CStateMachObject::Initialize entered.
14:53:26.400 12026 CStateMachObject::Initialize CLSID={6F5169CE-6835-11D0-8C39-00C04FC2F9BC}.  
14:53:26.400 12025 CStateMachObject::Initialize Not a TCP/IP RE.
Note The CLSID={6F5169CE-6835-11D0-8C39-00C04FC2F9BC} GUID contains "11D0" instead of the expected "11d0."

The class ID (CLSID) that appears is a valid COMTI TCP/IP remote environment. However, because the CLSID contains "11D0" instead of "11d0," the CLSID does not match a valid TCP/IP remote environment. The method call fails and the Tracebits.exe trace contains the following information:
14:53:26.400  18003 TCP Transport Connect entered, Remote TP = METHOD_NAME, bRefreshTme = 0
14:53:26.400  18084 TCP Transport ExtractTCPParameters: Entry: METHOD_NAME.
14:53:26.400  18084 TCP Transport ExtractTCPParameters: Exit no parameters to extract.
14:53:26.400  18006 TCP Transport Connect exited abnormally, at point=2,  hr=80040844
14:53:26.400  12013 State Machine Bind failed

To enable Host Integration Server 2000 tracing by using Tracebits.exe, follow these steps:
  1. Click Start, click Run, type tracebits, and then click OK
  2. In the COMTI Trace Settings window, click to select the following check boxes to enable trace items:
    • General
    • Transport
    • COMTI Proxy
  3. Click Save.
Note Typically, traces are written to the Program Files\Host Integration Server\Traces folder.

After you take the traces, turn off tracing by clicking Clear all in the COMTI Trace Settings window.

Note COMTI Tracebits.exe trace files do not have a size limit. Therefore, make sure that you turn off tracing when the trace is finished.
Modification Type:MinorLast Reviewed:7/25/2006
Keywords:kbHotfixServer kbQFE kberrmsg kbHIS2004 kbhis2000 kbfix kbbug kbpubtypekc KB894548 kbAudDeveloper
©2004 Microsoft Corporation. All rights reserved.