Distributed Transaction/UADTC Issues

Knowledge Base: UADriver Troubleshooting

The very first step in resolving a UADTC related problem is to use the “Transaction Coordinator Connectivity Test” feature. This feature can be accessed via the ODBC Data Source Administrator by selecting the UniAccess DSN in question.

Problem:
After installing MMC 3.0 (KB907265) on Windows XP or Windows Server 2003, MMC can abort if the UADTC service is not running.
Solution::
Review this document if your site uses distributed transactions.
Problem:
After installing Microsoft Security Bulletin MS05-051 (Knowledge Base article 902400) to Windows 2000, Windows XP, or Windows Server 2003, attempts to execute a distributed transaction using UADTC fail.
Solution:
Review this document if your site uses distributed transactions.
Problem:
Windows Server 2003 SP1 Disables MS DTC Network.
Solution:
Review this document for steps on how to enable MS DTC network access.
Problem:
Windows XP and Windows Server 2003 do not support TIP protocol by default.
Solution:

Windows XP and Windows Server 2003 disable TIP protocol by default. Prior to attempting to use UADTC, TIP protocol must be enabled.

Steps to enable the TIP protocol are:

  • Start, Control Panel, Administrative Tools, Component Services
  • Expand Component Services
  • Expand Computers
  • Right click on the computer on which you wish to enable TIP, select Properties, select the MSDTC tab
  • Click on Security Configuration
  • Check the box “Transaction Internet Protocol (TIP) Transactions
  • Click OK
  • Click OK
  • Click OK
  • Close the Component Services window
Problem:
A pre-10R2 UADTC is not usable when installed on Windows XP Service Pack 2.
Solution:
This is due to the fact that the launch permissions for UADTC are not compatible with Windows XP Service Pack 2. Note: The launch permissions have been changed beginning with UADTC versions 2.10.0004 and 2.11.0001.

Steps to manually update UADTC launch permissions to be compatible with Windows XP Service Pack 2 are:

  • Start, Control Panel, Administrative Tools, Component Services
  • Expand Component Services
  • Expand Computers
  • Expand on the UADTC computer
  • Expand on the DCOM Config
  • Right-click on UADTC, select Properties, select the Security tab
  • Check the box “Use Default” under Launch Permissions
  • Click OK
  • Stop and Start the UADTC Service (if already running).
Problem:
UniAccess distributed transactions may cause system hang (EXERR-410).
Solution:
Install the changes associated with EXEC PLE 17674544.
Problem:
UADTC service cannot be started
Solution:
Check the Event Viewer Application Log for any UADTC events. This error usually happens when the UADTC service is unable to bind to a port previously assigned to it by the operating system. In other words, the port UADTC is trying to bind to has already been assigned to another application. To correct this problem, using UADTC snap-in, reset the listen port to zero. This will cause the UADTC service to request a new port at startup.

Please note that changing the listen port can potentially cause the previously active transactions to remain unresolved as MSDTC may try to connect to the previously assigned UADTC port. If this is a concern, stop the application that has been assigned the UADTC listen port and restart the service.

If the service is failing to start after the initial install of the service, reboot your system and attempt to start the service again.

Problem:
Failed to register transaction with MSDTC or UDS
Solution:
This error means that the participating UASL transaction was unable to register itself with MS DTC. This error usually happens if the UADTC service is currently stopped. Another reason this error may occur is when the UDSBDI parameter specified in UniAccess Configuration File is incorrect.
Problem:
In a Windows XP or Windows Server 2003 environment, the UADriver Transaction Coordinator Connectivity Test returns a failure for Microsoft TIP Support
Solution:
When Windows XP or Windows Server 2003 is installed, the default setting for the Microsoft DTC TIP support is disabled. TIP must be enabled on the pc running MS DTC. To enable TIP, select Component Services from Control Panel, Administrative Tools, right-click My Computer and select Properties. Select theMSDTC tab and select the Security Configuration button. Check the box titledTransaction Internet Protocol (TIP) Transactions. This configuration change will require that the MS DTC Service be stopped and restarted.
Problem:
The Transaction Coordinator Connectivity UADTC Proxy Support test fails in the ODBC Administrator with the following error: “Unable to create an instance of the UADTCTIPHelper class. Error code 0x80070005 Description: Access is denied”.
Solution:

Verify that the UADTC service is started. The UADTC service must be running in order for the UADTC Proxy Support test to be successful.

Problem (UniAccess #1661):
ACOB distributed transaction hangs during TDCOMPLETE.
Solution:
This is resolved in UniAccess 10R1-4, 10R2-3, 10R3-0 and up.
Problem (UniAccess #1693):
If a distributed UASL transaction has not called TDCOMPLETE, and a PREPARE is received, the transaction will not receive an error.
Solution:
This is resolved in UniAccess 10R1-4, 10R2-3, 10R3-0 and up.
Problem (UniAccess #1372):
ACOB distributed transaction receives a TDS-INTERNAL-ERROR on 2nd TDACCEPT.
Solution:
This is resolved in UniAccess 10R1-2, 10R2-0, 10R3-0 and up.
Problem (UniAccess #1211):
UASL ACOB transaction participating in a distributed environment can hang.
Solution:
This is resolved in UniAccess 10R1-0, 10R2-0, 10R3-0 and up.
Problem (UniAccess #1724):
When a communication error prevents UADTC sending the TDCOMPLETE command, a transaction which has issued a TDCOMPLETE may hang if the CONTIMOUT ACOB distributed transaction hangs during TDCOMPLETE.
Solution:
This is resolved in UniAccess 10R1-4, 10R2-3, 10R3-0 and up.

Knowledge Base: UADriver Troubleshooting