ODBC & Driver
ODBC data source not found or not recognized
The application cannot find the specified ODBC connection or driver name. “Data source name not found and no default driver specified” is the typical English message for SQLSTATE IM002. This does not establish that the database itself has failed.
- SourceApplication
- Check the connectionDSN & Driver
- DestinationDatabase
How this appears in daily operation
An office application works on the old PC. On a new workstation, “Data source name not found” appears. Or a scheduled import fails even though the same user can start it manually. The first question is where the access actually runs.
Distinguish typical causes
Different name or workstation
The application expects a particular DSN. After a move, that entry may be missing or the connection may use a different driver name.
Different execution account
A logged-in employee's user data source is not automatically available to a service running under another account.
Architecture mismatch
A visible data source alone does not establish whether the application has the appropriate 32-bit or 64-bit driver.
What you can check first
Record the complete error message
Record the SQLSTATE, application and time. Remove passwords from screenshots or connection strings.
Identify where the process runs
Does access run on a workstation, a terminal server or a background service? Compare the affected computer with a working connection.
View entries
In the ODBC administrator matching the application, check the expected DSN and driver list. Inspect only: do not delete or rename a production data source.
When the problem runs deeper
If the driver loads and a timeout, login or certificate error then appears, a different stage has been reached. Repeatedly recreating the DSN helps little. We separate local configuration, server access and business data processing.
DSN and connections without a DSN
A DSN is a named connection. Alternatively, a connection can specify the driver and destination directly. First clarify which variant the affected application uses. A DSN from another project is not a reliable repair template.
From a workstation problem to an operational process
For recurring failures, we document which application accesses which system under which account. This can form the basis of a traceable connection for an import, an overview or the continued use of a legacy database.
When support makes sense
Support is useful when only certain accounts are affected, workstations behave differently or nobody can explain the old connection. Application name, error message and the last known change are enough for an initial assessment.
The right solution pathKeep using existing databasesSources for technical assessment
Technical content reviewed on 7 October 2026. Vendor statements refer to the products named; they do not replace checking your specific configuration.
Clarify the next step together.
Your application names and a brief description of the problem are enough to start.
