hi,

    I have two servers and both are of 64bit Windows server 2003 OS. I am getting the error "The Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine" in one server only.

FYI.. I can see "office12" folder in one server(where it is working fine) in the location"C:\Program Files(x86)\Common Files\Microsoft Shared\OFFICE12" but not on the ther one. On the other server(where i am getting the error) is having "office11" folder in the same location. Could you please help.

Is it a problem with Access Database Engine ?

Hi,

I think this issue is caused by you are running 64-bit windows and there are no MS Access drivers that run 64-bit. So I suggest you trying to change your build configuration to x86. You can do that on the project properties dialog under "Compile>Advanced Compile Options...>Target CPU". Change it to "x86". Then clean and rebuild your solution.

Hope that helps.

• Proposed as answer by emaraszek Friday, November 30, 2012 9:45 PM

Hi,

I think this issue is caused by you are running 64-bit windows and there are no MS Access drivers that run 64-bit. So I suggest you trying to change your build configuration to x86. You can do that on the project properties dialog under "Compile>Advanced Compile Options...>Target CPU". Change it to "x86". Then clean and rebuild your solution.

Hope that helps.

• Proposed as answer by emaraszek Friday, November 30, 2012 9:45 PM

Hi,

I think this issue is caused by you are running 64-bit windows and there are no MS Access drivers that run 64-bit. So I suggest you trying to change your build configuration to x86. You can do that on the project properties dialog under "Compile>Advanced Compile Options...>Target CPU". Change it to "x86". Then clean and rebuild your solution.

Hope that helps.

• Proposed as answer by emaraszek Friday, November 30, 2012 9:45 PM

Hi,

    Thanks for your reply, but if I run the same build in other servers(of same 64 bit OS version) it is running fine. I am facing this problem only, if i try to read any excel file of 2007 version(.xlsx), but not .xls files. I am trying to read those files from VB.net application.

     FYI... I can see "MS Access Database Engine 2007" in "Add and Remove" programes of other servers, where it is running fine. So, will that help, if I install "MS Access Database Engine" in this server as well.

http://www.microsoft.com/downloads/en/details.aspx?familyid=7554F536-8C28-4598-9B72-EF94E038C891&displaylang=en  

 

• Marked as answer by geek_jumper Friday, November 19, 2010 5:36 AM

Hi,

    Thanks for your reply, but if I run the same build in other servers(of same 64 bit OS version) it is running fine. I am facing this problem only, if i try to read any excel file of 2007 version(.xlsx), but not .xls files. I am trying to read those files from VB.net application.

     FYI... I can see "MS Access Database Engine 2007" in "Add and Remove" programes of other servers, where it is running fine. So, will that help, if I install "MS Access Database Engine" in this server as well.

http://www.microsoft.com/downloads/en/details.aspx?familyid=7554F536-8C28-4598-9B72-EF94E038C891&displaylang=en  

 

• Marked as answer by geek_jumper Friday, November 19, 2010 5:36 AM

Hi,

    Thanks for your reply, but if I run the same build in other servers(of same 64 bit OS version) it is running fine. I am facing this problem only, if i try to read any excel file of 2007 version(.xlsx), but not .xls files. I am trying to read those files from VB.net application.

     FYI... I can see "MS Access Database Engine 2007" in "Add and Remove" programes of other servers, where it is running fine. So, will that help, if I install "MS Access Database Engine" in this server as well.

http://www.microsoft.com/downloads/en/details.aspx?familyid=7554F536-8C28-4598-9B72-EF94E038C891&displaylang=en  

 

• Marked as answer by geek_jumper Friday, November 19, 2010 5:36 AM

Hi,

I think this issue is caused by you are running 64-bit windows and there are no MS Access drivers that run 64-bit. So I suggest you trying to change your build configuration to x86. You can do that on the project properties dialog under "Compile>Advanced Compile Options...>Target CPU". Change it to "x86". Then clean and rebuild your solution.

Hope that helps.

that's true if you are working in a 64-bit machine. Change the compile option to X86 solved my issue. Thanks a lot!

• Proposed as answer by Liudi90 Wednesday, April 25, 2012 2:19 AM

Hi,

I think this issue is caused by you are running 64-bit windows and there are no MS Access drivers that run 64-bit. So I suggest you trying to change your build configuration to x86. You can do that on the project properties dialog under "Compile>Advanced Compile Options...>Target CPU". Change it to "x86". Then clean and rebuild your solution.

Hope that helps.

