error in access to online dashboards

[dmiguel365]

Hello.
I have a MySql database in Mysql Workbench.
First i created a cube in Visual Studio 2015 and i used the mysql database.
After I created the cube, I published.
Now i create a dashboard in live connection on Power BI Desktop and published the dashboard.
When i acessed the online dashboard i receveid an error "This datasource can't be accessed by a data gateway". In details: "Couldn't load the schema for the database model"

The gateway is correctly intalled with no error in management gateway.

Someone can help me?

I am sorry for my english.

[v-qiuyu-msft]

Hi @dmiguel365,

In your scenario, did the data gateway installed on the same server as SSAS cube existed? When you create a data source under data gateway, make sure the server name and database name match the data source used in report. Also I would suggest you change the server name from "localhost" to "<real server name>". When you run the report, please use SQL Profiler to trace connection.

In addition, when we run the report which connects to SSAS, the email address signed in the Power BI Service is considered as effective user, it will be passed to the gateway and onto SSAS server. If the email address doesn't match defined UPN within the local Active Directory Domain, the login will be failed. So I would suggest you check if there is a match between Power BI Service signed in email address and your local directory UPN. For more information, please refer to this article: Usernames with Analysis Services.

And I saw the same issue fixed by restarting SSAS server and server before. You can also do it to see if issue persists.

If you have any question, please feel free to ask.

Best Regards,
Qiuyun Yu

[Seth_C_Bauer]

@dmiguel365 Depending on what user account you used to set up the enterprise gateway, check to make sure that your user is in the "Users" tab of the data source (you can reference your screenshot)

This page also outlines a bunch of troubleshooting steps, along with the location of the log files. Check those to determine if you can get a more specific error.