Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
1 year ago
Solved

I am getting time out error

This is to inform i am getting this error due to this report not able to access. This confirms the timeout is specifically coming from Power BI → Amazon Redshift ODBC connection. The root cause is t...
Need Help
  • Anonymous's avatar
    Anonymous
    1 year ago

    Hi Anonymous 

    Thank you for reaching out regarding the timeout error when connecting Power BI to Amazon Redshift via ODBC. This issue typically arises because Power BI is unable to establish a TCP connection to the Redshift cluster on port 5439.

    Please follow these troubleshooting steps:

    Test Connectivity: Run the command :
    Test-NetConnection <redshift-cluster-endpoint> -Port 5439
    From your system. If the test fails, this indicates a network or firewall issue.

    Review AWS Security Groups: Go to your Redshift cluster’s VPC Security Groups and ensure inbound rules allow TCP traffic on port 5439 from your local machine’s IP (for Power BI Desktop) and Power BI service IP ranges (for cloud refresh).

    Check VPC and NACL Settings: Verify that the Redshift cluster’s subnet has appropriate routing and NACL rules for inbound and outbound traffic on port 5439.

    Update ODBC Driver: Install the latest Amazon Redshift ODBC driver and confirm that your Power BI connection string is accurate.

    Increase Connection Timeout: In Power BI’s Data Source Advanced options, set the Connection Timeout to at least 300 seconds.

    Validate Credentials: Test your Redshift credentials in SQL Workbench/J or DBeaver. If they work there but not in Power BI, review your Power BI ODBC configuration.

    This error is most often due to AWS Security Group or firewall rules blocking the connection. After following the steps above, Power BI should be able to connect successfully.

    Please let us know if you continue to experience issues. We are here to help.

    Best Regards,
    Tejaswi 

burakkaragoz's avatar
burakkaragoz
Icon for Super User rankSuper User
1 year ago

Hi Anonymous ,

 

A timeout error in Power BI, especially with Amazon Redshift ODBC connections, usually means your query is taking too long to complete. Here are steps you can take to resolve this:

  1. Optimize your queries. Remove unnecessary columns or complex calculations that may slow down processing.
  2. Increase the timeout value in your ODBC connection string, for example, Timeout=180. Remember, Power BI Service has a hard limit, typically 120 minutes, so setting a higher value will not help beyond this.
  3. Reduce the amount of data you are importing by applying filters to your data source.
  4. Check your Redshift server and network performance. High load or network instability can also cause timeouts. Consult your IT or database administrator if needed.
  5. Be aware of Power BI Service limitations. Large or slow queries may not finish before the timeout.

For additional perspective, a similar thread recommends setting query durations below the service limit, with many users choosing 90 minutes for reliability. You can read more here:
Time out error in Power BI desktop: https://community.fabric.microsoft.com/t5/Desktop/Time-out-error-in-Power-BI-desktop/m-p/920423

Official documentation:
Power BI data refresh overview: https://learn.microsoft.com/en-us/power-bi/connect-data/refresh-data

If you need more targeted help, please share your ODBC connection string and a sample query.

If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a Kudos if you found my response helpful.
This response was assisted by AI for translation and formatting purposes.