that's true if you are working in a 64-bit machine. Change the compile option to X86 solved my issue. Thanks a lot!

• Proposed as answer by Liudi90 Wednesday, April 25, 2012 2:19 AM

Hi,

I think this issue is caused by you are running 64-bit windows and there are no MS Access drivers that run 64-bit. So I suggest you trying to change your build configuration to x86. You can do that on the project properties dialog under "Compile>Advanced Compile Options...>Target CPU". Change it to "x86". Then clean and rebuild your solution.

Hope that helps.

that's true if you are working in a 64-bit machine. Change the compile option to X86 solved my issue. Thanks a lot!

• Proposed as answer by Liudi90 Wednesday, April 25, 2012 2:19 AM

Sorry if this is bringing up an old thread, but google returned this to me and I solved the problem myself, so I thought I would explain my different solution.

I also received this error about Microsoft.ACE.OLEDB.12.0 not being registered on the local machine. I tried changing my build to x86 as suggested. Still didn't work. Finally, I realized that I don't have Access 2007, I have the 2010 version. Don't know if that matters, but I do know that installing the 2007 Office System Driver: Data Connectivity Components did solve the problem. Hope it helps!

• Proposed as answer by David Schlum Friday, September 09, 2011 9:56 PM
• Marked as answer by David Wolters Monday, March 12, 2012 6:21 PM

Sorry if this is bringing up an old thread, but google returned this to me and I solved the problem myself, so I thought I would explain my different solution.

I also received this error about Microsoft.ACE.OLEDB.12.0 not being registered on the local machine. I tried changing my build to x86 as suggested. Still didn't work. Finally, I realized that I don't have Access 2007, I have the 2010 version. Don't know if that matters, but I do know that installing the 2007 Office System Driver: Data Connectivity Components did solve the problem. Hope it helps!

• Proposed as answer by David Schlum Friday, September 09, 2011 9:56 PM
• Marked as answer by David Wolters Monday, March 12, 2012 6:21 PM

Sorry if this is bringing up an old thread, but google returned this to me and I solved the problem myself, so I thought I would explain my different solution.

I also received this error about Microsoft.ACE.OLEDB.12.0 not being registered on the local machine. I tried changing my build to x86 as suggested. Still didn't work. Finally, I realized that I don't have Access 2007, I have the 2010 version. Don't know if that matters, but I do know that installing the 2007 Office System Driver: Data Connectivity Components did solve the problem. Hope it helps!

• Proposed as answer by David Schlum Friday, September 09, 2011 9:56 PM
• Marked as answer by David Wolters Monday, March 12, 2012 6:21 PM

Sorry if this is bringing up an old thread, but google returned this to me and I solved the problem myself, so I thought I would explain my different solution.

I also received this error about Microsoft.ACE.OLEDB.12.0 not being registered on the local machine. I tried changing my build to x86 as suggested. Still didn't work. Finally, I realized that I don't have Access 2007, I have the 2010 version. Don't know if that matters, but I do know that installing the 2007 Office System Driver: Data Connectivity Components did solve the problem. Hope it helps!

I was getting the same error when trying to import data from an Excel 2007 Spreadsheet into a SQL Server 2008 R2 database using SQL Server 2008 R2 Management Studio. I also had Office 2010 installed instead of Office 2007. I was able to fix the issue using tom.anderson's suggestion of installing the 2007 Office System Driver: Data Connectivity Components.

• Proposed as answer by Mesillaguy Tuesday, December 27, 2011 2:42 PM

Sorry if this is bringing up an old thread, but google returned this to me and I solved the problem myself, so I thought I would explain my different solution.

I also received this error about Microsoft.ACE.OLEDB.12.0 not being registered on the local machine. I tried changing my build to x86 as suggested. Still didn't work. Finally, I realized that I don't have Access 2007, I have the 2010 version. Don't know if that matters, but I do know that installing the 2007 Office System Driver: Data Connectivity Components did solve the problem. Hope it helps!

I was getting the same error when trying to import data from an Excel 2007 Spreadsheet into a SQL Server 2008 R2 database using SQL Server 2008 R2 Management Studio. I also had Office 2010 installed instead of Office 2007. I was able to fix the issue using tom.anderson's suggestion of installing the 2007 Office System Driver: Data Connectivity Components.

• Proposed as answer by Mesillaguy Tuesday, December 27, 2011 2:42 PM

Sorry if this is bringing up an old thread, but google returned this to me and I solved the problem myself, so I thought I would explain my different solution.

