64 Bit Oledb Provider For Odbc Msdasql

Microsoft Ole Db Provider For Sql Server
64-bit Ole Db Provider For Odbc (msdasql)
Download 32-bit Ole Db Provider For Odbc (msdasql)
Msdasql 32 Bit
64-bit Ole Db Provider For Odbc (msdasql) For Windows Server 2012
64-bit Ole Db Provider For Odbc (msdasql) Windows 7
Microsoft Ole Db Driver For Sql Server

I think the problem is that the 64-bit MSDASQL provider (OLEDB to ODBC bridge) cannot thunk to a 32-bit ODBC driver, so it's simply not going to be possible to connect to an ISAM database such as Microsoft Access, a Text file, Excel, etc. Which currently. The Microsoft OLE DB Provider for ODBC inserts several dynamic properties into the Properties collection of the unopened Connection, Recordset, and Command objects. The following tables are a cross-index of the ADO and OLE DB names for each dynamic property. This was the very first OLE DB provider ever released, and is also known as “MSDASQL”, due to the fact that it is contained in “MSDASQL.DLL”. MSDASQL allows OLE DB consumer applications to utilize ODBC drivers to connect to a data source. MSDASQL is an OLEDB provider that allows applications built on OLEDB and ADO (which uses OLEDB internally) to access data sources through an ODBC driver instead of a database. MSDASQL ships with the Windows Operating System, and Longhorn Beta 3 is the first Windows release to include a 64-bit version of MSDASQL. I think the problem is that the 64-bit MSDASQL provider (OLEDB to ODBC bridge) cannot thunk to a 32-bit ODBC driver, so it's simply not going to be possible to connect to an ISAM database such as Microsoft Access, a Text file, Excel, etc. Which currently only operate through 32-bit drivers (OLEDB and ODBC).

Microsoft OLE DB Provider for ODBC Overview.; 13 minutes to read Contributors. All; In this article. To an ADO or RDS programmer, an ideal world would be one in which every data source exposes an OLE DB interface, so that ADO could call directly into the data source. Jul 24, 2009 64-bit MSDASQL can only be used with 64-bit ODBC drivers. Since there were no 64-bit ODBC drivers shipped for MS Access (the latest ACE driver is also 32-bit only), 64-bit MSDASQL is not a solution for your problem.

Active6 years, 2 months ago

I need to create a Linked Server from SQL 2008 SP1 64 bit instance located on a Windows 64 bit 2003 SP2 server towards a Mysql Server. As many of you know MSDASQL provider for 64 bit systems was put available by Microsoft later in a hot fix. This is what I have done so far:

Install MySQL connector.
Install MSDASQL provider.
Create ODBC connection with correct credentials. Test is succesfull.

When I try to create a Linked Server specifying the new DSN created I get the following error:

Cannot initialize the data source object of OLE DB provider 'MSDASQL' for linked server 'MYSQL'. OLE DB provider 'MSDASQL' for linked server 'MYSQL' returned message 'Specified driver could not be loaded due to system error 998 (MySQL ODBC 5.1 Driver).'. (Microsoft SQL Server, Error: 7303)

Microsoft Ole Db Provider For Sql Server

I mention that I didn't reboot the server after installing the hotfix containing the OLEDB provider since it is a Production server and I must have a very good reason for doing this. Is the restart required?

I installed process monitor and I saw that before throwing the error SQL tries to get access to two paths:

Path: C:Program FilesMySQLConnector ODBC 5.1myodbc5.dll.2.ConfigResult: NAME NOT FOUND

Path: C:Program FilesMySQLMySQL Server 5.1sharecharsetsResult: NAME NOT FOUND

I gave full rights on C:Program FilesMySQLConnector ODBC 5.1 to user which tries to get the access.

Does anybody know how I can fix this?

Thanks,

yrushkayrushka

1,5371 gold badge11 silver badges20 bronze badges

1 Answer