Microsoft KB Archive/935217

From BetaArchive Wiki

Article ID: 935217

Article Last Modified on 12/4/2007



APPLIES TO

  • Microsoft Host Integration Server 2004 Enterprise Edition
  • Microsoft Host Integration Server 2004 Standard Edition
  • Microsoft Host Integration Server 2006




SYMPTOMS

When a Microsoft Host Integration Server 2004 or Host Integration Server 2006 Transaction Integrator application tries to connect to an IBM IMS application that uses an IMS Connect Remote Environment (RE) type, an error message that resembles the following is logged in the Application log:

Event ID: 102
Source: COMTI
Description: (102) COM Transaction Integrator reported the following exception to the client:
Component: <ComponentName>
Method: <MethodName>
Exception description: (2166) The TCP transport, using IMS Connect or OTMA, received a Request Status Message; Return Code=8, Reason Code=56. IP Address: <TCP/IP Address>, port: <PortNumber>, transid: <TRANS ID>. Return description: Error detected by IMS Connect. Reason description=Duplicate Client ID used; the client ID is currently in use

This problem is most likely to occur when the Transaction Integrator application is configured to use persistent connections.

CAUSE

This problem occurs because the algorithm that Transaction Integrator uses to create the IRM_CLIENTID value that is included in the IMS Connect header may generate duplicate values.

RESOLUTION

Host Integration Server 2004

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:



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
Convertprimex.dll 6.0.2085.0 75,264 20-Apr-2007 00:01 x86
Dcgen.dll 6.0.2085.0 99,840 20-Apr-2007 00:02 x86
Dpl1.dll 6.0.2085.0 20,480 20-Apr-2007 00:02 x86
Snanls.dll 6.0.2085.0 77,824 19-Apr-2007 23:58 x86
Sysctblj.exe 6.0.2085.0 30,720 19-Apr-2007 23:58 x86
Sysctblk.exe 6.0.2085.0 29,696 19-Apr-2007 23:58 x86
Sysctbls.exe 6.0.2085.0 29,696 19-Apr-2007 23:58 x86
Sysctblt.exe 6.0.2085.0 29,696 19-Apr-2007 23:58 x86
Tagen.dll 6.0.2085.0 96,256 20-Apr-2007 00:02 x86
Tranlu62.dll 6.0.2085.0 53,760 20-Apr-2007 00:02 x86
Trantcp.dll 6.0.2085.0 104,960 20-Apr-2007 00:02 x86
Trnsdt.dll 6.0.2085.0 10,752 19-Apr-2007 23:58 x86
Trnsdtj.dll 6.0.2085.0 7,680 19-Apr-2007 23:58 x86
Trnsdtk.dll 6.0.2085.0 6,656 19-Apr-2007 23:58 x86
Trnsdts.dll 6.0.2085.0 6,144 19-Apr-2007 23:58 x86
Trnsdtt.dll 6.0.2085.0 6,656 19-Apr-2007 23:58 x86

Host Integration Server 2006

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:

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.

Host Integration Server 2006, 32-bit editions
File name File version File size Date Time Platform
Tranlu62.dll 7.0.2813.0 90,976 14-Apr-2007 01:59 x86
Trantcp.dll 7.0.2813.0 149,848 14-Apr-2007 01:59 x86
Host Integration Server 2006, 64-bit editions
File name File version File size Date Time Platform Service branch
Tranlu62.dll 7.0.2813.0 90,976 14-Apr-2007 01:59 x86 Not Applicable
Trantcp.dll 7.0.2813.0 149,848 14-Apr-2007 01:59 x86 Not Applicable
Tranlu62.dll 7.0.2813.0 90,976 14-Apr-2007 01:59 x86 SYSWOW
Trantcp.dll 7.0.2813.0 149,848 14-Apr-2007 01:59 x86 SYSWOW


STATUS

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

MORE INFORMATION

After you apply this hotfix, Transaction Integrator sends an IRM_CLIENTID value that consists of eight SPACE characters.

The IRM_CLIENTID parameter specifies the name of the client ID that IMS Connect uses. IMS Connect generates a unique client ID when IMS Connect receives an IRM_CLIENT value of eight SPACE characters.

For more information, 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


Keywords: kberrmsg kbfix kbqfe kbpubtypekc kbhotfixserver KB935217