FIX: Incorrect Transaction Integrator registry parameters result in nondescript error messages


Consider the following scenario:
  • You deploy a Transaction Integrator (TI) application.
  • You have defined one or more Transaction Integrator registry parameters to alter some Transaction Integrator functionality.

In this scenario, if any of the TI registry parameters are defined incorrectly, you may encounter nondescript error messages when you run the Transaction Integrator application.

For example, the error messages do not provide any information that enables you to identify that an incorrect registry parameter is the cause of the run-time error.


Hotfix information

The hotfix that resolves this issue is included in cumulative update package 3 for Microsoft 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:
2654652 Cumulative update package 3 for Host Integration Server 2010


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 update, Transaction Integrator returns error messages that provide details about incorrect registry parameters that cause the run-time errors.

The following is an error message that Transaction Integrator logs after the TrimTrainingNulls registry parameter is incorrectly defined:
Event ID: 102
Source: HIS Application Integration
HISETBG0001 Application Integrator has intercepted an exception in method Unknown.  Following is the exception description: The type initializer for 'Microsoft.HostIntegration.TI.RuntimeCallContext' threw an exception.

Note The actual error message that is returned when this problem occurs will vary, depending on the TI application.

Raksta ID: 2629666. Pēdējo reizi pārskatīts: 2012. gada 22. febr.. Pārskatījums: 1