Forum Discussion

rayudu's avatar
rayudu
Regular Visitor
9 years ago
Solved

there was a data source access error. please contact the gateway administrator

I have create ssas tabular model and created a few reports in power bi desktop after installing power bi enterprise gateway and published power bi desktop reports to power bi services. and i have create a new data source for tabular data model by using data source type as analysis services.I was succussully completed the things upto here.

But i tried to access the data source i facing the big problem .So,kindly provide the why im not able to access the data source.

 

Please find the attaced screen shoots for more information.

 

 

 

 

 

 

  • Anonymous's avatar
    Anonymous
    9 years ago

    Hi rayudu,

    Firstly ensure that your SSAS server and gateway are installed in a same domain or trusted domains.

    Secondly, in Power BI,  the effective username is passed to the gateway and then onto your on-premises Analysis Services server each time a user interacts a report connected to Analysis Services. The email address that you use to sign in Power BI with is passed to Analysis Services as the effective user. This email address should match a defined UPN within the local Active Directory Domain, if a match cannot be found, you will get errors.

    You can use the following command from your workstation to find out the UPN for your account, if the UPN doesn't match the email address you sign into Power BI with, you can use “Map user names” feature to solve this issue.  Assume that you if you sign into Power BI with [email protected], but your local directory UPN is [email protected], you can configure a mapping rule to have [email protected] passed to Analysis Services. For more details, please review this article.

    whoami /upn


    Thanks,
    Lydia Zhang

12 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi rayudu,

    Firstly ensure that your SSAS server and gateway are installed in a same domain or trusted domains.

    Secondly, in Power BI,  the effective username is passed to the gateway and then onto your on-premises Analysis Services server each time a user interacts a report connected to Analysis Services. The email address that you use to sign in Power BI with is passed to Analysis Services as the effective user. This email address should match a defined UPN within the local Active Directory Domain, if a match cannot be found, you will get errors.

    You can use the following command from your workstation to find out the UPN for your account, if the UPN doesn't match the email address you sign into Power BI with, you can use “Map user names” feature to solve this issue.  Assume that you if you sign into Power BI with [email protected], but your local directory UPN is [email protected], you can configure a mapping rule to have [email protected] passed to Analysis Services. For more details, please review this article.

    whoami /upn


    Thanks,
    Lydia Zhang

    • mdaamirkhan's avatar
      mdaamirkhan
      Icon for Post Prodigy rankPost Prodigy

      Its not related with domain fisrt read carefully what I wrote. If you dont know the answer then dont give other answer which is not related with this.

       

      If the data is huge in the cube then when you try to live connect to cube and click ok nothing will show in Field section I kept 24 hours like that but nothing came. Live connect works properly on samll amount of data in the cube.

      • jennyy's avatar
        jennyy
        Frequent Visitor

        After reviwed the gatewayXXX.log  and  found   following error message

        GatewayPipelineErrorCode=DM_GWPipeline_UnknownError
        ProviderName=MSOLAP.5 --->
        Inner exception chain: System.Runtime.InteropServices.COMException
        <pi>System.Runtime.InteropServices.COMException (0x80040154): Retrieving the COM class factory
         for component with CLSID {308FF259-8671-4DF4-B66C-9851BFACF446} failed due to the following error: 80040154
         Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)).

         

        I finally get the issue solved by unregister 32 bit msolap110.dll and 64 bit msolap130.dll using following command

        regsvr32 -u "C:\Program Files (x86)\Microsoft Analysis Services\AS OLEDB\110\msolap110.dll"

        regsvr32 -u "C:\Program Files\Microsoft Analysis Services\AS OLEDB\130\msolap130.dll"

        and then reregister 64 bit msolap130.dll using command

        Regsvr32 "C:\Program Files\Microsoft Analysis Services\AS OLEDB\130\msolap130.dll"

        wish it is helpfule

      • jennyy's avatar
        jennyy
        Frequent Visitor

        Please  export the error log  by running enterpriseGatewayConfigurator.exe   which locates under  C:\Program Files\On-premises data gateway  by default ,

        Then check gateway log to find the details first.

      • jennyy's avatar
        jennyy
        Frequent Visitor

        i encounterred same error after upgraded on-promises data gateway. i am using SQL 2016 standard edition. any update? Thanks

  • manito969's avatar
    manito969
    Frequent Visitor

    my upn ( what i got it with the cmd) is the equal my email to sign in in power bi but local domain in which it is the ssas(DOMAIN\username) is different than domain (username@domain), so i think that my error is generated for this, it is posible?

    • asanchez's avatar
      asanchez
      Frequent Visitor
      Hello.
       
      Someone has connected this use case with stand alone servers that do not have UPN. more specifically, the published reports with analysis service on stand alone servers that do not have UPN work as user DOMAIN / USER

      I'm going to try removing the DLLs and re-registering them but if someone can confirm that the architecture works, I would be grateful
       
  • What worked for me is in the Connection Settings > Map Usernames, add another rule that user@domain.com (usually owner account or account signed in) is mapped to DOMAIN\username (same account in the Authentication part above). Then restart the onpremise gateway. Ensure the service account running SSAS and Gateway has enough Role permissions on SSAS as well.