Skip to main content

Troubleshooting

Data source not found ...

This is likely due to a mismatch between the version of the connector and the ODBC data source administrator tool that was used. Ensure that if a 32-bit data source is created that the 32-bit ODBC connector is used, and if a 64-bit data source is created that the 64-bit ODBC connector is used.

[SQLExecute] returned error [Code [07002] message [[Microsoft][ODBC
Text Driver] Too few parameters. Expected 1.] native error [-3010]].
Failed to perform operation [list].

This is likely caused by the use of an incorrect column name in the ODBC connector configuration script. Ensure that all selected columns are correctly specified in the configuration.

[SQLPrepare] returned error [Code [42000] message [[Microsoft][ODBC
Text Driver] Syntax error in FROM clause.] native error [-3506]].
Failed to perform operation [list].

This is likely caused by the use of special characters in the filename of CSV files. There are some limitations to the allowed characters in the filename for the CSV files. Dashes in particular are not allowed and cause the above error to be returned. Changing the dashes to underscores (or removing them) solves this problem.

[SQLExecute] returned error [Code [42S02] message [[Microsoft][ODBC Text Driver] File
      '<filename>.dbf does not exist.] native error [173]].  Failed to perform operation
      [list].

This is likely caused by insufficient permissions for access to the target database files. You may need to use the Run as option to use the target credentials to run the connector. You can also check the target administrator's privileges for the location of the files used by the target.