Power BI gateway issue with live SSAS Tabular connection

[Joshua_]

Hi guys,
Created a tabular model in SSAS and I can connect without problems from my power bi desktop.
Once published in power bi service, I have created my Analsys Services type gateway, but when I see the report it does not show data and an error:
"This report could not be accessed to the data source. Please contact the author so they can correct it."

I have read that it can be associated with a property of the active directory account (UPN), but I always use this account to publish other power bi reports and it works without problems.

I tried to open the tabular model from Excel and I can consume it without problems, which means that that part is fine and the problem is more associated with the gateway.

I also tried changing the tabular model compatibility in visual studio, but I haven't had good results.

What else can I do? Or what logs can I enable to have more information?

[Martin_D · Accepted solution]

Hi @Joshua_ ,

Your description matches with wrong or missing Power BI UPN (the one that you use to publish the report) to local AD UPN (the one that you use to access SSAS, e.g. from Power BI Desktop or Excel desktop app) being a potential cause. When you open the report in your web-browser, then Power BI Service sends your Power BI login name to the gateway and the getway to SSAS. In many setups, a local Active Directory manages usernames for login to your computer and services like SSAS on prem that differ from the Power BI login. If this is the case, then you either need to maintain manually in Power BI the username mapping (in the settings of the gateway SSAS data source in the web-browser, see https://learn.microsoft.com/en-us/power-bi/connect-data/service-gateway-enterprise-manage-ssas#manua... ) or you need to configure the gateway to read the mapping from the Active Directory. This article explains the steps: https://blog.jpries.com/2019/10/14/power-bi-gateway-when-your-powerbi-com-login-doesnt-match-your-ac...

If you are using impersonation for SSAS access, and the above doesn't completely solve your problem, you might also need to allow the user running the Power BI Gateway Service to impersonate users at the SSAS (The gateway connects to SSAS with the identity running the gateway service, then the gateway service tells SSAS to use the identity from Power BI. This work only if SSAS accepts such requests from the user running the gateway service.)

Another user solved the issue by setting up a SQL users for access from Power BI: https://blog.jpries.com/2019/10/14/power-bi-gateway-when-your-powerbi-com-login-doesnt-match-your-ac...

Another user suggested to upgrade to SQL Server 2017 and add the Power BI login as an external user (not sure whether this is a verified solution): https://community.fabric.microsoft.com/t5/Service/Connection-to-SSAS-through-Gateway-using-local-use...

So, first step I would suggest, you check with your SSAS developer or administrator what is the actual user that SSAS is seeing when you connect from Power BI Desktop successfully, then map your Power BI user to this user in the gateway settings in the web-browser. If this doen't solve the issue yet, make sure the user running the gateway service is allowed to impersonate users at your SSAS.

BR

Martin

[Joshua_]

hello everyone,
I do not have access to the active directory configuration, I must generate a ticket to be able to review this configuration and it is very slow.

Thank you very much for your help.

[v-weiyan1-msft · Accepted solution]

Hi @Joshua_ ,

It has been 2 weeks since your problem occurred, has it been resolved so far? Are you troubleshooting the problem based on the solution ideas provided by @Martin_D ? If the issue is not resolved at this time, can you provide more information for our reference? This will better help you deal with the issue.
Looking forward to your reply.

Best Regards,
Yulia Yan

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[Martin_D · Accepted solution]

Hi @Joshua_ ,

Your description matches with wrong or missing Power BI UPN (the one that you use to publish the report) to local AD UPN (the one that you use to access SSAS, e.g. from Power BI Desktop or Excel desktop app) being a potential cause. When you open the report in your web-browser, then Power BI Service sends your Power BI login name to the gateway and the getway to SSAS. In many setups, a local Active Directory manages usernames for login to your computer and services like SSAS on prem that differ from the Power BI login. If this is the case, then you either need to maintain manually in Power BI the username mapping (in the settings of the gateway SSAS data source in the web-browser, see https://learn.microsoft.com/en-us/power-bi/connect-data/service-gateway-enterprise-manage-ssas#manua... ) or you need to configure the gateway to read the mapping from the Active Directory. This article explains the steps: https://blog.jpries.com/2019/10/14/power-bi-gateway-when-your-powerbi-com-login-doesnt-match-your-ac...

If you are using impersonation for SSAS access, and the above doesn't completely solve your problem, you might also need to allow the user running the Power BI Gateway Service to impersonate users at the SSAS (The gateway connects to SSAS with the identity running the gateway service, then the gateway service tells SSAS to use the identity from Power BI. This work only if SSAS accepts such requests from the user running the gateway service.)

Another user solved the issue by setting up a SQL users for access from Power BI: https://blog.jpries.com/2019/10/14/power-bi-gateway-when-your-powerbi-com-login-doesnt-match-your-ac...

Another user suggested to upgrade to SQL Server 2017 and add the Power BI login as an external user (not sure whether this is a verified solution): https://community.fabric.microsoft.com/t5/Service/Connection-to-SSAS-through-Gateway-using-local-use...

So, first step I would suggest, you check with your SSAS developer or administrator what is the actual user that SSAS is seeing when you connect from Power BI Desktop successfully, then map your Power BI user to this user in the gateway settings in the web-browser. If this doen't solve the issue yet, make sure the user running the gateway service is allowed to impersonate users at your SSAS.

BR

Martin

[Amrselim8889]

Hello Mr.  @Martin_D 

kinldy note i need you help here,

i beleive i have the same situation here, which is 

1. i have power bi service.

2. i have on prime analaysis services.

3. i have gateway.

i open the power bi desktop with Genena\amr.selim and log on the Analsysis server , which is fine, after i finish i publish to the service and then create the gate way use my username and password ((Genena\amr.selim , password)) the gateway is online and test connection is succsedded, i know that i must map users UPN then i mapped the my user on power bi service to my user on analsysis on premises so ("bi_powerbi" with be "Genena\amr.selim") but still not working and even i added the gatway user to the analysis service properties security as a user adminstrator "NT SERVICE\PBIEgwService"  but still not working, any help please....

i read something about make sure the user running the gateway service is allowed to impersonate users at your SSAS.

how is this done, i already used map user name effectiveusername and then mapping but still not working