I also received this error about Microsoft.ACE.OLEDB.12.0 not being registered on the local machine. I tried changing my build to x86 as suggested. Still didn't work. Finally, I realized that I don't have Access 2007, I have the 2010 version. Don't know if that matters, but I do know that installing the 2007 Office System Driver: Data Connectivity Components did solve the problem. Hope it helps!

I was getting the same error when trying to import data from an Excel 2007 Spreadsheet into a SQL Server 2008 R2 database using SQL Server 2008 R2 Management Studio. I also had Office 2010 installed instead of Office 2007. I was able to fix the issue using tom.anderson's suggestion of installing the 2007 Office System Driver: Data Connectivity Components.

• Proposed as answer by Mesillaguy Tuesday, December 27, 2011 2:42 PM

Thanks.

Saved me time...

This an happen because of mismatch in application compiler settings and xBits version installed on a syste. Refer http://yoursandmyideas.wordpress.com/2011/02/05/how-to-read-or-write-excel-file-using-ace-oledb-data-provider/

Thanks David -- That solution worked perfectly!

If you have 64 bit machine and 32 bit office 2010 intsall on your machine and you are getting the above error then follow the below link.

http://www.arboundy.com/2010/11/the-microsoft.ace.oledb.12.0-provider-is-not-registered-on-the-local-machine/

 

 

Thanks

Shukraj khadse

• Edited by Shukraj Khadse Thursday, January 19, 2012 11:44 AM
• Proposed as answer by Shukraj Khadse Thursday, January 19, 2012 11:44 AM

If you have 64 bit machine and 32 bit office 2010 intsall on your machine and you are getting the above error then follow the below link.

http://www.arboundy.com/2010/11/the-microsoft.ace.oledb.12.0-provider-is-not-registered-on-the-local-machine/

 

 

Thanks

Shukraj khadse

• Edited by Shukraj Khadse Thursday, January 19, 2012 11:44 AM
• Proposed as answer by Shukraj Khadse Thursday, January 19, 2012 11:44 AM

If you have 64 bit machine and 32 bit office 2010 intsall on your machine and you are getting the above error then follow the below link.

http://www.arboundy.com/2010/11/the-microsoft.ace.oledb.12.0-provider-is-not-registered-on-the-local-machine/

 

 

Thanks

Shukraj khadse

• Edited by Shukraj Khadse Thursday, January 19, 2012 11:44 AM
• Proposed as answer by Shukraj Khadse Thursday, January 19, 2012 11:44 AM

In my scenario I had no issue with 32-bit Office 2010 running on 64-bit windows 7.
However, with 64-bit Office 2010, I encountered the Microsoft.ACE.OLEDB.12.error.  The installation of 2007 Office System Driver: Data Connectivity Components resolved it.

Thank you, Mr. Anderson. 

Thank You tom.anderson ! 2007 Office System Driver: Data Connectivity Components did solve the problem!

Cheers, Stephan

(Win7 Enterprise x64; Office Pro 2010 x64; VS C#

Thanks a Ton!!!...It really saved me a lot of time

Hi,

I think this issue is caused by you are running 64-bit windows and there are no MS Access drivers that run 64-bit. So I suggest you trying to change your build configuration to x86. You can do that on the project properties dialog under "Compile>Advanced Compile Options...>Target CPU". Change it to "x86". Then clean and rebuild your solution.

Hope that helps.

This worked for me on a 64-bit server with Visual Studio 2012 and Access 2010 (x86) installed

• Proposed as answer by CodeGirl19 Tuesday, September 03, 2013 4:06 PM
• Unproposed as answer by CodeGirl19 Tuesday, September 03, 2013 4:07 PM

Hi,

I think this issue is caused by you are running 64-bit windows and there are no MS Access drivers that run 64-bit. So I suggest you trying to change your build configuration to x86. You can do that on the project properties dialog under "Compile>Advanced Compile Options...>Target CPU". Change it to "x86". Then clean and rebuild your solution.

Hope that helps.

This worked for me on a 64-bit server with Visual Studio 2012 and Access 2010 (x86) installed

• Proposed as answer by CodeGirl19 Tuesday, September 03, 2013 4:06 PM
• Unproposed as answer by CodeGirl19 Tuesday, September 03, 2013 4:07 PM

Hi,

I think this issue is caused by you are running 64-bit windows and there are no MS Access drivers that run 64-bit. So I suggest you trying to change your build configuration to x86. You can do that on the project properties dialog under "Compile>Advanced Compile Options...>Target CPU". Change it to "x86". Then clean and rebuild your solution.

Hope that helps.

This worked for me on a 64-bit server with Visual Studio 2012 and Access 2010 (x86) installed

• Proposed as answer by CodeGirl19 Tuesday, September 03, 2013 4:06 PM
• Unproposed as answer by CodeGirl19 Tuesday, September 03, 2013 4:07 PM

See here:

http://kambiz-na.blogspot.com/2012/12/microsoftaceoledb120-provider-is-not.html

Thanks a lot Tom. I had the same issue and solved following the above steps. 

• Edited by SQL KD Tuesday, February 12, 2013 6:25 PM

Thanks a lot Tom. I had the same issue and solved following the above steps. 

• Edited by SQL KD Tuesday, February 12, 2013 6:25 PM

Thanks a lot Tom. I had the same issue and solved following the above steps. 

• Edited by SQL KD Tuesday, February 12, 2013 6:25 PM

hi geek,

I also have the same problem, but this time around mine is just a normal laptop running on x64 architecture.

Pls me fix this; i know yours worked.

Thanks...

You are the man! Thank you very much.

Thank you!!! It worked perfectly and I was under a lot of pressure with production support... :) 

