1. Access 2016 Odbc Driver Download
2. Windows 10 Excel Odbc Driver
3. Microsoft Excel Driver Odbc Download
4. Excel Odbc Driver Download

ODBC Data Source Administrator Help - Windows Data Access Components ODBC Drivers for Microsoft Access, dBase, Excel, Paradox, and Others. 64-bit MSDASQL for Windows 2003 is now available for download.

While connecting .net to sybase server I got this error message:

[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified

This has worked properly before. System DSN with same details work and data connection through vs.net also work.

I am using vs.net 2005.

Any suggestions?

4 Answers

If you're working with an x64 server, keep in mind that there are different ODBC settings for x86 and x64 applications. The 'Data Sources (ODBC)' tool in the Administrative Tools list takes you to the x64 version. To view/edit the x86 ODBC settings, you'll need to run that version of the tool manually:

When your app runs as x64, it will use the x64 data sources, and when it runs as x86, it will use those data sources instead.

I got a similar error, which was resolved by installing the corresponding MySQL drivers from:

and by performing the following steps:

1. Go to IIS and Application Pools in the left menu.
2. Select relevant application pool which is assigned to the project.
3. Click the Set Application Pool Defaults.
4. In General Tab, set the Enable 32 Bit Application entry to 'True'.

Reference:

For anyone coming to this latterly, I was having this problem over a Windows network, and offer an additional thing to check:

Python script connecting would work from commandline on my (linux) machine, but some users had problems connecting - that it worked from CLI suggested the DSN and credentials were right. The issue for us was that the group security policy required the ODBC credentials to be set on every machine. Once we added that (for some reason, the user had three of the four ODBC credentials they needed for our various systems), they were able to connect.

You can of course do that at group level, but as it was a simple omission on the part of one machine, I did it in Control Panel > ODBC Drivers > New

Perform the following steps:

1. Start the Registry Editor by typing regedit in the Run window.
2. Select the following key in the registry: HKEY_LOCAL_MACHINESOFTWAREODBC.
3. In the Security menu, click Permissions.
4. Grant Full Permission to the account which is being used for making connections.
5. Quit the Registry Editor.

Access 2016 Odbc Driver Download

protected by dippasAug 31 '16 at 13:31

Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?

UPDATED:

We were having the same issue and it was related to a bug in the ActualTech ODBC package. They have since posted an update on their website here:

http://www.actualtech.com/download.php

After installing the update, we were back in action.

I am not sure this is the whole source of the problem, despite Microsoft's articles...

I just downloaded and installed v4.0 of the Actual Open Source Database drivers, and they appear to BE 64bit....

Looking at the ODBC driver:

$ lipo -info 'Actual Open Source Databases'

Architectures in the fat file: Actual Open Source Databases are: i386 ppc7400 x86_64 ppc64

I do have others installed, not all of which might be 64bit, but in your case if Actual is the only one installed and you are on the latest release it should be 64bit capable.

UPDATE: In fact, all but one of my installed ODBC drivers WERE 64bit, so I removed the onlly one that was not and the same crash happens. I don't think the 64bit issue is the entire answer to the problem this latest office update has inflicted on us.

Ok so I called into their support line and they were able to give me an installer for the 32 bit version of Excel. I'd recommend you do the same if you need the functionality now.

BTW chat was a no-go for this, I had to call.

I'd post the link here but they also removed some other things manually in order to completely remove Office 2016 before re-installing. I think its safer to have them do that.

Regarding the error the exception I was getting looks like this:

Windows 10 Excel Odbc Driver

Crashed thread: 0

It references iODBC, which I believe is the first ODBC manager Excel attempts to use prior to prompting you to use the ODBC manager that comes w/ the Actual package.

I'm not sure if iODBC is installed w/ Excel or Actual.

We have discovered that our driver has an issue with the August (64-bit) release of Excel 2016. We will be releasing a fix within the next 48 hours.

I will post here when the new version has been released.

UPDATE: we have posted a new version of the Actual ODBC Pack to our website: http://www.actualtech.com/download.php

The new versions of the ODBC drivers fix the crashing issue with 64-bit Excel 2016 (15.25).

Jonathan Monroe

Actual technologies - ODBC for macOS

http://www.actualtech.com

I see an update posted, and after I installed it Excel 2016 64bit (15.25 (160817)) is no longer crashing when I attempt to insert data from an external database.

Thanks!!

Hi, here is the information we have on this issue, I hope it helps. If you continue to experience problems after installing a compatible driver, please let us know.

Issue

When retrieving data via Data > Get External Data > From Database from an external database that uses a 32-Bit ODBC driver, the 64-Bit Excel 2016 for Mac (version 15.25 or later) crashes

Status: Workaround

This is a known compatibility issue. Please visit this article ODBC drivers that are compatible with Excel for Mac and install a driver that includes 64-bit support.

See Also

Microsoft Excel Driver Odbc Download

Freya

Excel Odbc Driver Download

Office Newsroom