Forum Discussion

teconsultant's avatar
teconsultant
Regular Visitor
6 years ago

Unable to perform Direct Query against SQL Server

We recently upgrade to PBIRS and are excited to take advantage of leveraging PBI on-premise.  

We have created some basic PBIX files that are configured as Direct Query.  They work fine in PBI desktop, however, we get the following error when trying to run the PowerBI report after it has been uploaded.

 

2 Replies

  • bradsy's avatar
    bradsy
    Microsoft Employee

    Error? Did you manage for proper credentials?

    • teconsultant's avatar
      teconsultant
      Regular Visitor

      Some updates, and then I will show the error...


      Following the steps in this article (we are using SQL server instead of Analysis Services)
      https://docs.microsoft.com/en-us/power-bi/report-server/configure-kerberos-powerbi-reports

       

      1. Authentication type within Report Server config.
      2. SPNs for the report server service account.  (this isn't needed since we are using Virtual Service Account in PBIRS)
      3. SPNs for the Analysis Services service. (SQL Server)
      4. SPNs for the SQL Browser service on the Analysis Services machine. This is for named instances only.
      5. Delegation settings on the report server service account.

        The interesting thing is, now I am able to pull up test PBI reports, and I am getting mixed results.
        as a power user (same user who was able to create reports) I can view them from any machine except for on the local report server.

        I have 1 test PBI report with DQ that can be viewed from almost any user.  However, if i create another similar simple report, we get the same generic error.  Is there any way of getting PBIRS to provide a more detailed message?

        An unexpected error occurred
        An unexpected error occurred. Please try again later.
        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 IDe61dd989-ba98-8c66-78dd-b743444bff06
        TimeWed Dec 18 2019 14:37:16 GMT-0500 (Eastern Standard Time)
        Version15.0.1102.371