When an ODBC database transaction fails, the error messages displayed by expressor Studio and the etask command might indicate that an exception occurred. To get enough information to diagnose the problem, you may need to turn on ODBC Tracing. That will capture all error messages. Note, however, that performance will degrade while ODBC Tracing is turned on.
An erro message might indicate specifically that an ODBC Exception has occurred. For example, the message "Exception 'GenericOdbcOpException"" clearly indicates a problem with an ODBC connection. ODBC Tracing can be useful, though, even when an ODBC-specific message is not generated. If Studio crashes while running a dataflow that uses ODBC connections, turning on ODBC Tracing might prove helpful in identifying the specific problem if is is related to the ODBC connection.
Turn on ODBC Tracing prior to running a dataflow that is generating errors or otherwise failing.
Select the Start > All Programs > expressor > expressor3 > system tools >Data Sources (ODBC) menu item.
Select the Tracing tab in the ODBC Data Source Administrator dialog box.
Change the Log File Path or leave the default path indicated.
Click the Start Tracing Now button.
Click the Apply button.
Rerun the dataflow.
Reopen the ODBC Data Source Administrator dialog box.