I am using Windows 7 (x64bit) Ultimate.
I have both ODBC32 and ODBC64 Managers that I can access via Start.
The default appears to be the ODBC64.
However I do not see MSDASQL -Microsoft OLEDB for ODBC listed.
I wonder if it exists. I see some references to 64Bit MSDASQL for Windows Server 2003.
The IBM 64bit for ODBC seems to work (I heard) but not tried.
Now I would like to know if any one knows the link for 64-bit MSDASQL for Windows 7. Microsoft seems to have deprecated MSDASQL and I am not sure of the status of this story.
These issues came up while setting up a linked server in SQL Server 2012 for SQL (SAP) SqlAnywhere server.
I am not sure how I missed. This link allows you to download the Microsoft Access Database Engine 2010 Redistributable
http://www.microsoft.com/en-us/download/details.aspx?id=13255
The details of this indicates both ODBC and OLEDB as copied from the Microsoft Web Site:
"This download will install a set of components that facilitate the transfer of data between existing Microsoft Office files such as Microsoft Office Access 2010 (*.mdb and .accdb) files and Microsoft Office Excel 2010 (.xls, *.xlsx, and *.xlsb) files to other data sources such as Microsoft SQL Server. Connectivity to existing text files is also supported. ODBC and OLEDB drivers are installed for application developers to use in developing their applications with connectivity to Office file formats. "
There is no MSDASQL x64 bit for Windows 7. There is one for Windows Server 2003. I finally was able to create a linked server in SQL Server 2012 Express using the SAOLEDB.16 from Sybase/SAP.
Although I replied myself that there is no MSDASQL(x64)based on some 'deprecated items' information I am still looking at it.
Here is a link to the same question on MSDN:
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/3c715023-4322-4bc6-a2c8-64a873f87e46/can-someone-confirm-the-architecture-of-this-file-preferably-microsoft-guys?forum=sqldatabaseengine#db5ed4e2-2391-4062-b34d-1f1b11431e1e
Related
'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine. I am getting this in visual studio only after upgrading from 32bit office 2013 to 64bit office 16. I have already installed the 64bit database engine and my published project from IIS is working with the existing access database. I switched debug mode to x64 and remove the references to the old office and replaced them with the new office access. How can I get Visual Studio 2010 to recognize my access database created in access 2013?
Things I have tried:
Installing Microsoft Access Database Engine 2010 Redistributable 64bit version.
Updating the office references in the project.
Debugging in x64 mode
This is a little outside of my normal area of database application design;
it's unclear - you state 2016 Office 64 bit installed but then Access 2010 Redistributable/Runtime 64bit - - so do you have a full license of Access installed?
if you do have the full Access license - try something that is quick: create a brand new database and import that table. Then try the link to this new db.
I had that issue in the past.
install 2007 Office System Driver and restart visual studio.
I've dealt many time with this problem, the solution was ever install one of these:
AccessDatabaseEngine 2007.exe
AccessDatabaseEngine_2010.exe
AccessDatabaseEngine_2016.exe
AccessDatabaseEngine_X64_2010.exe
AccessDatabaseEngine_X64_2016.exe
Most of the time I've solved installing the 2007 one even using 2016 version.
To run 32-bit applications on IIS, you will get the same error. So, from the IIS 7, right-click on the applications' application pool and go to "advanced settings" and change "Enable 32-Bit Applications" to "TRUE".
Restart your website and it should work.
I have a website which will use OleDB.12.0 to read data from an Excel worksheet upon upload. It works fine on my local PC. But when hosted in my production server I get the following error.
microsoft.ace.oledb.12.0 is not registered on the local machine
How can I correct this?
My production server configuration:
MS Office 2007.
IIS 7
VS 2010
Windows 2008 R2
SQL Server2008
Does your production server have Access installed?
In any event, try installing/reinstalling Microsoft Access Database Engine 2010 Redistributable to the production server.
Update
Another point: is your production server running 32-bit or 64-bit Windows? Choose the download appropriately.
Update 2
From this link it appears that using the 64-bit version will cause trouble on a 32-bit system, but the 32-bit version will work.
I have installed Microsoft Access Database Engine 2010 Redistributable http://www.microsoft.com/en-us/download/details.aspx?id=13255 on the Windows 2008 server. However, when I ran my web application to import a spreadsheet table to the database. It complains with the error message - "Microsoft.ACE.OLEDB.12.0 is not registered in the local machine."
I have tested my code and works in my Windows 7 local machine. Any idea?
There is a problem with Microsoft.ACE.OLEDB.12 when AccessDatabaseEngine x86 or x64 2010 is installed.
I have long attempted to use the SSMS (2005-2008-2008R2-2012) Export Wizards to export large tables onto Excel and I needed the AccessDatabaseEngine installed to be able to do that.
However, regardless of the MS Office version (2010, x86 or x64, or whatever it is), the 2010 version of AccessDatabaseEngine will not work towards registering the provider.
The solution is to download and install the previous one which is none other than the 2007 x86 one.
This one will work even if Office or SQL Server or VS are x64.
Download it from here http://www.microsoft.com/en-us/download/confirmation.aspx?id=23734
Now, any other propagated issues revolving around the notorious failure to register "the provider" on the local machine for the Microsoft.ACE.OLEDB.12 should be resolved by the above.
Feel free to paste me your experiences on this matter.
Hi i have an application developed on XP with Text ODBC drivers. But when i deployed on Win 7 with office 2007, i have connection issues.
<add key="SQLConnection.TextConnectionString" value="Driver={Microsoft Text Driver (*.txt; *.csv)};Dbq=c:\Data\;Extensions=asc,csv,tab,txt;Persist Security Info=False" />
ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
i have googled every solutions like installing the following
http://blogs.msdn.com/b/sqlblog/archive/2009/12/29/how-to-connect-to-file-based-data-sources-microsoft-access-microsoft-excel-and-text-files-from-a-64-bit-application.aspx
Microsoft Access Database Engine 2010 Redistributable (32-bit)
2007 Office System Driver: Data Connectivity Components
after all of those, in my datasources(ODBC), it still only shows "SQL native client/SQL server/SQL server native client"
in the C:\Windows\SysWOW64\odbcad32.exe
i can see all the x32 drivers, but how can i modify my connection strings to access 32-bit Microsoft Text Drivers or are there any alternative solutions?
Thanks
I'm pretty sure it'll work automatically (even on a 64-bit machine) as long as the executing process is 32-bit.
Try recompiling to target x86 specifically.
You need the 64-bit Microsoft Access Database Engine 2010 Redistributable
http://www.microsoft.com/downloads/details.aspx?familyid=C06B8369-60DD-4B64-A44B-84B371EDE16D&displaylang=en
Then try
Microsoft Access Text Driver (*.txt, *.csv)
for the driver name.
AFAIK, all 64-bit ODBC drivers from the Microsoft Access Database Engine 2010 64-bit Redistributable have slightly changed their driver names, I guess to differentiate them from their 32-bit counterparts.
I had this exact problem and the recompiling to target x86 specifically worked! Note that in order to do this I had to specify the Target CPU in the advanced compiler setting dialog - Project Menu> Properties> Compile tab> Advanced Compile Options button.
Before finding this forum entry I did install the Microsoft Access Database Engine 2010 Redistributable (32-bit) but I don't know if that had any affect on this issue.
As mentioned above, when the executing process is 32-bit (in this case compiling against x86 makes the app 32-bit specific) the application will use the drivers from C:\Windows\SysWOW64\odbcad32.exe.
Thanks Cameron.
We were doing this from ASP.Net and got it working on Windows 2012 just by moving the one site into a separate app pool that had "32-bit Enabled" turned on in the advanced settings for the App Pool.
A lot of people seem desperate here, I want to offer a few solutions. But, first I want to highlight what a dated proprietary trash idea from the 90s this is.
Use Unix ODBC to host the text file from Linux which the docs (seem to) claim to support an implementation of the Microsoft text driver
A better option would be of course to import the CSV into PostgreSQL.
I would suggest just doing this with \COPY and dropping the notion of a CSV.
You can maintain the CSV with PostgreSQL acting as a server with the Foreign Data Wrapper (file_fdw).
If you don't want to run an RDBMS, the modern way would be to use SQLite. This is a great idea if you don't need the server/client model.
The ODBC->text interface is especially insane, because ODBC doesn't define configuration beyond connection (so I assume there are lots of assumptions there).
I am following the learning ASP.NET 3.5 by O'REILLY to write some ASP.NET 3.5 code using Visual Studio 2008 SP1. I have gotten to the point to where I need to Configure a Data Source using the SqlDataSource control. I chose Microsoft SQL Server (SqlClient) even though I have SQL Server Express 2005 - This seems like the only logical choice.
I get to the Add Connection window and successfully add a Server name and I use the Select or enter a database name of AdventureWorks. When I click on Test Connection I get the Test Connection Succeeded message box.
Unfortunately, when I click OK I get an error message of the following:
Could not load file or assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=10.0.0.0, Culture=neutral,
PublicKey Token=89845dcd8080cc91' or one of its dependecies. The system cannot find
the file specified.
At his point I am at a loss and everywhere I look and find something similar to my issue it involves other versions of either Visual Studio or SQL Server.
I'd really appreciate any help on this!
You may investigate this recipe.
You may need to reinstall your copy of SQL 2005 Express. But sure to install all of the client-side developer packages in the installer.
I had the exact same issue.
Following the suggestions in this thread , I went to the "Microsoft SQL Server 2008 Feature Pack, August 2008 " - and downloaded (and installed) the "Microsoft SQL Server 2005 Backward Compatibility Components ". This did not help.
Then I also downloaded and installed the following components: SharedManagementObjects.msi, sqlncli.msi, SQLSysClrTypes.msi.
And now it works for me.
I'm using SQL Server 2008 Express and Visual Web Developer 2008 Express Edition.