|
 |
DB2 for i5/OS
Developing Distributed Applications with DB2 UDB for iSeries and Microsoft MTS

|
Troubleshooting
Applications using Client Access ODBC with Microsoft Transaction Server (MTS) or Microsoft COM+ transaction services may encounter the error "[IBM][Client Access Express ODBC Driver (32-bit)]Enlist with DTC phase failed. x", where x is the reason code for the error. The most common reason for the enlist phase error is that the CWBODBC.DLL (Client Access ODBC driver) is not in the global PATH on the Windows system where the MTS process is running. To correct the path, select Control panel --> System Properties --> Environment Variables --> System Variables --> Path. Add the directory, where the CWBODBC.DLL is located to the PATH system variable. Usually the driver can be found in C:\Program Files\ibm\Client Acccess\Shared directory. You may need to reboot your system for the change to go into effect.
Sometimes, when resolving an error in a distributed environment, you may pin down the problem area by taking the detail ODBC traces. This should allow you to verify that the ADO requests are properly passed to the ODBC driver. You may also track the transaction flow to see if any error messages were returned from the DB2 UDB for iSeries database. The detail traces need to be taken in the same context as the MTS component and MSDTC are running under. Here are the steps required to take a detail trace:
- Verify that the identity for the package that contains you component under MTS is as shown below:
- Configure the Log On properties of the MSDTC service as shown below (through the service panel):

- Use a user profile with administrator authority. Restart the MSDTC service.
- Enable the detail trace on the desktop by selecting Start --> Programs --> Client Acccess --> Service --> Diagnostic Tools. In the right-hand side of your desktop, you will see a icon that looks like a computer with a little red dot on it. Right-click on the icon and choose 'Start All Diagnostics'
- After you recreated the problem, the trace file should contain data similar to the following:

[ Prev | Next ]
|
|
|
|
|