January 8, 2018 at 11:11 am
We have a SSIS package that is going to run on a SQl Server 2014 instance.
I use Visual studio 2017 to open it on my work station which recently have office 365 installed.. Previously it has the traditional professional office installed. Now when I run in visual studio it does not work.
It fails with the error Microsoft.ACE.OLEDB.16.0 is not registered on the local machine. if the 32 bit drive is not installed, run the package in 64 bit mode.
I tried to change the project in visual studio to run in 64 bits mode or 32 bits mode, neither works.
Also I tried to download and install Microsoft Access Database engine 2016 redistributable 32 bits, it got an error : you cannot install the 32 bit version of Microsoft access database engine 2016 vecaue you currently have 64 bit office products installed.
What should I do now?
The requested OLE DB provider Microsoft.ace.oledb.16.0 is not registered.
Thanks
January 8, 2018 at 1:00 pm
The ACE OLEDB drivers are a part of the Microsoft Access Database Engine redistributable, You can find that here:
https://www.microsoft.com/en-us/download/details.aspx?id=54920
January 8, 2018 at 1:07 pm
Thanks, like I said in the post,
downloaded and installed Microsoft Access Database engine 2016 redistribute 32 bits, it got an error : you cannot install the 32 bit version of Microsoft access database engine 2016 because you currently have 64 bit office products installed.
I was able to fix this by install Microsoft Access Database engine 2010 redistribute 32 bits
January 8, 2018 at 1:34 pm
I suppose you could use the older version, but there are 32 and 64 bit drivers available at the website I posted a link to.
January 8, 2018 at 1:58 pm
sqlfriends - Monday, January 8, 2018 1:07 PMThanks, like I said in the post,
downloaded and installed Microsoft Access Database engine 2016 redistribute 32 bits, it got an error : you cannot install the 32 bit version of Microsoft access database engine 2016 because you currently have 64 bit office products installed.I was able to fix this by install Microsoft Access Database engine 2010 redistribute 32 bits
You could try installing the version using the /passive switch - that's how you need to install the 64 bit version if you have 32 bit Office. Just something like:
AccessDatabaseEngine.exe /passive
Sue
January 8, 2018 at 2:37 pm
Thank you two.
I am a little confused.
I checked our current version of office is Office 365 32 bits. I know this by opening excel, go to account, I see it says Ofifce 365 Proplus.
I click about Excel, I see it says 32 bits.
So when I ran the ssis, it failed and said Microsoft.ACE.OLEDB.16.0 is not registered on the local machine.
But when I tried to install Microsoft Access Database engine 2016 redistributable 32 bits,
it got an error : you cannot install the 32 bit version of Microsoft access database engine 2016 because you currently have 64 bit office products installed.
Why it says 64 bits office installed?
Thanks,
January 8, 2018 at 2:43 pm
sqlfriends - Monday, January 8, 2018 2:37 PMThank you two.I am a little confused.
I checked our current version of office is Office 365 32 bits. I know this by opening excel, go to account, I see it says Ofifce 365 Proplus.
I click about Excel, I see it says 32 bits.So when I ran the ssis, it failed and said Microsoft.ACE.OLEDB.16.0 is not registered on the local machine.
But when I tried to install Microsoft Access Database engine 2016 redistributable 32 bits,
it got an error : you cannot install the 32 bit version of Microsoft access database engine 2016 because you currently have 64 bit office products installed.
Why it says 64 bits office installed?Thanks,
Maybe from the other Office you had installed before Office 365? Do you remember what bit that one was?
Look in Control Panel -> Programs and Features. Maybe there is something in there you can see that wasn't uninstalled.
Sue
January 8, 2018 at 3:25 pm
I cannot find that in installed programs.
The office we installed is Office 365 Proplus. Click to run.
Any way searched online it seems microsoft does not allow install both 32 bits and 64 bits for 2016 on the same workstation.
Only option for now is to install earlier version of 32 bits.
That worked.
https://www.codeproject.com/Questions/1173202/The-microsoft-ace-oledb-provider-is-not-registered
January 8, 2018 at 3:31 pm
January 8, 2018 at 3:47 pm
sqlfriends - Monday, January 8, 2018 3:25 PMI cannot find that in installed programs.
The office we installed is Office 365 Proplus. Click to run.Any way searched online it seems microsoft does not allow install both 32 bits and 64 bits for 2016 on the same workstation.
Only option for now is to install earlier version of 32 bits.
That worked.https://www.codeproject.com/Questions/1173202/The-microsoft-ace-oledb-provider-is-not-registered
Thanks for that link.
I'd take that with a grain of salt for now though. I was looking further and others who had no changes with Office had the 16.0 driver stop working. There are a few things saying something about some Windows Update breaking things...which I wouldn't doubt as it seems to happen every two or three months. Some support person on one of the MSDN forums reproduced another persons issue and said it was more likely OS. But nothing posted after that. You may want to just search on it ever month or so, eventually whatever the issue is will get posted.
Sue
September 27, 2019 at 11:09 am
ERROR: The 'Microsoft.ACE.OLEDB.16.0' provider is not registered on the local machine
Thoughts on how to configure our Windows 10 laptop running SSMS 2017 v18.3 on SQL 2017 Developer Edition to allow for a large XLS import (sheet has > 65k rows in it) --- into a SQL 2017 table?
On our Windows 10 laptop, User requires newer version of 'Microsoft.ACE.OLEDB.16.0' provider as they're importing > 65k rows. We tried uninstalling the 64-bit ACE.OLEDB driver and installing the 32-bit -- to no avail. The older versions of EXCEL (2007-2010, etc) will run during the import setup BUT they do NOT accommodate > 65k rows.
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply