Troubleshooting

If you are having trouble diagnosing your application errors, refer to the following of troubleshooting tips:

  • Make sure that the Distributed Transaction Coordinator (DTC) is running on all servers.
  • Check network communication by first testing on a local computer to verify that the application works. If you are running TCP/IP on your network, you can use the ping.exe utility to verify that the machines are on the network.
  • Make sure that SQL and DTC are located on the same computer or that the DTC Client Configuration program specifies that the DTC is on another computer. If not, SQLConnect will return an error internally when called from a transactional component.
  • Set the transaction time-out to a higher number than the default 60 seconds. After the transaction time-out has elapsed, COM+ aborts the transaction. All subsequent calls to the component return immediately with CONTEXT_E_ABORTED.
  • Make sure that your ODBC drivers are thread-safe and do not have thread affinity.
  • If you have difficulty getting an application to work over several servers, reboot the client and then verify that your domain controller is configured properly.

Fault Isolation and Failfast Policy

Finding the Source of an Error

How COM+ Modifies Return Values

Interpreting Error Codes

Strategies for Handling Errors in COM+