Forum Discussion

pnussbaumer's avatar
pnussbaumer
Frequent Visitor
10 years ago

Enterprise Gateway - greyed out, why?

Hey there... I configured a Enterprise Gateway on my on-premises SharePoint-Server. Check. I configured this Enterprise Gateway in my Power BI Service on app.powerbi.com. Check. I added my Share...
Need Help
TealCanady's avatar
TealCanady
Icon for Advocate II rankAdvocate II
10 years ago

If you have different credentials in your on premise data sourc; the users online technically can't access the data because you can't add their credentials in. A common occurence of this is using mydomain.local in active directory. You may need to establish a UPN for these users in Activie directory using their online accounts. 

https://powerbi.microsoft.com/en-us/documentation/powerbi-admin-power-bi-security/

 

 

Hope this helps!

 

Teal Canady

Sr. Data Architect 

ajone107's avatar
ajone107
New Member
10 years ago

Hello, 

 

I have this same error. I am confused by your response. Are you saying that individuals on a .local domain need to add a UPN to allow the Enterprise/Personal data gateways to work? What would the UPN look like to work with MSFT cloud services?

 

Please advise as this has been a major headache for me. I have had to use a 3rd party tool called PowerUpdate to get my refresh to work.

 

Thanks,

Adam

  • TealCanady's avatar
    TealCanady
    Icon for Advocate II rankAdvocate II
    10 years ago

    Adam,

     

    Can you connect through the desktop edition of power bi to the sharepoint list? If so then I may be way off base and all you would have to do is push the local power bi desktop file to the cloud; provided they are the same data source then it will use the enterprise gateway for the future. If not then an explination of UPN is below.


    So to connect to your on premise data source lets go through the scenario. You have installed the Power BI Enterprise Gateway on a server and everything connects to Sharepint etc. You have a user online that has access, [email protected].

     

    In the app.powerbi.com you login with [email protected]

    Locally you log in to sharepoint with [email protected]

     

    Power BI can't make the connection to sharepoint because there are no permissions for [email protected] present. When Power BI connects to the enterprise gateway it calls on your Active Directory Server to get an effective username; so it tries to look up [email protected] and it does not exist. 

    A UPN on user [email protected] that reads as [email protected] allows the security to translate those two different users. A UPN makes it so that when you login and try to query with [email protected] it uses the security from [email protected] as the effective username.

    I'm sorry to say I don't have sharepoint to test this out for you; i'm basing this on my experience with on premise tabular models. 

     

     

    Teal Canady

    • allankz's avatar
      allankz
      New Member
      8 years ago

      Hi,

       

      I had this problem and (after at least one hour almost loosing my mind) found the problem.

       

      Check ALL sources on your PBIX file to see if your gateway works with all of them.

       

      For example: I needed to read the folder "c:\test\reporting" on the server (and this folder also exist on my desktop computer). However, when I was testing I used to use "c:\Users\myname\Desktop\test\reporting"... and there was ONE source pointing to this folder that only exists on my desktop computer. So, I think that the gateway thought "I can locate the first folder, but cant locate this second one, so I cannot provide data source for this pbix".

       

      After I removed this wrong path from the data source that was using it, the gateway has been enabled on power bi data sources.