Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
8 years ago
Solved

PowerBI Server (October) DirectQuery to SQL Server table - bug

Hi   I have created a PowerBI Report on PowerBI Desktop (October) with a DirectQuery connection to a table on a SQL Server. The report works in PowerBI Desktop (October). When I save it to PowerBI ...
DirectQuery
Power BI Report Server
  • Jon-Heide's avatar
    Jon-Heide
    8 years ago

    Try storing your credentials (windows or sql) in the server after you publish. You can do this under the data sources tab. The report server now hosts Analysis Services under the covers and that AS server could not connect to your DQ data source. 

v-qiuyu-msft's avatar
v-qiuyu-msft
Icon for Community Support rankCommunity Support
8 years ago

Hi Anonymous,

 

Please go to Manage pane of the report, click Test Connection to verify the used credential is valid. 

 

 

Best Regards,
Qiuyun Yu

  • su2pbi's avatar
    su2pbi
    Frequent Visitor
    8 years ago

     

    Hi Qiuyun Yu, 

    I am received the similar error. 

     

    We couldn't run the report because we couldn't connect to its data source. The report or data source might not be configured correctly.
    Please try again later or contact support. If you contact support, please provide these details.

    We couldn't connect to the Analysis Services server. Make sure you've entered the connection string correctly.

    Request ID1d123dfe-bd75-68f9-cb8c-f20e2714b9fc

    TimeFri Jan 26 2018 22:02:00 GMT-0500 (Eastern Standard Time)

    Version14.0.600.434

     

     

    I had 

    1. Confirmed via SSMS user has correct access (role security was defined) in SSAS cube 
    2. Confirmed Kerberos is setup correctly by testing the same user same cube with Paginated Report and Excel Online
    3. Confirmed  via Manage pane of the report, clicked Test Connection with "as the user viewing the report" and received a green check mark. 

     

    Is this really a bug on Oct release? Or there is something else I need to look into more?

     

     

    • Arez2017's avatar
      Arez2017
      Icon for Advocate I rankAdvocate I
      8 years ago

      Hello 

       

      I am facing the same issue.

      Did you find a workrround please?

       

      Regads

      • Anonymous's avatar
        Anonymous
        Not applicable
        8 years ago

        Hi

         

        The workaround is to go to "Data Sources" of the report after you published it to server.And then manually enter the username and password.

        A permanant solution was to configure Kerberos for the server.

         

        Jaco

  • su2pbi's avatar
    su2pbi
    Frequent Visitor
    8 years ago

     

    Hi Qiuyun Yu, 

    I am received the similar error. 

     

    We couldn't run the report because we couldn't connect to its data source. The report or data source might not be configured correctly.
    Please try again later or contact support. If you contact support, please provide these details.

    We couldn't connect to the Analysis Services server. Make sure you've entered the connection string correctly.

    Request ID1d123dfe-bd75-68f9-cb8c-f20e2714b9fc

    TimeFri Jan 26 2018 22:02:00 GMT-0500 (Eastern Standard Time)

    Version14.0.600.434

     

     

    I had 

    1. Confirmed via SSMS user has correct access (role security was defined) in SSAS cube 
    2. Confirmed Kerberos is setup correctly by testing the same user same cube with Paginated Report and Excel Online
    3. Confirmed  via Manage pane of the report, clicked Test Connection with "as the user viewing the report" and received a green check mark. 

     

    Is this really a bug on Oct release? Or there is something else I need to look into more?