Forum Discussion
Refresh Error - 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine.
Hi Tmk123
Since you've updated Power BI to a 64-bit version, ensure that you also have the 64-bit version of the Microsoft Access Database Engine installed. You can download it from the link provided in the error message.
Hopefully this will resolve the issue. If not, try to install both 32-bit and 64-bit ACE Providers (as sometimes there are some apps / software requiring 32-bit and others 64-bit).
Hope this helps!
Theo 🙂
- Tmk1232 years ago
Helper II
Hi Theo, thanks for your response.
I had to wait until my IT dept could work with me to install those files. Unfortunately, that did not work. I already had the 64-bit version of the file installed and then followed Step 4 in the following link: https://learn.microsoft.com/en-us/power-bi/connect-data/desktop-access-database-errors. I now have both 32-bit and 64-bit installed on my PC and still receive the following error when I try to refresh the data from my workspace. I can't be the only person that has to deal with data sources in an XLS format. Do you have any additional thoughts? I am stumped.
Data source error: [ValidateMarkupTags][ccon]DataSource.NotFound: Excel Workbook: [ccon]The 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine. The 64-bit version of the Access Database Engine OLEDB provider may be required to read this type of file. To download the client software, visit the following site: https://go.microsoft.com/fwlink/?LinkID=285987.[/ccon]. [/ccon]. The exception was raised by the IDbCommand interface. Table: MarlinnDailyOpenPO.
Cluster URI: WABI-US-NORTH-CENTRAL-H-PRIMARY-redirect.analysis.windows.net
Activity ID: 8b147179-3067-4789-a2b2-c4c2133e30d9
Request ID: f9996d1b-360a-78d8-e376-d72e53944561
Time: 2023-11-28 14:38:19Z- tf21 year agoNew Member
old post but did you ever get this figured out?
- Tmk1231 year ago
Helper II
Unfortunatly, no. I think Microsoft stopped supporting legacy file formats and left it at that. There could be new workarounds developed by others within this community or "for pay" services that can bridge the gap but I have stopped looking. Sorry. I wish you luck and hope you find your solution.