On this page

    Troubleshooting Connections to Dremio from Microsoft Power BI

    Power BI Service update (June 2022)

    Problem

    Microsoft Power BI Service (June 2022 - Client version: 2206.1.11664-train) now contains the ability to directly connect to Dremio Cloud without a gateway. See the following actions required to connect new or already published reports.

    Solution

    I have a report...To turn off a gateway
    Created using Power BI Desktop and published to Power BI Service1. In Power BI Service, open the Data hub tab. Click the vertical ellipsis next to the dataset and select Settings.

    2. Expand the Data source credentials section and click Edit credentials.

    3. Select an authentication method.

    4. Set the Privacy level setting for this data source.

    5. Click Sign in.

    Published using Power BI Desktop to Power BI Service and a gateway was used to display the report1. In Power BI Service, open the Data hub tab. Click the vertical ellipsis next to the dataset and select Settings.

    2. Expand the Gateway connection section and toggle On-premises or VNet data gateway off.

    3. Expand the Data source credentials section and click Edit credentials.

    4. Select an authentication method.

    5. Set the Privacy level setting for this data source.

    6. Click Sign in.

    If the connection is successful, the report will run.

    Mismatch of parameters between Power BI Desktop and Power BI Gateway

    Problem

    As new versions of the Dremio Power BI connectors are released, this will change some of the parameters you can enter. When this occurs, there could be errors reported in Power BI Service such as:

    (1110) Unable to determine the data source.

    (1110) Gateway or datasources not reachable.

    Typically this will occur if you have generated a report (pbix) with a newer connector and you tried to open it with an older connector.

    Solution

    It is important that both Power BI Desktop and Power BI Gateway use the same connector Dremio.mez file version. You can ensure this by installing Power BI Desktop and Power BI Gateway, which have the same installation date (example: September 2021).

    The Power BI connector is contained in a Dremio.mez file, which is not the same as the desktop and gateway versions.

    note:

    It is recommended to use the latest connector version as this offers the best backward compatibility.

    Power BI Desktop Installation

    The Power BI Desktop installation should not have the connector Dremio.mez file installed locally. Instead, it should use the Certified Connector that comes with Power BI Desktop.

    To ensure there is no local version on your Windows computer:

    1. Open a File Explorer and navigate to C:\Users\<your user>\Documents\Power BI Desktop\Custom Connectors.
    2. If this folder exists and the file Dremio.mez exists in that folder, then delete the file.
    3. If Power BI Desktop is open, then close it. When you reopen Desktop, it will find the correct Dremio connector.

    Power BI Gateway Installation

    The Power BI Gateway installation should not have the connector Dremio.mez file installed locally. Instead, it should use the Certified Connector that comes with Power BI Gateway.

    To ensure there is no local version on your Windows computer:

    1. Open Power BI Gateway and then select Connectors from the left menu.
    2. Use a File Explorer and navigate to C:\Users<your user>\Documents\Power BI Desktop\Custom Connectors.
    3. If this folder exists and the file Dremio.mez exists in that folder, then delete the file.
    4. Restart Power BI Gateway.

    Uncertified Connector message

    Problem

    When the Power BI Desktop is opened and the Dremio connector is selected in Get Data, the following pop-up message appears:

    This error occurs because there is a Power BI connector installed locally.

    note:

    We are moving away from having connectors installed locally. Instead, you should use the certified connectors that are available as part of the desktop or gateway installations.

    Solution

    Check to see if you have a Dremio.mez file in the C:\Users\{Your Username}\Documents\Power BI Desktop\Custom Connectors folder. If so, you should remove it.

    Power BI SSO AAD fails with error AADSTS650052

    Problem

    This problem applies to Dremio Cloud, because Single Sign On (SSO) authentication is already working for UI logins.

    After Configuring SSO to add the tenant info in the Dremio UI, you complete the following steps to connect to Power BI:

    1. Select the Dremio Cloud connector and click OK.
    2. Select Microsoft Account and click Sign in.
    3. On the pop-up message, specify my AAD user and password credentials, and click Sign In.
    4. (Optional) If there is another pop-up message stating Microsoft has enabled Security Defaults to keep your account secure, click Skip for now….

    Then in the Power BI login, you are receiving the following error:

    access_denied: AADSTS650052: The app needs access to a service (‘https://connectors.dremio.app/powerbi') that your has not subscribed to or enabled. Contact your IT Admin to review the configuration of your service subscriptions.

    Solution

    First, you need to confirm the correct tenant ID is being used in the Dremio UI. You can find your Azure Active Directory Tenant ID by signing into the Azure portal and navigating to Dremio > Overview > Basic information.

    After you have found your tenant ID, paste the following into a browser:

    https://login.microsoftonline.com/<tenant_ID>/v2.0/adminconsent?<client_id>&&scope=User.Read&redirect_uri=https://app.dremio.cloud/sso
    

    You will need to change the tenant ID to the one you obtained before hitting Enter in the browser. The value entered in the Dremio UI should also match this value.

    Next, sign in with your Dremio account. You will then be directed to a screen that asks an admin to sign in. It will look similar to this message:

    You will see an error at the end about not finding a redirect page, but this is okay. The command above it does not have this set to a valid value.

    Then try connecting with Power BI again. If you are asked to grant permission once again at the sign-in stage, accept the request. The connection should now proceed as normal.

    “Request sent” for AAD authentication

    Problem

    When you attempt to log in via AAD, you may get redirected to a page that instructs you to request access from an admin. When you provide a reason for the request and send the request, the admin of your organization never receives any such request.

    Solution

    This is caused by a misconfiguration during setup. Walk through PowerBI SSO AAD fails with error AADSTS650052 and Setting Up Azure AD and ensure that every step was followed. Ensure the tenant ID is of your tenant, the application is set up in that tenant, and the following permission is enabled, as shown below: