Enterprise Gateway - Cannot connect to the mashup data source

[jeffhadley]

I have a data set that utilizes the Snowflake connector, as well as a connector to a file list in SharePoint.  In the past few weeks, I've begun receiving the following error when attempting to refresh the dataset in the Power BI service:

I am able to successfully refresh all queries from PBI Desktop, it just is an issue once I've published the dataset to the PBI Service.  My IT friends have upgraded the Gateway to the most recent version (earlier this week), but that hasn't solved the issue.  I have many other datasets that utilize Snowflake, SQL, and SharePoint and they are all experiencing the same issue.  In each, the table identified in the error message is a Snowflake-sourced table.

Any assistance anyone can provide would be greatly appreciated.

-Jeff

[jeffhadley · Accepted solution]

I figured out the issue. While PBI Desktop can navigate Snowflake's different schemas correctly, apparently the PBI Gateway cannot. Once I changed the data sources to all be from the same schema, the gateway was able to refresh without issue. I'm not sure why we utilized different schemas in the first place, but I'll keep this in mind down the road.

[Anonymous]

What did you do to "changed the data sources to all be from the same schema"?

Can you give little detail how you did that.  Do you mean that you consolidated data coming from different sources to once single source?  SQL database, excel spreadsheet, etc in to one?

[jeffhadley]

Hi Brian,

In snowflake, views are setup in different 'schemas'.  So we have some views setup in a PBI schema and others that house similar information setup as ETL schemas (there's also a PSA schema).  I'm VERY new to using Snowflake and probably haven't done as much homework as I should to understand it all.  One of my reports utilized a data source that was a PBI view (employee attributes) and another source was using an ETL view (location attributes).  Since I also had a PBI view that provided the location attributes I needed, I changed my data source to pull from the PBI view instead of the ETL view, which solved my mashup issue.

[Anonymous]

Thaks for posting the details.  What I do to getaround mashup data is:

When you bring in the tables from different data sources, I make a reference table of each original table. Then I run queries against the reference table and leave the original alone.  This work for me.

[v-frfei-msft]

Hi @jeffhadley,

Please delete the dataset in Power BI service and publish the report, after that, try to refresh the dataset in power BI service again.

Reagrds,

Frank

[jeffhadley]

Hi @v-frfei-msft

I deleted the dataset and then republished it.  I still get the same mashup error when I attempt to refresh the dataset.

[Anonymous]

I have the same issue. Ther report refresh without any probmles on my desktop, however, one I pulish it to the PBI service the detaset will not refresh.

Unable to refresh dataset :  my report is not refreshing. My dataset uses data gateway, data source credential has admin access, Gateway is ON and schedule refresh is also on. I am still working on this issue to find a solution, and in the mean time I would really appreciate  of my usergroup input, suggestions, workaround etc.


here is the error msg:
Last refresh failed: Fri Nov 30 2018 10:16:15 GMT-0800 (Pacific Standard Time)
Cannot connect to the mashup data source. See error details for more information.Hide details
Underlying error code: -2147467259 Table: Invoice Totals by Cust and Product.
Underlying error message: MySQL: Fatal error encountered during data read.
DM_ErrorDetailNameCode_UnderlyingHResult: -2147467259
Microsoft.Data.Mashup.ValueError.DataSourceKind: MySql
Microsoft.Data.Mashup.ValueError.DataSourcePath: 00.00.00.000;xxyyss
Microsoft.Data.Mashup.ValueError.ErrorCode: -2147467259
Microsoft.Data.Mashup.ValueError.Message: Fatal error encountered during data read.
Microsoft.Data.Mashup.ValueError.Reason: DataSource.Error