Refresh fails with error - Cannot connect to the mashup data source.

[Anonymous]

Hey All,
Getting the following error when (auto) refresh is triggered:

Last refresh failed: Wed Jan 09 2019 06:15:24 GMT+1100 (AUS Eastern Daylight Time)
Cannot connect to the mashup data source. See error details for more information.Hide details

Underlying error code: -2147467259 Table: DB bla_bla.
Underlying error message: Data on the server had an unexpected format. It might be possible to fix this by setting the 'OldGuids' option to true.
DM_ErrorDetailNameCode_UnderlyingHResult: -2147467259
Microsoft.Data.Mashup.ValueError.Reason: DataFormat.Error
Cluster URI: WABI-AUSTRALIA-SOUTHEAST-redirect.analysis.windows.net
Activity ID: a22f803c-1acb-4912-8fc4-d9c2ca083d92
Request ID: 394a2ced-e806-4317-8a75-e6eaeaa1ed80
Time: 2019-01-08 19:15:24Z

The suggested solution is already in place. "It might be possible to fix this by setting the 'OldGuids' option to true."
This is my query string:
= MySQL.Database("localhost:####", "DB", [ReturnSingleDatabase=true, OldGuids=true])

Any idea of the root cause and how to fix this?
Thanks!
A

[v-frfei-msft · Accepted solution]

Hi @Anonymous,

Please refer the stpeps of this bolg.

https://paultebraak.wordpress.com/2015/12/08/mysql-import-issues-with-power-bi-and-oldguids/

Regards,

Frank

[Anonymous · Accepted solution]

Hey,

Wanted to update and summarize the issue.

Issue - In general there are issues with connections to MySQL DBs from Power BI. The symptom in my case was that data refresh did not work and failed with the error message in my first/original post.

Solution - Creat a connection string to MySQL DB with the query in it. For example: 

= MySQL.Database("localhost:3306", "DB_Name", [ReturnSingleDatabase=true, OldGuids=true, Query="select * from MyTable where MyCondition"])

There is no need to delete or re-create the original connection string. Just to update it.

Thank you @GilbertQ and @v-frfei-msft for your assistance.

Cheers!

[GilbertQ]

Thanks for letting us know, will certainly assist others if they run into this issue.

[v-frfei-msft · Accepted solution]

Hi @Anonymous,

Please refer the stpeps of this bolg.

https://paultebraak.wordpress.com/2015/12/08/mysql-import-issues-with-power-bi-and-oldguids/

Regards,

Frank

[Anonymous]

Hi @v-frfei-msft,

I am not sure how this is related. As I can see the imported data.

Anyhow, Can I modify the existing connection? And just enter the SQL statement?
I don't want to re-build the report(s) after creating the new datasource.
Renaming the DS does not matter, the report still points at the original one.
Cheers!

[GilbertQ]

Yes, what you could do is to connect again in the same model with the SQL Statement.

Then copy all the code from your new table into your existing table.

[GilbertQ]

Hi there Does this work if you refresh via the Power BI Desktop? If it does, I would then suggest updating the Power BI On-Premise data gateway to the latest version to ensure that the mashup engine versions are the same.

[Anonymous]

Hey @GilbertQ
What do you mean refresh via the Power BI Desktop?
The gateway was installed this week, believe it is the latest one there is.

Anyhow, when I tried to update it, I got this error message below.

Reading previous posts, seems like it is a bug?!
What should be done? I dont want to lose my configurations.
The version installed is 3000.0.265 (December 2018), is that the latest (and greatest?)

Thanks!

[GilbertQ]

Hi there What I meant was if you manually refresh it via the Power BI Desktop file does it refresh. It does appear as if you have got the latest version of Power BI On-Premise Data Gateway. Can you confirm that the settings and testing the network connectivity works?

[Anonymous]

Hi @GilbertQ

Yes, connectivity is good.

Moreover, I have other datasources on the same server and they work fine. For example a MS SQL DB.

Seems like it is related to MySQL DB only and not other data sources.

Cheers!