Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
8 years ago

Power Bi using Access 2013 32 bit Failed

Hi There

I am also getting the same error while refreshing my Power Bi using Access

It refresh fine while on Desktop but when I do refresh in Power Bi Service I got the following error.

Just to give you bit of back ground I am using 64 bit Power Bi desktop and using Access 32 bit But I am using 'Microsoft.ACE.OLEDB 64 bit

I hope this might help

Can you please advise.

Thanks

Syed

 

Last refresh failed: Wed Aug 01 2018 21:05:15 GMT+1200 (New Zealand Standard Time)
Cannot connect to the mashup data source. See error details for more information.Hide details
Underlying error code:-2147467259 Table: Date.
Underlying error message:Unspecified error
DM_ErrorDetailNameCode_UnderlyingHResult:-2147467259
Microsoft.Data.Mashup.ValueError.Reason:DataFormat.Error
Cluster URI:WABI-AUSTRALIA-SOUTHEAST-redirect.analysis.windows.net
Activity ID:3d095c94-fe44-432f-a756-1db89c8b4a22
Request ID:f92c78f1-3a00-f490-39ee-d84dc9790d7b
Time:

2018-08-01 09:05:15Z

 

 

Need Help

3 Replies

    • Anonymous's avatar
      Anonymous
      Not applicable
      8 years ago

      Hi Ross

      I don’t believe that this could be a solution as I could not be able to use the 32 bit Power Bi desktop due to m data size.

      I don’t believe that the gateway installed on 64 bit machine and 32 bit drivers of ACE OLEDB provider  will work well with that either.

      I need to understand what would be the cause of this issue and is there any work aorund or fix for that as the error is not really helpful.

      I look forward for your response.

      thanks

      Syed

       

      • Anonymous's avatar
        Anonymous
        Not applicable
        8 years ago

        The issue is in the Driver making the connection to Access 32.  From what we have seen, trying to use a 64bit Access driver doesn't work, so you need to find a way of having the 32 bit Access driver installed, so when the connection is made it runs through that Access driver.  If you have Office 32bit or Power BI Desktop 32-bit install, this simplifies the process as it puts that driver in for you.

         

        Access is awful to work with once you start to want to do Enterprise solutions, so any ability to migrate away will make your life easier.  For the moment, see if you can install a 32bit driver.

         

        I have had some luck in other connections by routing connections through an ODBC driver, however I've not had to try this with access.