64-bit OLEDB Provider for ODBC (MSDASQL) Is Now Available For Windows Server 2003

Lost Drive Blog » 64-bit OLEDB Provider for ODBC (MSDASQL) Is Now Available For …

Tue, 08 Apr 2008 04:48:42 GMT

PingBack from http://lostdriveblog.com/2008/04/07/64-bit-oledb-provider-for-odbc-msdasql-is-now-available-for/

64-разрядный поставщик OLEDB для ODBC (MSDASQL)

Alexander Gladchenko — Tue, 08 Apr 2008 09:40:27 GMT

4 апреля 2008г. стала доступна для загрузки 64-разрядная версия MSDASQL для Windows 2003/XP. Поставщик

re: 64-bit OLEDB Provider for ODBC (MSDASQL) Is Now Available For Windows Server 2003

randyhersom — Wed, 16 Apr 2008 23:29:07 GMT

Does this now mean that 64 bit SQL Server can access .MDB data files through a linked server. I have already built a kludge using a 32 bit named instance to remedy this severe compatibility problem in 64 bit SQL Server, but would be happy to be able to accomplish the same task in a cleaner way.

re: 64-bit OLEDB Provider for ODBC (MSDASQL) Is Now Available For Windows Server 2003

mrovendro — Thu, 24 Apr 2008 17:18:37 GMT

Now that I have access to the ODBC drivers (thanks), how do I get the "Microsoft Text Driver (*.txt, *.csv)" amongst the other drivers installed on my x64 server?

64 bit OLDEB Provider for ODBC on Windows Server 2003

Hot Topics — Sat, 26 Apr 2008 18:37:49 GMT

In case you've been waiting for this (even if you thought MSDASQL was being deprecated), it's

re: 64-bit OLEDB Provider for ODBC (MSDASQL) Is Now Available For Windows Server 2003

Shahar — Tue, 29 Apr 2008 02:12:38 GMT

I'm trying to create a linked server to a SQL server (localhost - just for testing). When I create a DSN using the regular ODBC link (in system32) it works. However, when I create the DSN using the c:\WINDOWS\SysWOW64\odbcad32.exe it does not work.

Any Ideas?

Thanks

re: 64-bit OLEDB Provider for ODBC (MSDASQL) Is Now Available For Windows Server 2003

Phil — Wed, 30 Apr 2008 19:55:06 GMT

I am also experiencing the same issue. Loaded the new 64-bit MSDASQL, but it does not see the 32-bit ODBC DSN created on the Server. The environment is Server 2003 (64) & SQL Server Enterprise 2005 Clustered (64). My ultimate goal is to create a Linked Server to our Informix database. We done this successfully on our 32-bit SQL Server Standard 2005 environment. Unfortunately, IBM doesn't have a 64-bit ODBC driver for Informix.

re: 64-bit OLEDB Provider for ODBC (MSDASQL) Is Now Available For Windows Server 2003

Joe — Tue, 06 May 2008 12:46:18 GMT

The following codes works well on windows xp 32-bit but fails on windows xp 64-bit, I have installed the 64-bit msdasql, anybody can help me? Thanks!

_bstr_t strConnect="Provider=MSDASQL;Driver={Microsoft Access Driver (*.mdb)};Dbq=C:/test/test.mdb;";

m_pConnection.CreateInstance("ADODB.Connection");

hr =m_pConnection->Open(strConnect,"","",NULL);

re: 64-bit OLEDB Provider for ODBC (MSDASQL) Is Now Available For Windows Server 2003

Malcolm Stewart — Fri, 09 May 2008 16:59:19 GMT

The MSDASQL provider only bridges OLE DB to ODBC. It does not bridge 64-bit to 32-bit. This means that 32-bit OLE DB Providers, such as Jet, and 32-bit ODBC Drivers, such as the text driver, are still inaccessible to SQL Server 64-bit.

