Registrations are now open. Join us today!
There is still a lot of work to do on the wiki yet! More information about editing can be found here.
Already have an account?

Microsoft KB Archive/925107

From BetaArchive Wiki

Article ID: 925107

Article Last Modified on 12/4/2007



APPLIES TO

  • Microsoft Host Integration Server 2004 Enterprise Edition



SYMPTOMS

A Microsoft Host Integration Server 2004 Transaction Integrator (TI) transaction that uses a two-phase commit (2-PC) protocol may fail when an application calls a TI method recursively. When this problem occurs, TI will log an event that resembles the following in the Application log:

Event ID: 102
Source: COMTI
Description: (102) COM Transaction Integrator reported the following exception to the client: Component: Component Name Method: Method Name Exception description: Exception description: (1227) COM Transaction Integrator was unable to enlist on the DTC transaction (HRESULT=0x8004d10d). If HRESULT is 8004d10E or 8004d10F, retry the request. If HRESULT is 8004d110, the transaction recovery has failed. Use the DTC Admin Console to manually resolve any pending transactions. For all other HRESULTs, start the COM Transaction Integrator Resynchronization Service. If COMTI Resynchronization Service is already active, contact Microsoft customer support.

RESOLUTION

Service pack information

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

940313 How to obtain the latest Host Integration Server 2004 service pack


Hotfix information

A supported hotfix is now 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. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:

File information

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 item in Control Panel.

File name File version File size Date Time Platform
Capture.dll 6.0.2044.0 25,600 14-Sep-2006 22:41 x86
Comticontext.dll 6.0.2044.0 25,600 14-Sep-2006 22:41 x86
Dcgen.dll 6.0.2044.0 99,840 14-Sep-2006 22:41 x86
Microsoft.hostintegration.ti.clientcontext.dll 6.0.2044.0 12,288 14-Sep-2006 22:40 x86
Microsoft.hostintegration.ti.dcgen.interop.dll 6.0.1701.0 4,096 14-Sep-2006 22:41 x86
Microsoft.hostintegration.ti.remotinginterceptor.dll 6.0.2044.0 15,872 14-Sep-2006 22:41 x86
Microsoft.hostintegration.ti.tracing.interop.dll 6.0.1701.0 4,608 14-Sep-2006 22:40 x86
Mobase.dll 6.0.2044.0 249,344 14-Sep-2006 22:40 x86
Playback.dll 6.0.2044.0 24,064 14-Sep-2006 22:41 x86
Tagen.dll 6.0.2044.0 96,256 14-Sep-2006 22:41 x86
Tracing.dll 6.0.2044.0 542,720 14-Sep-2006 22:40 x86
Tranlu62.dll 6.0.2044.0 53,760 14-Sep-2006 22:41 x86
Trantcp.dll 6.0.2044.0 104,448 14-Sep-2006 22:41 x86
Turnaround.dll 6.0.2044.0 34,304 14-Sep-2006 22:41 x86




STATUS

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

MORE INFORMATION

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates


Steps to reproduce this problem

  1. An application calls a COM+ package that is named PACKAGE1.
  2. The PACKAGE1 COM+ package calls a second COM+ package that is named PACKAGE2.
  3. The PACKAGE2 COM+ package calls a TI method that is named TI_METHOD1 during the call that is made by the PACKAGE1 COM+ package in step 2.
  4. The PACKAGE2 COM+ package makes a second call to the TI_METHOD1 method.
  5. The PACKAGE1 COM+ package calls a third COM+ package that is named PACKAGE3.
  6. The PACKAGE3 COM+ package calls a TI method that is named TI_METHOD2 during the call that is made by the PACKAGE1 COM+ package in step 5.
  7. The call to the TI_METHOD2 method fails. You receive event ID 102.


Keywords: kbhotfixserver kbqfe kbpubtypekc kberrmsg kbfix KB925107