Not able to refresh Semantic model which is using AWS redshift DB.

[TusharGaurav]

Hi Experts,

I am using AWS redshift DB on cloud and I can connect to the database from the power bi desktop.

When I publish the report to power bi service and try to refresh the underlying semantic model, I am getting below error:

-------------------------------

Failed to update data source credentials: ODBC: ERROR [08S01] [Microsoft][Amazon Redshift] (10) Error occurred while trying to connect: [SQLState 08S01] timeout expired

-------------------------------

Can you please suggest whats needed to be done I can connect to AWS redshift DB from Power BI Desktop but not from Power Bi Service?

Thanks and Regards,

Tushar Gaurav

[Poojara_D12 · Accepted solution]

Hi @TusharGaurav 

The issue you're encountering—where Power BI Desktop can connect to your AWS Redshift database but Power BI Service cannot—is due to network accessibility differences between the two environments. Power BI Desktop operates from your local machine, which has direct access to the Redshift database, whereas Power BI Service runs in Microsoft's cloud infrastructure and cannot access your private Redshift instance unless it is publicly reachable or a secure bridge is established. The most reliable and secure solution is to use an on-premises data gateway installed on a machine within your network or cloud environment that can access Redshift. This gateway acts as a bridge, allowing Power BI Service to securely communicate with Redshift during scheduled refreshes. You’ll need to configure the gateway, register the Redshift data source with it, and bind your dataset to use the gateway in Power BI Service. Without this setup, Power BI Service will be unable to reach your Redshift instance, resulting in connection timeouts like the one you’re experiencing.

[v-karpurapud]

Hi @TusharGaurav 

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.

Thank you.

[v-karpurapud]

Hi @TusharGaurav 

May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.

Thank you.

[v-karpurapud]

Hi @TusharGaurav 

Welcome to the Microsoft Fabric Forum. Also, thank you @Akash_Varuna for your quick response.

The error message you received, ODBC: ERROR [08S01] [Microsoft][Amazon Redshift] (10) Error occurred while trying to connect: [SQLState 08S01] timeout expired, indicates a network timeout. This typically happens because Power BI Desktop connects directly through local network, while Power BI Service is cloud-based and needs additional configuration to access external data sources like Redshift.

Here are possible workarounds to resolve this:

Configure an On-premises Data Gateway. This allows Power BI Service to securely access  Redshift database via a machine within the network or with access to the Redshift environment. Once installed, register the data source in Power BI Service and map the semantic model to use the configured gateway.

Alternatively, if use case permits, make your Redshift cluster publicly accessible and allow Power BI Service to connect directly. This involves modifying  Redshift cluster settings in AWS to enable public access and updating the security group to allow inbound access from Microsoft’s Power BI service IP ranges. This method is complex for production environments due to security risks.

After implementing either solution, update the dataset credentials in Power BI Service and initiate a test refresh to ensure connectivity is successful.

If this response resolves your query, kindly mark it as Accepted Solution to help other community members. A Kudos is also appreciated if you found the response helpful.

Thank you!

[Akash_Varuna]

Hi @TusharGaurav  Could you ensure Power BI Service has network access to your Redshift cluster by allowing its IP ranges in the Redshift security group. If the cluster isn't public, set up an On-Premises Data Gateway and configure it for Redshift. Update the data source credentials in Power BI Service using the correct authentication method. Adjust Redshift connection settings, such as increasing the timeout in the connection string or database parameters.