Getting error : Failed to test the connection to your data source. Please retry your credentials

[saurabhtd]

Hello everyone, 

I need one help. 

I am unable to start the refresh of semantic model in Power BI Service as my creditionals are not getting validated. I getting this error "Failed to update data source credentials: " and "Failed to test the connection to your data source. Please retry your credentials". I have admin access in both Power BI and Databricks workspace. Power BI semantic model is consuming data from Databricks. 

Can you please help me in resolving this issue ? Any solutions to this solve this ? 

[v-jialongy-msft · Accepted solution]

Hi @saurabhtd 

Follow the steps below to solve your problem

Step 1: Verify Databricks Token

First, ensure that the Databricks access token you are using is still valid. Databricks tokens have an expiration date, and if yours has expired, you will need to generate a new one. Follow the steps in the Databricks documentation to create a new token  and update the connection in Power BI with this new token.Authentication for Databricks automation - overview | Databricks on AWS

Step 2: Validate Gateway Configuration

If you are connecting to Databricks using an on-premises data gateway, make sure that the gateway is online and properly configured. Verify that the Databricks data source is correctly set up in the gateway and that the credentials stored there are up-to-date. For more information on configuring gateways, refer to the Tutorial: Connect to on-premises data in SQL Server - Power BI | Microsoft Learn

Step 3: Test Connection in Power BI Desktop

Try to establish the connection to Databricks from Power BI Desktop first. If you can successfully connect and access data from Power BI Desktop, republish the PBIX file to the Power BI Service. This ensures that any connection or credential changes are updated in the service.

Best Regards,

Jayleny

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[saurabhtd]

Thanks a lot @v-jialongy-msft. These steps helped me in resolving the issue. Now I am not getting this error and I am able to start the refresh.