[ Microsoft ][ ODBC 驱动程序管理器]未找到数据源名称，也未指定默认驱动程序

我试图在 WindowsXPPro 上首次打开一个使用 PostgreSQL9的程序。我收到一个错误消息，说:

在尝试登录或创建 生产数据库。详细信息: [ Microsoft ][ ODBC 驱动程序管理器]数据 未找到源名称，也未指定默认驱动程序

在 ODBC 管理器中，我有一个用户 DSN 和系统 DSN 的列表。我尝试安装 postgres odbc 驱动程序，看看是否有帮助，但它没有。

在程序文件中有一个 Connect.dat 文件，其中有一行写着“ OLEDB Provider = MSDASQL”。更改此条目将得到的错误消息更改为“ Provider 未找到，可能未正确安装”。

我不知道要插入什么提供程序名称才能正常工作。我对这个错误做了大量的研究，但是没有用。如有任何建议，我们将不胜感激。

531326 次浏览
小开

  1. In reference to the error: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified.

    That error means that the Data Source Name (DSN) you are specifying in your connection configuration is not being found in the windows registry.

    • It is important that your ODBC driver's executable and linking format (ELF) is the same as your application. In other words, you need a 32-bit driver for a 32-bit application or a 64-bit driver for a 64-bit application.

      If these do not match, it is possible to configure a DSN for a 32-bit driver and when you attempt to use that DSN in a 64-bit application, the DSN won't be found because the registry holds DSN information in different places depending on ELF (32-bit versus 64-bit).

      Be sure you are using the correct ODBC Administrator tool. On 32-bit and 64-bit Windows, the default ODBC Administrator tool is in c:\Windows\System32\odbcad32.exe. However, on a 64-bit Windows machine, the default is the 64-bit version. If you need to use the 32-bit ODBC Administrator tool on a 64-bit Windows system, you will need to run the one found here: C:\Windows\SysWOW64\odbcad32.exe

      Where I see this tripping people up is when a user uses the default 64-bit ODBC Administrator to configure a DSN; thinking it is for a 32-bit DSN. Then when the 32-bit application attempts to connect using that DSN, "Data source not found..." occurs.

    • It's also important to make sure the spelling of the DSN matches that of the configured DSN in the ODBC Administrator. One letter wrong is all it takes for a DSN to be mismatched.

      Here is an article that may provide some additional details

      It may not be the same product brand that you have, however; it is a generic problem that is encountered when using ODBC data source names.

  2. In reference to the OLE DB Provider portion of your question, it appears to be a similar type of problem where the application is not able to locate the configuration for the specified provider.

小开

Got this error because I had the Data Source Name in User DSN instead of System DSN enter image description here

小开

The Problem might be from the driver name for example instead of DRIVER={MySQL ODBC 5.3 Driver} try DRIVER={MySQL ODBC 5.3 Unicode Driver} you can see the name of the driver from administration tool

小开

I got this with data driven tests using:

Microsoft Excel Driver (*.xls, *.xlsx, *.xlsm, *.xlsb)

The problem is the above driver only is 32 bit. I had switched visual studio testsettings file to 64 bit to test a 64-bit-only application.

Switching back to 32 bit in the testsettings file fixed the issue.

using a test settings file

小开

I tried the above but found my issue was I used a | in the name of the DSN (I have multipled ODBC connectors - one for each DB - to make sure I don't comingle data)

I replaced the | (pipe) with a _ and all now works fine.

I was trying to call SQL Server from Alteryx.

小开

Following the instructions here http://help.loftware.com/pages/viewpage.action?pageId=27099554 I had to install the Microsoft Access Database Engine 2010 Redistributable before I had the Excel driver installed to use the DSN-less connection I wanted to use from perl.

小开

if you are using IIS, maybe you should try
"application pools" --> "DefaultAppPool" --> "application pools default value" --> "32-Bit-application-activ" --> set false

小开

In my case, it was working in x86 but not in x64.

It quite ridiculous, but in x64 the following change had to be added before it would work:

x86 -> szDsn = "DRIVER={MICROSOFT ACCESS DRIVER (*.mdb)};
x64 -> szDsn = "DRIVER={MICROSOFT ACCESS DRIVER (*.mdb, *.accdb)};

Note the addition of *.accdb.

小开

Check the exact driver name in the ODBC Administrator tool. Press Windows key + R and then:

  • C:\Windows\System32\odbcad32.exe on 32-bit systems
  • C:\Windows\SysWOW64\odbcad32.exe on 64-bit systems

In my case it should have been Microsoft Access Driver (*.mdb, *.accdb) instead of Microsoft Access Driver (*.mdb).

小开

For me the below worked:

  1. Add the linked server as a System DSN (ODBC System Source Administration) e.g. with name -> TEST_NAME

enter image description here

  1. Use as data source the TEST_NAME enter image description here
小开

This was not the first time I have come to this page searching for the same error message. Unfortunately, Microsoft error messages are vague and often several different issues will cause the same error message, hence why there are so many answers here.

I will propose another solution in case this helps anyone else.

Under Excel Datasource settings I use the following connection string:

"ODBC;DSN=jg_report;Trusted_Connection=Yes;"

The problem is that when I am opening an ADODB connection in VBA, and I use this same string, it will produce the "[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified" error.

To correct the connection string, I simply have to remove the "ODBC;" as follows:

"DSN=jg_report;Trusted_Connection=Yes;"

The connection then works as expected without producing errors.


提交答案