FIX: ADO.NET Provider for DB2 fails and returns "ITransactionJoin.JoinTransaction" error

Applies to: Host Integration Server 2013Host Integration Server 2016


When you run an application by using the ADO.NET Provider for DB2 that's configured for distributed transaction, the application fails under load and returns the following Exception:



This issue was introduced when we added XA transaction support. In some situations, the destructor for MSDTC cleanup was never called. This causes the MSDTC exception.


The fix that resolves this problem is included in the following cumulative updates for Host Integration Server:

Cumulative Update 2 for Host Integration Server 2016

Cumulative Update 4 for Host Integration Server 2013


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


Learn about the terminology Microsoft uses to describe software updates.