If I drop the linked table and use the 64-bit odbcad to create the DSN, it works just fine and I can query data from the remote server as expected.ĭoes anyone know how to get around this issue? I have seen a lot of 64/32-bit discussion, but nothing about this specifically. 'ODBC: ERROR 08001 FATAL: password authentication failed for user. Updated: Unable connect Oracle DB via ODBC. "cannot initialize the data source of OLE DB provider "MSDASQL" for linked server "MyServerName".(Microsoft SQL Server Error:7303) Add another string value with Name ODBC call to connect database failed with error: ODBC call for data source The odbcinst.
In the Select Components tab, select which version of the driver to install (64-bit/32-bit). Select the installation directory for the ODBC driver for Oracle.
The linked server code completes without error, but when I try to navigate the object browser to see the tables, I get an error message that says" To install the ODBC Driver for SQL Server on Windows 10: Run the downloaded installer file.
SQL Server has trouble using the 32-bit driver for some reason. The problem is that the legacy app only has a 32-bit driver, so I have to use the %windir%\SYSWOW64\odbcad32.exe to create the DSN as the driver doesn't show up in the 64-bit version. I am using the SQL code I found on this site to create a linked server to an ODBC data source with a DSN thusly: XLS driver is both in english and spanish. Have no idea why these Spanish drivers are displayed - but as you can see the. 1 for SQL Server is a single dynamic-link library (DLL) containing run-time support for applications using native-code APIs to connect to Microsoft SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016, Analytics Platform System, Azure SQL Database and Azure SQL Data Warehouse. I have a Windows Server 2008 64-bit machine running SQL Server 2008 R2 64-bit. This is a screenshot of one of our other machines (2003 32 bit) that has a whole bunch of drivers.