{"id":233,"date":"2026-10-07T15:42:39","date_gmt":"2026-10-07T13:42:39","guid":{"rendered":"https:\/\/datenquelle.at\/?page_id=233"},"modified":"2026-10-08T07:08:10","modified_gmt":"2026-10-08T05:08:10","slug":"odbc-data-source-not-found-im002","status":"publish","type":"page","link":"https:\/\/en.datenquelle.at\/index.php\/odbc-data-source-not-found-im002\/","title":{"rendered":"ODBC data source not found (IM002)"},"content":{"rendered":"<div class=\"et_pb_section_0 et_pb_section et_section_regular et_flex_section\">\n<div class=\"et_pb_row_0 et_pb_row et_flex_row\">\n<div class=\"et_pb_column_0 et_pb_column et-last-child et_flex_column et_pb_css_mix_blend_mode_passthrough et_flex_column_24_24 et_flex_column_24_24_tablet et_flex_column_24_24_phone\">\n<div class=\"et_pb_code_0 et_pb_code et_pb_module\"><div class=\"et_pb_code_inner\"><section class=\"dq-section dq-help-hero\" id=\"dq-main\"><div class=\"dq-wrap\"><nav class=\"dq-breadcrumbs\" aria-label=\"Breadcrumb navigation\"><a href=\"https:\/\/en.datenquelle.at\/\">Home<\/a><span>\/<\/span><a href=\"https:\/\/en.datenquelle.at\/index.php\/errors-solutions-for-your-data\/\">Errors & solutions<\/a><span>\/<\/span><a href=\"https:\/\/en.datenquelle.at\/index.php\/errors-solutions-for-your-data\/#odbc\">ODBC & Driver<\/a><\/nav><p class=\"dq-eyebrow\"><span class=\"dq-dot\" aria-hidden=\"true\"><\/span>ODBC & Driver<\/p><h1>ODBC data source not found or not recognized<\/h1><p class=\"dq-lead\">The application cannot find the specified ODBC connection or driver name. \u201cData source name not found and no default driver specified\u201d is the typical English message for SQLSTATE IM002. This does not establish that the database itself has failed.<\/p><ol class=\"dq-help-flow\" aria-label=\"Data path and checkpoint\"><li><span>Source<\/span><strong>Application<\/strong><\/li><li class=\"is-checkpoint\"><span>Check the connection<\/span><strong>DSN & Driver<\/strong><\/li><li><span>Destination<\/span><strong>Database<\/strong><\/li><\/ol><\/div><\/section><\/div><\/div>\n<\/div>\n<\/div>\n<\/div><div class=\"et_pb_section_1 et_pb_section et_section_regular et_flex_section\">\n<div class=\"et_pb_row_1 et_pb_row et_flex_row\">\n<div class=\"et_pb_column_1 et_pb_column et-last-child et_flex_column et_pb_css_mix_blend_mode_passthrough et_flex_column_24_24 et_flex_column_24_24_tablet et_flex_column_24_24_phone\">\n<div class=\"et_pb_code_1 et_pb_code et_pb_module\"><div class=\"et_pb_code_inner\"><section class=\"dq-section dq-help-body\"><div class=\"dq-wrap\"><div class=\"dq-help-layout\"><article class=\"dq-help-article\"><section class=\"dq-help-situation\"><h2>How this appears in daily operation<\/h2><p>An office application works on the old PC. On a new workstation, \u201cData source name not found\u201d appears. Or a scheduled import fails even though the same user can start it manually. The first question is where the access actually runs.<\/p><\/section><section id=\"ursachen\"><h2>Distinguish typical causes<\/h2><div class=\"dq-help-causes\"><div><h3>Different name or workstation<\/h3><p>The application expects a particular DSN. After a move, that entry may be missing or the connection may use a different driver name.<\/p><\/div><div><h3>Different execution account<\/h3><p>A logged-in employee's user data source is not automatically available to a service running under another account.<\/p><\/div><div><h3>Architecture mismatch<\/h3><p>A visible data source alone does not establish whether the application has the appropriate 32-bit or 64-bit driver.<\/p><\/div><\/div><\/section><section id=\"pruefen\"><h2>What you can check first<\/h2><ol class=\"dq-help-checks\"><li><h3>Record the complete error message<\/h3><p>Record the SQLSTATE, application and time. Remove passwords from screenshots or connection strings.<\/p><\/li><li><h3>Identify where the process runs<\/h3><p>Does access run on a workstation, a terminal server or a background service? Compare the affected computer with a working connection.<\/p><\/li><li><h3>View entries<\/h3><p>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.<\/p><\/li><\/ol><\/section><section id=\"tiefer\"><h2>When the problem runs deeper<\/h2><p>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.<\/p><div class=\"dq-help-details\"><details><summary>DSN and connections without a DSN<\/summary><p>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.<\/p><\/details><details><summary>From a workstation problem to an operational process<\/summary><p>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.<\/p><\/details><\/div><\/section><section id=\"weiter\"><h2>When support makes sense<\/h2><p>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.<\/p><a class=\"dq-help-service\" href=\"https:\/\/en.datenquelle.at\/index.php\/reuse-legacy-systems\/\"><span>The right solution path<\/span><strong>Keep using existing databases<\/strong><span class=\"dq-ui-arrow\" aria-hidden=\"true\"><\/span><\/a><aside class=\"dq-help-cross\"><p>If new PCs, a terminal server or the Windows environment are also involved, reviewing the IT environment belongs with DAXS.<\/p><a href=\"https:\/\/daxs.com\/\" rel=\"noopener\">Further support from DAXS<span class=\"dq-ui-external\" aria-hidden=\"true\"><\/span><\/a><\/aside><\/section><section class=\"dq-help-sources\"><h2>Sources for technical assessment<\/h2><ul><li><a href=\"https:\/\/learn.microsoft.com\/en-us\/troubleshoot\/sql\/database-engine\/install\/windows\/odbc-driver-install-checking\" rel=\"noopener\">Microsoft: Check ODBC drivers and DSNs<\/a><\/li><\/ul><p>Technical content reviewed on 7 October 2026. Vendor statements refer to the products named; they do not replace checking your specific configuration.<\/p><\/section><\/article><aside class=\"dq-help-toc\"><nav aria-label=\"On this help page\"><span class=\"dq-kicker\">On this page<\/span><a href=\"#ursachen\">Typical causes<\/a><a href=\"#pruefen\">Initial checks<\/a><a href=\"#tiefer\">Technical relationships<\/a><a href=\"#weiter\">Suitable solution path<\/a><\/nav><div><span class=\"dq-kicker\">Related problems<\/span><a href=\"https:\/\/en.datenquelle.at\/index.php\/32-bit-odbc-on-64-bit-windows\/\">32-bit ODBC on 64-bit Windows<\/a><a href=\"https:\/\/en.datenquelle.at\/index.php\/sql-server-connection-failed\/\">SQL Server: connection failed<\/a><a href=\"https:\/\/en.datenquelle.at\/index.php\/errors-solutions-for-your-data\/\">To the topic overview<\/a><\/div><\/aside><\/div><\/div><\/section><\/div><\/div>\n<\/div>\n<\/div>\n<\/div><div class=\"et_pb_section_2 et_pb_section et_section_regular et_flex_section\">\n<div class=\"et_pb_row_2 et_pb_row et_flex_row\">\n<div class=\"et_pb_column_2 et_pb_column et-last-child et_flex_column et_pb_css_mix_blend_mode_passthrough et_flex_column_24_24 et_flex_column_24_24_tablet et_flex_column_24_24_phone\">\n<div class=\"et_pb_code_2 et_pb_code et_pb_module\"><div class=\"et_pb_code_inner\"><section class=\"dq-section dq-help-contact-section\"><div class=\"dq-wrap\"><div class=\"dq-help-contact\"><div><h2>Clarify the next step together.<\/h2><p>Your application names and a brief description of the problem are enough to start.<\/p><\/div><a class=\"dq-button\" href=\"https:\/\/en.datenquelle.at\/index.php\/discuss-your-data-challenge\/\" aria-haspopup=\"dialog\" aria-controls=\"dq-booking-modal\" data-dq-booking>Book an initial consultation<\/a><\/div><\/div><\/section><\/div><\/div>\n<\/div>\n<\/div>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>Understand ODBC error IM002: distinguish DSNs, drivers and user context. What you can check without making changes, and when the connection needs deeper investigation.<\/p>\n","protected":false},"author":2,"featured_media":204,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-233","page","type-page","status-publish","has-post-thumbnail","hentry"],"_links":{"self":[{"href":"https:\/\/en.datenquelle.at\/index.php\/wp-json\/wp\/v2\/pages\/233","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/en.datenquelle.at\/index.php\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/en.datenquelle.at\/index.php\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/en.datenquelle.at\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/en.datenquelle.at\/index.php\/wp-json\/wp\/v2\/comments?post=233"}],"version-history":[{"count":4,"href":"https:\/\/en.datenquelle.at\/index.php\/wp-json\/wp\/v2\/pages\/233\/revisions"}],"predecessor-version":[{"id":313,"href":"https:\/\/en.datenquelle.at\/index.php\/wp-json\/wp\/v2\/pages\/233\/revisions\/313"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/en.datenquelle.at\/index.php\/wp-json\/wp\/v2\/media\/204"}],"wp:attachment":[{"href":"https:\/\/en.datenquelle.at\/index.php\/wp-json\/wp\/v2\/media?parent=233"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}