Skip to main content

Error: 'Data source name not found and no default driver specified'

Steps you can take to resolve the ODBC data source error that occurs when running a data import in Orchestrate.

Written by Arthur Ashdown

You may see the following error message when running a data import:

Orchestrate data flow import has failed. The detailed information is as follows:
​
ERROR [IM002][Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
​
Import Command: N/A


Resolution

Work through the following options in order until the issue is resolved.

Option 1: Check the ODBC data source configuration

If you are importing from CSV, check that the ODBC data source is correctly configured in Orchestrate System Manager:

  1. Log in to Orchestrate System Manager.

  2. Select File, then select Data Import Configuration.

  3. Select Data Source Configuration.

  4. Click New.

  5. Select ODBC Data Connections from the Data Source Type dropdown list.

  6. Click Next.

  7. Click Manage ODBC Source.

  8. Select the System DSN tab and select the relevant name (for example, CSV Import), 32-bit, Microsoft Text Driver.

  9. Click Configure.

  10. Click Select Directory.

  11. Click OK.

Option 2: Check the data flow configuration

A data sequence may be missing from the data flow, a field mapping may be missing from an existing data sequence, or the data source may be directed to the wrong database. To check the data flow configuration:

  1. Log in to Orchestrate System Manager.

  2. Select File, then select Data Import Configuration.

  3. Select Data Flow Configuration.

  4. Select CSV Import and click Edit.

  5. Check each bulk copy into table data sequence and click Settings.

  6. Confirm that the CSV data source is selected from the dropdown list.

  7. Confirm that the source table contains the name of the CSV file — for example, the data sequence Bulk Copy into Table orc_Items should contain Items.CSV in the source table field.

  8. Confirm that there is a correct source expression in the equivalent Orchestrate field name.

📌Note: If no CSV is configured, you can demonstrate how it works but cannot create all the data sequences. Setting up a full CSV configuration is chargeable consultancy — raise a self-gen case if required.

Option 3: Set up a new ODBC source and Excel/CSV import configuration

If the above options do not resolve the issue, set up a new ODBC source and configure the Excel/CSV import:

  1. Launch ODBC from Windows.

  2. Select the System DSN tab.

  3. Click Add and enter a name — for example, CSV Import.

  4. Launch Orchestrate System Manager.

  5. Select File, then select Data Import Configuration.

  6. Select Excel/CSV Import Configuration.

  7. Click New, then click Next.

  8. Select which Orchestrate table the data will import to — for example, Purchase Orders.

  9. Click Browse to enter the source data location (the Excel workbook file).

  10. Click Preview, then click Next.

  11. Select Map Fields and, when complete, click Finish.

  12. Log in to Orchestrate and select File.

  13. Select Import, then select Import Excel/CSV Data.

Did this answer your question?