Forum Discussion

nwrong's avatar
nwrong
Icon for Helper I rankHelper I
9 years ago

Dataset Refresh error Microsoft.ACE.OLEDB.12.0 provider is not registered on the local machine

I published a report/dataset from PBI desktop to PBI Service. The datamodel is made up of a mix of access db, xlsx, and direct import from sql server db. I used the instructions from the link below to get get it working in desktop:

 

https://powerbi.microsoft.com/en-us/documentation/powerbi-desktop-access-database-errors/

 

Unfortunately with the report published to PBI service, and personal gateway running, I get this error:

 

Can't connect to the data source.Hide details

Data source type: 
Data source error:Microsoft Access: The 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine. The 64-bit version of the Access Database Engine 2010 Access Database Engine OLEDB provider is required to connect to read this type of file. To download the client software, visit the following site: https://go.microsoft.com/fwlink/?LinkID=285987.
Cluster URI:WABI-WEST-US-redirect.analysis.windows.net
Activity ID:4303771a-b2c4-4ad5-829f-a0b7c7048603
Request ID:bf24aa16-e9d3-f546-0246-dbf684055cd7
Time:2016-12-07 22:10:53Z

 

 

 

Any one else run into this error? or know a workaround? 

 

 

 

 

5 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable

    You are running powerbi version different than your access. Both program must have the same version (32bits or 64bits).

     

    Just download the right version to fix it.

    • nwrong's avatar
      nwrong
      Icon for Helper I rankHelper I

      I am running 32 bit pbi desktop and 32 bit MS access. That already works fine.

       

      The problem is when the report is published to app.powerbi.com, i'm using the Personal Gateway, and the refresh is failing with the error in my original post.

      • v-qiuyu-msft's avatar
        v-qiuyu-msft
        Icon for Community Support rankCommunity Support

        Hi nwrong,

         

        I can reproduce the issue on my side. And already reportit internally. Will update here once get any feedback.

         

        Best Regards,
        Qiuyun Yu