Forum Discussion
Memorable MemberDataset Refresh error Microsoft.ACE.OLEDB.12.0 provider is not registered on the local machine
Impactful Individualmike_honey, yes I see. I got the information from PG team that “refreshing against a .xls file is not supported”. So it will not work when users are trying to use the web datasource with .xls excel. I'm checking with the workaround, will post back when I got the information. Sorry for the inconvenience it brings you.
Memorable MemberThanks for the update Vicky, but that seems quite ridiculous. A Microsoft-hosted web service doesnt support using a Microsoft driver to access a Microsoft file type? We can access 50 different web services (most of which I've never heard of, but they do sound cool), but not an Excel file?
- Vicky_Song
mike_honey, as this article described: "Power BI supports importing or connecting to workbooks created in Excel 2007 and later. Workbooks must be saved as .xlsx or .xlsm file type and be under 250 MB". Currently, you need to change files from type .xls to .xlsx in order to fix this issue.
I understand the issue you're facing and will report back to PG team about your concerns.
- mike_honey
I dont have any solution for this continuing annoyance. The post in the Ideas forum for this issue only has 13 votes, which is a lot less than the comments on this thread. Can all please vote early and vote often:
https://ideas.powerbi.com/forums/265200-power-bi-ideas/suggestions/15081357-web-xls
FWIW, my workaround is to use Power Update, a 3rd party scheduling product:
dcrespAdvocate IV
Vicky_Song is there any update on this one. As mike_honey says it seems a liitle rediculus that you can not refresh xls files and should not be that hard to fix.
Hello!
As far as I understand, no fix was put in place to allow .xls extension to be used as a source for Power BI online.
Did anyone find a solution for this issue? Is there any ideias on how to automate de file convertion for .xlsx or .csv fo instance?
Best regards.
Raphael Leis
- dcresp
@Vicky_Song are you able to provide any update on this. It is an ongoing known bug. Thank you.