Accessing Excel files on a x64 machine
In the old times while all the CPUs were 32bit, we were happily using JET OLEDB Provider reaching Excel or MDB files for long time without any issues.
After we started using x64 CPUs and x64 Windows machines, we noticed that JET OLEDB Provider is not working. The reason for this was x64 Windows operating systems were not containing x64 bit JET OLEDB Provider but they had 32bit JET OLEDB Provider. We needed to recompile our applications as 32bit by changing the "Target CPU" as x86 in our Visual Studio Projects (remember that default "Target CPU" fro a Visual Studio Project is "Any CPU"), or using a 32bit application pool for a web application just to be able host our app in a 32bit w3wp.exe.
Now we have a new guy in the town. Let me introduce it : "Microsoft ACE OLEDB Provider". It's "ProgID" (in terms of COM/OLEDB) is "Microsoft.ACE.OLEDB.12". It does not come within the OS, you should install this manually by downloading it from here . The name of the download is "Microsoft Access Database Engine 2010 Redistributable" as this 64bit ACE OLEDB Provider is the result of our Office 2010. It has been around in the scene with Office 2007 but it was available as 32bit only.
With the Office 2010, we have 64bit ACE OLEDB Provider which is good news :)
Here are some cases with the details how to use this new OLEDB Provider :
CASE 1: Retrieving data from an Excel file in SQL Server
Please follow the steps below :
- 1) Download our 64bit version (AccessDatabaseEngine_X64.exe) of our "Microsoft Access Database Engine 2010 Redistributable" from the URL below :
- 2) Install AccessDatabaseEngine_X64.exe on your SQL Server machine
- 3) Open a new "Query Window" in SQL Server Management Studio (SSMS) after connecting to your SQL Server Engine and issue the T-SQL commands below :
USE [master]
GO
sp_configure 'show advanced options', 1
GO
RECONFIGURE WITH OverRide
GO
sp_configure 'Ad Hoc Distributed Queries', 1
GO
RECONFIGURE WITH OverRide
GO
EXEC master.dbo.sp_MSset_oledb_prop N'Microsoft.ACE.OLEDB.12.0' , N'AllowInProcess' , 1
GO
EXEC master.dbo.sp_MSset_oledb_prop N'Microsoft.ACE.OLEDB.12.0' , N'DynamicParameters' , 1
GO
- 4) Now try executing the query below :
select * FROM OPENROWSET('Microsoft.ACE.OLEDB.12.0', 'Excel 12.0;Database=C:\temp\test.xls', [Sheet1$])
Yuppe I got the data from XLS :)
CASE 2: Retrieving data from an Excel file in a .NET app
- 1) Download our 64bit version (AccessDatabaseEngine_X64.exe) of our "Microsoft Access Database Engine 2010 Redistributable" from the URL below :
- 2) Install AccessDatabaseEngine_X64.exe on your x64 machine (Likely that it will be your web server which will be hosting your ASP.NET app in a 64bit app pool or the server that you will run your .NET Windows Service as 64bit etc.)
- 3) Use the System.Data.OleDBConnection with the connection string below :
OleDbConnection conn = new OleDbConnection("Provider=Microsoft.ACE.OLEDB.12.0;Data Source=c:\\temp\\test.xls;Extended Properties=\"Excel 12.0;HDR=YES;\"");
P.S. 1 : If you are going to deploy this app to a machine without ACE OLEDB Provider, don't forget that you should install "Microsoft Access Database Engine 2010 Redistributable" to the target machine.
P.S. 2 : If you have Office 2010 32bit is installed on the machine you cannot install "Microsoft Access Database Engine 2010 Redistributable" 64bit .
Comments
Anonymous
June 16, 2010
Awsome information. The Excel connection string change tricked me. Assumed it would automatically increment from 12 to 14.Anonymous
June 22, 2010
The comment has been removedAnonymous
July 30, 2010
This is great news! However, when I install on 64bit WinServer2008 and attempt to access an Excel file I get: The 'Provider=Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine. The application has properly installed (I can see it in Add/Remove programs). I noticed that the version there is 14.0. Should the OleDb connection look like below? OleDbConnection conn = new OleDbConnection("Provider=Microsoft.ACE.OLEDB.14.0;Data Source=c:\temp\test.xls;Extended Properties="Excel 12.0;HDR=YES;"");Anonymous
August 01, 2010
The comment has been removedAnonymous
August 02, 2010
Do I still have to do all these steps if U already have installed 64-bit Office 2010?Anonymous
August 02, 2010
Hi Oskar, If you check the download page for "Microsoft Access Database Engine 2010 Redistributable", the "Overview" paragraph has an explanation answering your situation. Here's the quote from its download page : ========================================== The 2007 Office System Driver are not intended: As a general replacement for Jet (If you need a general replacement for Jet you should use SQL Server Express Edition). As a replacement for the Jet OLEDB Provider in server-side applications. As a general word processing, spreadsheet or database management system -To be used as a way to create files. (You can use Microsoft Office or Office automation to create the files that Microsoft Office supports.) To be used within a service program or web application that relies on a Windows service. ========================================== So, neither ACE OLEDB Provider (either 32bit or this new 64bit) nor our good old friend Jet OLEDB Provider intended to be used in mult-threaded applciations like web applications. Best Regards, Faruk CelikAnonymous
August 17, 2010
Hi Faruk, according to your P.S. 2 you say that it is not pssible to install "Microsoft Access Database Engine 2010 Redistributable" 64bit when MS Office 2010 32bit is installed. This is only true if you call AccessDatabaseEngine_X64.exe without any arguments. But when you call AccessDatabaseEngine_X64.exe /passive then is installs with no complaints in parallel with ian existing 32bit counter part. Best Regards, Andreas MarschallAnonymous
September 22, 2010
So, how would one interact with Office in files in an environment like Oskar’s above?Anonymous
October 12, 2010
The comment has been removedAnonymous
November 17, 2010
Hi Faruk, Regarding the quote "The 2007 Office System Driver are not intended: As a general replacement for Jet (If you need a general replacement for Jet you should use SQL Server Express Edition). As a replacement for the Jet OLEDB Provider in server-side applications. " If this is NOT INTENDED for server side use, then what it? Do you know any supported way to read Excel files and Access db:s at the SQL Server machine? Regards Hans SAnonymous
January 22, 2011
Hi everyone! I'm trying to access Excel files using this instructions and am able to open XLS files but when trying to open XLSX files I get a "External table is not in the expected format" error... Details at: social.microsoft.com/.../e294886f-9dac-4d1a-b927-5d10ac6d25db I really need to open XLSX files so I would very much appreciate your helpAnonymous
January 22, 2011
Hello everyone! I'm having the problem with opening XLSX files (External table not in a recognized format) described here: social.microsoft.com/.../c407ada2-4a37-4d77-af4b-ce31a6fb9259 Aby help would be very much appreciatedAnonymous
January 30, 2011
Andreas, thanks for the information. How do we then select the correct (64-bit) version through the program? Do we need to change the connection string in any way?Anonymous
March 11, 2011
Thanks a million. This problem was pestering me for some time. I tried changing the connection string , but the AccessDatabaseEngine saved meAnonymous
March 11, 2011
In response to Michael's question "Do I still have to do all these steps if U already have installed 64-bit Office 2010?" No you don't. But if yo've installed Office 2010 on your server please be sure that you're not doing "Office Automation" which will need Excel.exe, WinWord.exe etc. to be spawned. Here's the KB article about "Office Automation" ===> support.microsoft.com/.../257757Anonymous
March 21, 2011
hi i couldnot install AccessDatabaseEngine_X64.exe, it says i have to remove 32-bit office products. does it mean i have to uninstall the office 2010 i have on the computer? I have 64-bit windows and office 2010.Anonymous
April 09, 2011
Thanks very much!Anonymous
April 30, 2011
The comment has been removedAnonymous
May 01, 2011
@Wyatt, As you already have Office 2010 x64 installed on your machine, you have x64 version of 'Microsoft.ACE.OLEDB.12.0' OLEDB Provider is installed. Visual Studio 2010 (or 2008, 2005) IDE itself is a 32bit process named "devenv.exe" (You can check from "Task Manager", you will "*32" next to devenv.exe like "devenv.exe *32"). We don't have 64bit version of Visual Studio 2010 (or the old ones), it is/was always 32bit. As devenv.exe (Visual Studio 2010 for your scenario) is a 32bit process, it cannot reach 64bit 'Microsoft.ACE.OLEDB.12.0' OLEDB Provider or any 64bit OLEDB provider at all. So, you have to have 32bit version of 'Microsoft.ACE.OLEDB.12.0' OLEDB Provider. Please download AccessDatabaseEngine_x86.exe to have 32bit version of 'Microsoft.ACE.OLEDB.12.0' OLEDB Provider on your machine. I'm not sure if it will allow you to have installed on your machine as you have Office 2010 x64. If it says "sorry, you have 64bit Office I cannot install 32bit AccessDatabaseEngine_x86), you will have to uninstall your Office 2010 x64 and install Office 2010 x86. Hope that helps. Regards, FarukAnonymous
May 01, 2011
I have downloaded the 32-bit AccessDatabaseEngine.exe and it will NOT allow me to install since it detected that I have installed Office x64. I knew the VS2010 is a 32-bit application. It seems the problem is similar to Outlook x64 cannot ActiveSync with Windows Phone 6.5 because WMDC 64-bit driver is calling the 32-bit version instead of a "real" 64-bit driver. I think the Office x64 is of no use because of incompatibility with all other 32-bit applications. As such, I would like to ask what is the "use" of the AccessDatabaseEngine_x64.exe as various guys have mentioned in this comment history ?Anonymous
May 01, 2011
I have finally uninstalled Office 2010 x64 and installed back Office 2010 x86, now VS2010 can connect to the Access 2010 .accdb files successfully.Anonymous
May 01, 2011
"AccessDatabaseEngine_x86.exe" and "AccessDatabaseEngine_x64.exe" is a runtime for you to have ACE on your "Server" machines on production. In case if your applications need to connect to .accdb, .xlsx etc. files as data source. We do not suggest installing whole Microsoft Office on a server as it's not intended to be used on server machines but consumer (Information Worker, IW) desktop machines.Anonymous
May 03, 2011
I want to know how to detect the Access Database Engine 2010 ""AccessDatabaseEngine_x86.exe" and "AccessDatabaseEngine_x64.exe" has already installed or not to a server or desktop machine ?Anonymous
May 17, 2011
The comment has been removedAnonymous
May 17, 2011
H Vinnicius, Please use our tool Process Explorer (technet.microsoft.com/.../bb896653) and Ctrl-F (Find handle or substring) and type your .accdb or .xlsx file you're trying to connect. It will show you the process using your .accdb or .xlsx file. HTH :) By the way you're English is not bad ;)Anonymous
May 27, 2011
I have Office 2010 64-bits installed under Windows 7 64-bits, however when I try to read in SSIS 2008 a .xlsx file, the following message appears: The 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine. Why is that?Anonymous
July 08, 2011
Nel passato, quando tutte le CPU erano a 32bit, ognuno di noi ha avuto il piacere di utilizzare almenoAnonymous
July 09, 2011
@Francisco As BIDS (Business Intelligence Development Studio) tool itself is a 32bit process (devenv.exe, you can check it from Task Manager), it cannot reach 64bit ACE OLEDB Provider. You should have 32bit ACE OLEDB Provider installed on your machine. But you cannot install 32bit ACE runtime on a machine with Office 2010 64bit installed. You should uninstall your 64bit Office 2010 and either install 32bit Office 2010 as a whole product or just 32bit ACE Runtime, because you cannot have 64bit and 32bit ACE runtime in the same machine.Anonymous
July 09, 2011
@Wyatt Wong, Ona 64bit OS;
- If 32bit is installed "ACEOLEDB.DLL" should exists here : C:Program Files (x86)Common FilesMicrosoft SharedOFFICE14ACEOLEDB.DLL
- If 64bit is installed "ACEOLEDB.DLL" should exists here : C:Program FilesCommon FilesMicrosoft SharedOFFICE14ACEOLEDB.DLL On a 32bit OS; "ACEOLEDB.DLL" should exists here : C:Program FilesCommon FilesMicrosoft SharedOFFICE14ACEOLEDB.DLL HTH, Faruk
Anonymous
July 15, 2011
Remember to check files using the CommonProgramFiles CommonProgramFiles(x86) CommonProgramW6432 env. variables or other solution.Anonymous
August 04, 2011
Quick Question: I have developed a program (VB.NET) on a x86 XP machine that uses OLEDB to read a .XLSX file. The program runs fine on all other x86 machines in the office. However, I would like it to be able to run on the X64 W7 machines we have here too, but am not succeeding. The x64 machines have x86 Office installed. I tried installing the x86 Access Connectivity Engine (b/c I can't install the x64 version with x86 Office on the computer), but no cigar. My target CPU in Visual Studio on the xp machine while developing is "Any CPU". Any idea what I need to do to get this to work for both 32 and 64-bit?Anonymous
August 22, 2011
The comment has been removedAnonymous
September 16, 2011
Hi, I'm not able to install the AccessDatabaseEngine_X64. it gives me an error installation of the package failed. can u pls help me out with this.Anonymous
September 18, 2011
@Mahalakshmi S, If you're receiving an error message during the installationcould you please share ? Also I will need the answers to the questions below : 1)Which OS you're trying to install AccessDatabaseEngine_X64 on ? (Please don't forget to add the CPU version x86, x64 of your OS)
- Do you have Microsoft Office installed on your machine ? If it is, which Microsoft Office version (2007, 2010) is installed ? If it is Office 2010, is it 32bit or 64bit ?
Anonymous
September 18, 2011
The comment has been removedAnonymous
September 22, 2011
Hi Faruk, In my machine MS office 2010 64-bit version installed but still I get below error. "The 'Microsoft.Jet.OLEDB.12.0' provider is not registered on the local machine."Anonymous
October 06, 2011
I am using VS 2010 and created a page that imports data from xlsx file. connection string "Provider=Microsoft.ACE.OLEDB.12.0;Data Source=" + strFilePath + "; Extended Properties="Excel 12.0;HDR=No;IMEX=1;TypeGuessRows=0;ImportMixedTypes=Text"";" When i run it in VS environment it runs well and the data is imported. but as soon as i try to run it from IIS as virtual Directory i get the problem "The 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine." When i try to build the application with x86 and try to run the application it fails with the error "Could not load file or assembly 'FinRep' or one of its dependencies. An attempt was made to load a program with an incorrect format. " I have checked registry entry and it seems ACE.OLEDB.12.0 is already registered there. Please help. Thanks GunjanAnonymous
October 27, 2011
As Andreas Marschall wrote in his post above, it is possible to install the Access Database Engine in the passive mode. AccessDatabaseEngine_X64.exe /passive If your programm is still not runing, you could install the 32 bit version in the passive mode too. After that your programm should run (also if you choose "Any CPU" in VS). (It worked for me) Regards I.PfeiferAnonymous
October 27, 2011
Mahalkhshmi, Could you please do 64bit and 32bit UDL Test and let me know in which one(s) you see "Microsoft Office 12.0 Access Database Engine OLE DB Provider" in "Provider" list. Here are my blog posts for "UDL Test" (s) .
- 64bit UDL Test on a 64bit OS ==> blogs.msdn.com/.../basics-first-udl-test.aspx[TR]-loc-[Services]-[farukc]
- 32bit UDL Test on a 64 bit OS ==> blogs.msdn.com/.../udl-test-on-a-64-bit-machine.aspx[TR]-loc-[Services]-[farukc] Thanks
Anonymous
October 27, 2011
The comment has been removedAnonymous
October 31, 2011
this driver does not work, installed 64-bit drivers, rebooted server 2008 R2, but getting the same error as most of the users here are getting .... driver is not registered...Anonymous
October 31, 2011
i have VS 2010 while reading Excel sheet from MS Office 32 bit. I installed the 32 OLE provider but i got the error "Could not find installable ISAM." any help?Anonymous
October 31, 2011
The comment has been removedAnonymous
October 31, 2011
@Mohamed Zaatar Are you receiving "Could not find installable ISAM" when running the app inside Visual Studio or outside of Visual Studio ? As I'm repeating in my comments above, please do "UDL Test"s on your machine to see if the "ACE OLEDB Provider" is working fine first. If you get the "Could not find installable ISAM" through "UDL Test"s too, please uninstall/re-install the 32bit ACEOLEDB provider please let me know :
- Your Office version
- You OS version (together with the CPU version : x86 ? x64 ?)
- What is the Excel ifle extension (xlsx ? xlsm ? xls ? etc.)
- What is your application type ? (consol app, windows forms app, ASP.NET web app etc ; if it is a web app what is your application pool bitness 32bit or 64bit ?)
Anonymous
November 25, 2011
I have this code working on 64-bit Win 7 / Excel 2010. Note the ISAM=1 extended property - this fixed the "Could not find installable ISAM." problem for me. Presumably it will be the same for 32-bit Excel public void Method2() { string cStr = "Provider=Microsoft.ACE.OLEDB.12.0; " + "Data Source=C:\users<yourname>\documents\Book1.xlsx; " + "Extended Properties="Excel 12.0;HDR=YES;IMEX=1;ISAM=1;""; OleDbConnection conn = new OleDbConnection(cStr); conn.Open(); // Select the data from Sheet1 of the workbook. string stmt = "select * from [Sheet1$]"; OleDbDataAdapter ada = new OleDbDataAdapter(stmt, conn); DataSet ds = new DataSet(); ada.Fill(ds); dataGridView1.DataSource = ds.Tables[0].DefaultView; dataGridView1.AutoSizeColumnsMode = DataGridViewAutoSizeColumnsMode.AllCells; conn.Close(); }Anonymous
December 15, 2011
After the succesful installation I have created a linked server from SQL Server 2008 R2 to a Access database on a network file share. I always get a error when the file is still in use. I don't have this Problem form a linked server from a 32Bit SQL Server. Is there a way that this also works from 64Bit ?? Thanks very much.Anonymous
May 16, 2012
The comment has been removedAnonymous
June 13, 2012
On Win 2008 Server 64 bit , If i install 32 bit ACE oledb driver and run application with dlls built on ANY CPU configuration is not working .it is giving ACE driver not registered error.. any help would be appreciated .Anonymous
December 10, 2012
Thanks for the detailed reasoning and solutionAnonymous
July 12, 2013
Excellent article. Thanks!Anonymous
July 12, 2013
Regarding using Microsoft.ACE.OLEDB.12.0 in a web application, does it mean that this provider cannot be used in any web application?Anonymous
November 22, 2013
I have Office 365 32-bit, Visual Studio Express 2013 32-bit, Microsoft.ACE.OLEDB.12.0 provider 32-bit, Windows 8.1. Adding a data connection, the "test connection" button succeeds, but at runtime I still get "Microsoft.ACE.OLEDB.12.0 provider is not registered on the local machine". I had to un-install OLEDB* 64-bit and install 32-bit to get this far, but not far enough... Any suggestions?Anonymous
July 22, 2014
@faruk I don't know if you are still responding to these blog comments. If you are I have a web app with an excel file embedded in the app. When I run the app on the development machine which has Office 2010 installed it works fine. When I install the app on the Server on which I have run the AccessDatabaseEngine_x64.exe , then it will initiate the connect successfully but throw an error on the Query SELECT * FROM [SHEET1$] saying it can't find a sheet1$. The only thing I've been able to find is a bunch of people suggesting that maybe the file doesn't have a sheet1$, which is of course ridiculous. So I am wondering if you had any ideas one why the query doesn't work.Anonymous
July 22, 2014
I have a web app with an excel file embedded in the app. When I run the app on the development machine which has Office 2010 installed it works fine. When I install the app on the Server on which I have run the AccessDatabaseEngine_x64.exe , then it will initiate the connect successfully but throw an error on the Query SELECT * FROM [SHEET1$] saying it can't find a sheet1$. The only thing I've been able to find is a bunch of people suggesting that maybe the file doesn't have a sheet1$, which is of course ridiculous. So I am wondering if you had any ideas one why the query doesn't work.Anonymous
July 24, 2014
Is it possible to use a Excel Spreadsheet that is in some network address? For example \serverfoldersheet1.xlsx ? Here in my computer it doesn't seem to work.Anonymous
August 12, 2014
the correct solution has been provided by Andreas above. I have 32 bit office on windows 7 64 bit Andreas Marschall 18 Aug 2010 12:15 AM # Hi Faruk, according to your P.S. 2 you say that it is not possible to install "Microsoft Access Database Engine 2010 Redistributable" 64bit when MS Office 2010 32bit is installed. This is only true if you call AccessDatabaseEngine_X64.exe without any arguments. But when you call AccessDatabaseEngine_X64.exe /passive then is installs with no complaints in parallel with an existing 32bit counter part. Best Regards, Andreas MarschallAnonymous
September 22, 2014
I get the: "The Microsoft Access database engine cannot open or write to the file ''. It is already opened exclusively by another user, or you need permission to view and write its data" Error. It occurs when running a mailmerge between Excel & Word and sends the word mail files as attachments to email addresses using outlook, all the code is in a VBA script in the source excel file. This worked fine in XP & office 2010 (32 bit), it gets about 25% of the way through the exercise (so sends some fine) but then falls over. Currently running W7E 64bit SP1 & Office 2010. Is this related to the Jet DB issue and will patching my local client with the redistributable file be OK? Sorry I'm just a n Excel user rather than an IT developer so not sure if this make sense.Anonymous
September 22, 2014
I don't think that the issue you are experiencing is related to the one I'm explaining in this blog post. I will suggest you to ask this in Microsoft Forums here : social.technet.microsoft.com/.../homeAnonymous
September 23, 2014
Thank you for information Faruk. Also thanks for humorous wording. :)Anonymous
September 23, 2014
Thanks for responding Faruk I'll try over there.Anonymous
September 29, 2014
The comment has been removedAnonymous
September 29, 2014
Hello Sandy, It looks like your app is an ASP.NET app because the callstack/stack trace in the error shows calls from System.Web namespace. It is possible that you are getting the 0x80004005 error because your IIS application pool's identity cannot reach to the file you specified in "excelFilePath". Please check this first. Also, JET OLEDB provider will need to create .tmp files under %temp% folder of the user running the process hosting it. In this case, process is w3wp.exe and the user running the process is the application pool identity you set. Please try "Response.Write"ing the %TEMP% environmental variable (Refer to : msdn.microsoft.com/.../77zkk0b6(v=vs.110).aspx ). In this way you will see the %TEMP% folder for the current user/applicaiton pool identity running your application pool. You should grant read/write access to the %temp% folder. Our free tool "Process Monitor" (technet.microsoft.com/.../bb896645.aspx) will be your best friend to see the file activities. You should find your w3wp.exe, add a filter to it and see if it gets any "ACCESS DENIED" for any of its calls. Hope that helpsAnonymous
September 29, 2014
Hi Faruk, You simply rock. Thanks for your prompt reply. Yes i did install the process monitor and saw that one of the temp folder inside 64 bit windows 2008 was not having proper permissions. it was right here C:windowsservicesserviceprofilesnetworkserviceappdatatemp. The issue is now resolved. Thanks BTW: I am having another DCom related issue related to word 2010 access. Is this the right forum i can post my question? Please let me know.Anonymous
October 23, 2014
After AccessDatabaseEngine_X64.exe /passive my application works, but latter when I start excel it goes into a repair mode, after that I am no longer able to connect in x64. What am I missing?Anonymous
November 07, 2014
Hi Sandy, It's good to hear that your issue is resolved :) For your DCOM issue I will suggest checking our MSDN Forums. A search for "dcom" keyword in MSDN forums bring lots of things : social.msdn.microsoft.com/.../home HTH, farukAnonymous
December 03, 2014
The comment has been removedAnonymous
January 13, 2015
The comment has been removedAnonymous
January 13, 2015
Hi T Neahr, SSMS is a 32bit process and actually you are spawning another 32bit process (C:Program Files (x86)Microsoft SQL Server100DTSBinnDTSWizard.exe) as well when you ran Import/Export Wizard. We have 64bit version of DTSWizard.exe located in C:Program FilesMicrosoft SQL Server100DTSBinnDTSWizard.exe . You can run this directly instead of selecting "Tasks/Import Data" (or Export Data) database context menu item while you're in SSMS. As you have MS Access 2010 64bit installed on your machine, you already have ACE in 64bit and you should see ACE OLEDB provider in the combobox when you ran 64bit DTSWizard. Thanks, FarukAnonymous
January 14, 2015
Faruk, Thanks for the response. I'll keep investigating this topic as I only have 'MSDTSSrver.ini.xml' in the directory of C:Program FilesMicrosoft SQL Server100DTSBinn. I located the DTSWizard.exe in a different directory: C:Program FilesMicrosoft SQL Server120DTSBinn. Thanks, T NeahrAnonymous
January 14, 2015
Hi T Neahr, My bad, I gave the path for 100 which is SQL Server 2008 or 2008 R2 (90 is for SQL Server 2005, 100 is for 2008/2008R2, 110 is for SQL 2012 and 120 is for SQL 2014). Looks like you have SSMS of SQL 2014 and it is also ok to use it as long as it is 64bit. Regards, FarukAnonymous
February 01, 2015
My VM is 64Bit OS, I am using 32 bit MS Office 2007, I have a procedure, which will fetch the data from 2007 compatible excel file (.xlsx) and insert into a sql server 2008 R2 64 bit environment, I amusing the below method for getting the excel data: select n.* into #TempNewSales from( select x.[HSQ_DATE] 'HSQ_DATE',c.[COM_CompanyID] 'COM_CompanyID', c.COM_Full_Name 'COM_Full_Name',X.[COMPANY_NP_NAME] 'COMPANY_NP_NAME' ,X.[SALES] 'Sales','N' 'Updated',x.Name 'UserName' FROM OPENROWSET( 'Microsoft.ACE.OLEDB.12.0', 'Excel 12.0;HDR=YES;Database=\hdrexample.xlsx', 'Select * from [1947$]')x if I copy the entire sql and past it my excel file->data-Get data from other sources, by selecting the the command type is SQL and click on OK, I am getting the desired output in Excel. But If I open the same excel file in another VM, which has 32 bit environment and only excel is installed, where as my VM has full office installed. it throws the error, unable to connect database with "Microsoft.ACE.OLEDB.12.0 failed to connect But there is no error from my end, when I used the same excel file for call that procedure Please helpAnonymous
June 30, 2016
help me! I dnag problems importing data, currently I'm đùng Offic 2013, Visual Studio 2013 environment and SQL server 2012 .. I try to take all measures to import data but I've got this error message "Additional information: The 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine. "Help me!. thank you very much!Anonymous
September 02, 2016
My problem is the error, "Could not find installable ISAM". I have Windows 10 and Visual Studio 2015 Community and Access (Office 365). When I try to connect with a database, I hit this error. Everything is 64-bit including Target CPU. I have tried reinstalling everything. The error persists. Do you know why?