Dataset refreshing fails with specific table

[Alberto_sd]

Hi everyone,

I have heen trying to refresh a dataset from app.powerbi.com client and I get the following error message: 

Something went wrong

Cannot connect to the mashup data source. See error details for more information.

Please try again later or contact support. If you contact support, please provide these details.

Underlying error code: -2147467259 Table: XXXXXXX.

Underlying error message: Error in the evaluation.

DM_ErrorDetailNameCode_UnderlyingHResult: -2147467259

Cluster URI: WABI-EUROPE-NORTH-B-redirect.analysis.windows.net

Activity ID: 6adfd0a9-f934-403b-8666-ba824a8604ab

Request ID: 86c1c0fc-7a25-2447-09ab-2131cb3ea0b6

Time: 2018-12-06 10:53:54Z 

The dataset refresh works for even larger tables, so I dont know what could be happening with this one. I have already checked credentials and they work to refresh any other table of the MySQL database, so seems something related to this specific table. 

Thank you very much for the comments/suggestions, 

Alberto

[Anonymous]

Hi @Alberto_sd,

I check you request id but haven't found anything specific in trace log. It shows a common error measure about refresh task canceled.

Is there any changes apply on your source data?(e.g. add remove table fields, change fields type...)

Regards,

Xiaoxin Sheng

[Alberto_sd]

Hi @Anonymous,

I have just been trying again some other tests. Only importing that table (without any change on the source data like removing or adding columns) in a report allows the refresh to be completed successfully. Only the importing of the table makes the report to  be about 100MB.

However, in a still simple report with some relationships (2) but still no transformations on the data source (total size of report 800MB), the refresh fails and the same message is shown. 

So no, I am not applying any changes on my source data, but complexity of the report (really low) seems to be involved.

Thank you Xiaoxin,

Alberto

[Anonymous]

Hi @Alberto_sd,

I can't find anything particular from your description which may cause your issue.

In my opinion, it sounds like gateway processing transformed compress refresh data size limit issue but I can't reproduce this and find out similar issues.

In addition, can you please open a support ticket for this issue to get better support from power bi team?

submit a support ticket

Regards,

Xiaoxin Sheng