Cannot connect to the mashup data source

[Anonymous]

Hi all,

Really stuck!

I'm having problems refreshing a SQL server datasource from Power BI service. I can refresh the data in desktop, and can configure the datasource in the enterprise gateway, but I cannot refresh or schedule refresh in Power BI service.

I am getting the following error message:

Last refresh failed: Fri Oct 12 2018 20:08:20 GMT+0100 (British Summer Time)
Cannot connect to the mashup data source. See error details for more information.Hide details
Cluster URI: WABI-NORTH-EUROPE-redirect.analysis.windows.net
Activity ID: c2541578-23ce-46e4-a671-087c35989d8e
Request ID: edb7c772-3d3d-89cd-c651-f834a2d4cf04
Time: 2018-10-12 19:08:20Z

Has anyone else come across this? I am able to connect refresh from other SQL databases but just having a problem with this one.

Regards

Mike

[v-danhe-msft]

Hi @Anonymous,

Could you have assigned the data base when you are getting data from SQL server? I have found the same issue that you could have a view:

https://community.powerbi.com/t5/Service/Cannot-connect-to-the-mashup-data-source/td-p/346879

Regards,

Daniel He

[Anonymous]

Hi Daniel

The database is already assigned in desktop.

Regards

Mike

[Anonymous]

Still getting this error message. Can anyone help? Thanks

[TomMartens]

Hey,

without further knowledge, it will become quite difficult to provide some additional hints.

But as you have already stated, other on-premises SQL Server data sources can be refreshed from within the Power BI Service using the same on-premises data gateway machine.

So the question is what sets this database / SQL Server apart from the other data sources:

• can you ping the database machine form the gateway machine
• maybe the authentication mode for this data source is Kerberos whereas the gateway machine / the service account is not prepared for this

Have you had a first glimpse at the log files of the gateway.

Debugging this can become quite lengthy.

Regards,

Tom

[Anonymous]

Hi Tom,

Thanks. Will check pinging the machine and gateway logs.

The connection works in the service when using direct query, just not when the data is imported. Any idea why this would be?

Regards

Mike