In addition, since the Microsoft Access ODBC driver is not thread-safe, and the text driver is based on this, using these drivers from SQL Server or IIS is not supported. You would have to use the OLE DB connection string for these and these are limited to being called from 32-bit applications only.

re: 64-bit OLEDB Provider for ODBC (MSDASQL) Is Now Available For Windows Server 2003

Auri Rahimzadeh — Sun, 15 Jun 2008 18:51:39 GMT

I ported the OpenCSV project (opencsv.sourceforge.net) to the .NET Framework. This version is read-only, although if you want a writer, let me know. Unlike OpenCSV, OpenCSV# returns a datatable, so you can simply pass in a CSV filename and it will be parsed and returned in a form that's bindable!

You can download the DLL and the source at: http://aurigroup.com/downloads/OpenCSVSharp.zip

So why not use the Microsoft Text Driver? Well, Microsoft's Text Driver doesn't work on Microsoft's 64-bit operating systems! Necessity is the mother of all invention, and therefore I'm releasing my port of OpenCSV for all .NET users to enjoy :)

Also unlike OpenCSV, OpenCSV# support setting whether the first row of data is the column headers, and automatically populates the column names so you don't have to work with index values and potentially wrong data.

Technical details:

* Written in C# instead of Java.

* Written for .NET Framework 2.0 and above.

* Made the ParseLine() function public so you can just pass a string and parse it, in case you don't want to parse an entire file. I haven't tested the ParseLine direct call, fyi.

Enjoy!

Auri Rahimzadeh

President, The Auri Group, LLC (TAG, www.aurigroup.com)

Contributor, ASP.NET Pro Magazine, Consultants Corner (yep, I do that column)

Author, Hacking the PSP, Geek My Ride

Technical Editor, Building Web Sites Bible 3rd Edition, Beginning Access 2007 VBA

re: 64-bit OLEDB Provider for ODBC (MSDASQL) Is Now Available For Windows Server 2003

stephen nally — Tue, 29 Jul 2008 20:11:54 GMT

Has any user had any success with this? It hasn't fixed my problem.

I'm not sure the install file works. I can't find any evidence of a new msdasql dll on my system. What is the file name and date? where is it installed?

A rock solid ASP application with about 50 installations will not connect to SQL Server on Windows Server 2003 64 bit.

re: 64-bit OLEDB Provider for ODBC (MSDASQL) Is Now Available For Windows Server 2003

John Welborn — Wed, 06 Aug 2008 05:55:30 GMT

I've had no success either. I've created system dsn's in both the 64bit and 32 bit sections... I've installed the patch, reboted... every random thing I can think of, and I still get the exact same error.

My connection strings look like this

DSN=DATABASE_someDB; Initial Catalog=someDB;user id=someUser;password=somePassword

Still getting the exact same no default provider message. I can get it to work if I change my connection string... but that's the whole point... I've got a ton of websites using just a few dsn connections... specifically so I wouldn't have to change them all if I moved to a new server etc. Arghhhh

re: 64-bit OLEDB Provider for ODBC (MSDASQL) Is Now Available For Windows Server 2003

John Welborn — Wed, 06 Aug 2008 06:06:27 GMT

actually... after doing a little more research, I've discovered something that might be a mind bogglingly simple solution... given, it still involves a slight alteration to the connection string, but still uses the dsn...

Same connection string as above but you add a provider to the front getting rid of the infamous (no default provider) message

Provider=MSDASQL; DSN=DATABASE_someDB; Initial Catalog=someDB;user id=someUser;password=somePassword

It's also probably worth mentioning that my dsn's connect to sqlserver, but just adding that provider description did the trick.

it was this article that clued me in...

http://www.asp101.com/articles/john/connstring/default.asp

Enjoy hopefully that will help someone.

re: 64-bit OLEDB Provider for ODBC (MSDASQL) Is Now Available For Windows Server 2003

Alan Sawyer — Fri, 08 Aug 2008 15:36:38 GMT

Does this mean that my SSIS package running on Windows Server 2003 Enterprise 64 bit would now be able to read Excel files?

