An order will not load and shows an ODBC "Data source name not found" error. The data source (DSN) your integration uses is missing or set up wrong on the station or server. Create or repair the DSN and confirm it tests successfully.

Problem

Loading an order errors right after you enter the order number, before you pick a carrier, with:

Error loading from integration ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified

Restarting the station does not clear it. It happens on both parcel and freight (LTL) loads.

Cause

The IM002 message comes from Windows. The data source (DSN) named in your integration either does not exist on that machine, exists only in the wrong version (32-bit versus 64-bit), or has connection settings that no longer reach the database. Shipstore runs the integration through that DSN, so the load fails before any carrier call.

How to check

Open the ODBC Data Source Administrator and look for a DSN with the exact name your integration expects.

Fix

  1. Open the ODBC Data Source Administrator on the station or server. Open both the 32-bit and 64-bit versions, because the app and the driver can use different ones.
  2. Confirm a data source (DSN) exists with the exact name your integration expects. If it is missing, create it.
  3. On the DSN's server tab, enter the correct server name and sign-in details, then click Test Connection and confirm it succeeds.
  4. Reload the web page and load the order again.
  5. If Test Connection succeeds but the order still fails, email support@shipstore.com and include your company name, the station name, and the exact error text.

What you should see

Test Connection returns success, and the order loads and rates with no "Data source name not found" error.