Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
7 years ago
Solved

Issue in Publishing Power BI Report Server with Local AD

 

Hi PowerBI Experts,

 

Scenario

 

  • Local AD is set is contoso.com for testing purposes with server domain controller with the named as DC server.

  • Setting up a Power BI Reporting Server testing environment with SQL Server 2016 Enterprise Trail with server name as SPSQL

  • Installed and Configured SQL Server Analysis Services (SSAS) Wide World Importer samples from GitHub.
  • Had set up SQL Server 2016 WWI-SSADMD as shown: 






    • Installed and Configured latest version of Power BI Enterprise data gateway on SQL Server 2016 box itself.

    • Clicked open the Power BI Desktop (Aug 2018) version for Power BI reporting server.

    • In Power BI desktop, Get Data >> SQL Server Analysis Server database. 



    • Connect to SQL Server 2016 with SSAS database




    • Drag and drop City in map Visuals. 



    • File >> Publish to Power BI service with my Office 365 login credentials as [email protected]   



    • Selected the Workspace. 





    • As I have configured enterprise gateway earlier, the publishing was successful.

Challenge   

 

  • In the Power BI URL https://app.powerbi.com I get this error.

  • Under Managed Gateway, the Gateway Clusters shows that it's Online




  • Data Sources is also successful with my Local AD accounts. 



  • I mapped the uses as per Power BI documentation 


 

As I am doing Power BI Reporting Server for the first, can you please advice how can resolve my issue? 
Any help would be highly appreciated.  

v-qiuyu-msft SivaMani v-yulgu-msft Anonymous

  • Anonymous's avatar
    Anonymous
    7 years ago

    Hi All, 

     

    I have resolved the issue. 
    Instead of my local AD accounts, I had to use the SQL Server User Account

    • Data Sources is also successful with my Local AD accounts.  (SQL Account)


1 Reply

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi All, 

     

    I have resolved the issue. 
    Instead of my local AD accounts, I had to use the SQL Server User Account

    • Data Sources is also successful with my Local AD accounts.  (SQL Account)