We are having to run the package in 32 bit mode because it was not possible to use it in 64 bit.

Conectar desde un SSIS a Excel/Access desde 64bits

Eladio Rincón, SQL Server MVP — Mon, 18 Aug 2008 19:02:14 GMT

Más de una vez me lo han preguntado y he aquí una solución: http://ssis.trigonblue.com/Excelin64bitenv

re: 64-bit OLEDB Provider for ODBC (MSDASQL) Is Now Available For Windows Server 2003

furia — Tue, 19 Aug 2008 01:01:47 GMT

Hi,

How 32-bit applications could use a 32-bit version of .UDL files?

Is there a 32-bit OLEDB subsystem under Windows 64-bit as there is for ODBC?

For ODBC we have:

%windir%\SysWOW64\odbcad32.exe

%windir%\system32\odbcad32.exe

For OLE DB we normally use UDL files, which seems to use only 64-bit OLE DB Drivers.

Thanks.

re: 64-bit OLEDB Provider for ODBC (MSDASQL) Is Now Available For Windows Server 2003

furia — Tue, 19 Aug 2008 02:37:18 GMT

I just found how to do it:

http://blogs.msdn.com/chaitanya_medikonduri/archive/2008/04/09/how-to-run-32-bit-udl-file-on-a-64-bit-operating-system.aspx

Here is the 32-bit version of OLEDB subsystem:

\Program Files (x86)\Common Files\System\Ole DB\oledb32.dll

re: 64-bit OLEDB Provider for ODBC (MSDASQL) Is Now Available For Windows Server 2003

furia — Tue, 19 Aug 2008 02:37:37 GMT

When will Microsoft provide both a 64-bit ODBC driver and OLEDB Provider for Jet, Excel and Text files?

re: 64-bit OLEDB Provider for ODBC (MSDASQL) Is Now Available For Windows Server 2003

J Pihl — Wed, 08 Oct 2008 17:34:13 GMT

Any suggestions how to make an x64 application read an excel file when jet is not supported.

re: 64-bit OLEDB Provider for ODBC (MSDASQL) Is Now Available For Windows Server 2003

DOQ — Sun, 25 Jan 2009 19:40:56 GMT

Also wondering when a 64-bit ODBC driver for Windows x64 will be made available? Have searched far and wide and none to be found. How can that be, and, when will one be made available? Would love to make use of 64-bit PERL, but, without the drivers, no can do....

re: 64-bit OLEDB Provider for ODBC (MSDASQL) Is Now Available For Windows Server 2003

Qasem — Thu, 19 Feb 2009 09:20:37 GMT

Dears,

Is there any provider on windows server 2008 (64-bit)to read an Excel File ??

Please help me!!!

re: 64-bit OLEDB Provider for ODBC (MSDASQL) Is Now Available For Windows Server 2003

Richard — Thu, 26 Feb 2009 18:28:27 GMT

MS Access is still a shipping product, so where the hell is the 64-bit Jet driver???

re: 64-bit OLEDB Provider for ODBC (MSDASQL) Is Now Available For Windows Server 2003

Don — Sat, 20 Jun 2009 07:14:05 GMT

Thought this idea might be of some help. I'm trying to access a MS Access 2003 file while on a Win2003 64 bit system. I was able to use the 32 bit providers when I ran Powershell in 32 bit mode. (%SystemRoot%\syswow64\WindowsPowerShell\v1.0\powershell.exe) I use the connection string from here:

http://skatterbrainz.blogspot.com/2009/05/using-powershell-with-ms-access.html

re: 64-bit OLEDB Provider for ODBC (MSDASQL) Is Now Available For Windows Server 2003

vasudev — Thu, 29 Oct 2009 07:41:51 GMT

Microsoft is planning to release 64 bit version of office i.e office2010 to have both 32 bit and 64 bit flavors. once its released we should have 64 bit drivers as well. this should resolve most of the 64bit driver issues with excel,jet etc