Thanks, that solved the issue for me too!

This error usually occurs when there is a mismatch between the bits allocation of the system on which the application  is built and that of the server system it is hosted into.

If the base system is 32-bits and server is say, 64 bits....This error will erupt.

To resolve,

1.) Go to IIS on the server

2.) Check for the application pool on which the website is hosted.

3.) Right Click on that application pool and go to properties.

4.) Set "Enable32-bitsApplication" to true.

• Proposed as answer by Florin Gugui Wednesday, November 13, 2013 1:33 PM

This error usually occurs when there is a mismatch between the bits allocation of the system on which the application  is built and that of the server system it is hosted into.

If the base system is 32-bits and server is say, 64 bits....This error will erupt.

To resolve,

1.) Go to IIS on the server

2.) Check for the application pool on which the website is hosted.

3.) Right Click on that application pool and go to properties.

4.) Set "Enable32-bitsApplication" to true.

• Proposed as answer by Florin Gugui Wednesday, November 13, 2013 1:33 PM

This error usually occurs when there is a mismatch between the bits allocation of the system on which the application  is built and that of the server system it is hosted into.

If the base system is 32-bits and server is say, 64 bits....This error will erupt.

To resolve,

1.) Go to IIS on the server

2.) Check for the application pool on which the website is hosted.

3.) Right Click on that application pool and go to properties.

4.) Set "Enable32-bitsApplication" to true.

• Proposed as answer by Florin Gugui Wednesday, November 13, 2013 1:33 PM

This worked for me, many thanks save me a lot of time.



Thanks I have same issue realted to office.But now its working well..thanks again

Thanks, this resolved my issue, down loaded and installed the data connectivity components

Hi Friends,

I was getting the same error on local pc and on server, I did full R & D and finally I found that we need to install below setup which resolves the error.

http://www.microsoft.com/en-us/download/details.aspx?id=23734

ENJOY !!!

Thanks and Regards,
Rohit Rathod
anrorathod@gmail.com

You need to install the same bit version of OLE provider as your porject settings is: More detailed instruction here: http://druss.pp.ua/2014/06/fixed-the-microsoft-ace-oledb-12-0-provider-is-not-registered-on-the-local-machine/

Lovely Man its done...Great Search.

1. Go to Microsoft's Site and Download AccessDatabaseEngine.

Its currently about 24 MB in size.

Here is the link:

http://download.microsoft.com/download/f/d/8/fd8c20d8-e38a-48b6-8691-542403b91da1/AccessDatabaseEngine.exe

2. Install the Database Engine.

You need to restart your computer in order to have it to work.

3. Change the Target CPU item: From ANY (CPU) to x86 as shown in the picture below.

I have indicated that part with a red oval rectangle.

That is all you need to change and then save project.

social.technet.microsoft.com/Forums/getfile/5262004

4. Click on refresh on your data resources tab.

You will then see the database showing after refresh.

5. Click on the Green Play or Run Button and you are done...

I had the same problem and this worked for me! Thanks

Best Solutions for this case instal office 2007 on server

Thanks a lot. I had the same issue. On visual Studio ( local ) it was working fine but when I hosted the application on the same system It was showing me this error. When I followed these steps It started working fine. :)

If you know you've installed the access engine, try changing the web-app's application pool to "enable 32bit applications".