FIX: Event ID 102 when TI calls a host application that deallocates an APPC transaction in Host Integration Server 2010


Consider the following scenario:
  • You run a Windows-based application in a Microsoft Host Integration Server 2010 environment. The Windows-based application uses a Transaction Integrator (TI) method that calls an IBM host application over an SNA network connection.
  • The network connection uses Advanced Program-to-Program Communications (APPC).
  • The host application returns data to the Windows-based application, and then deallocates the APPC conversation.
In this scenario, the following event is logged in the Application log:
Event ID: 102:
Source: HIS Application Integration
HISETBG0001 Application Integrator has intercepted an exception in method MethodName. Following is the exception description: HISMSNA0015 The SNATransport encountered an error calling internal method CMALLC when processing method MethodName, LUName APPC LU Name, Error = 1."


This issue occurs because TI does not call the TP_ENDED verb at the end of an APPC transaction when the host application deallocates the APPC conversation. The internal Transaction Program (TP) control block for the APPC conversation is not released when the TP_ENDED verb is not called. Over time, the maximum number of TP control blocks is reached, which prevents additional APPC transactions from starting. Therefore, this issue occurs when the host application tries to allocate a new APPC conversation when the maximum number of TP control blocks is being used.


To resolve this problem, apply either the cumulative update or the hotfix that is mentioned in this article.

Cumulative update information

The fix that resolves this issue is included in cumulative update package 6 for Host Integration Server 2010. For more information about how to obtain the cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2752426 Cumulative update package 6 for Host Integration Server 2010

Hotfix information

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 website: 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.


To apply this hotfix, you must have cumulative update package 5 for Host Integration Server 2010 installed.

Restart information

You do not have to restart the computer after you apply this hotfix.

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.
For all supported x86-based versions of Host Integration Server 2010
File nameFile versionFile sizeDateTimePlatform
For all supported x64-based versions of Host Integration Server 2010
File nameFile versionFile sizeDateTimePlatform
Note Because of file dependencies, the most recent fix that contains these files may also contain additional files.


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

More Information

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

The maximum number of internal TP control blocks for each TI application process is 15,000. When a TI application reaches this limit, the application cannot allocate new APPC conversations.

ID articol: 2750609 - Ultima examinare: 28 nov. 2012 - Revizie: 1