Power BI is turning 10, and we’re marking the occasion with a special community challenge. Use your creativity to tell a story, uncover trends, or highlight something unexpected.
Get startedJoin us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. Register now.
Hi folks, I'm having a problem while connecting to AWS Redshift. Error Message:
ODBC: ERROR [08S01] [Microsoft][Amazon Redshift] (10) Error occurred while trying to connect: [SQLState 08S01] server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request.
I was able to connect to the cluster on AWS Redshift before. However, that cluster got shut down due to late payment. I am able to restore the same cluster using the redshift snapshot. But I can't connect to the database on the cluster anymore.
Need your help!
Many thanks~~
Solved! Go to Solution.
Here are a few steps you can take to troubleshoot this problem:
Check Cluster Status: Ensure that your Redshift cluster is up and running. Sometimes, even after restoration, the cluster might not be fully operational.
Security Group Settings: Verify that the security group settings for your Redshift cluster allow inbound traffic from your IP address. Make sure the necessary ports (default is 5439) are open.
Public Accessibility: If your cluster is in a VPC, ensure that it is set to be publicly accessible if you are connecting from outside the VPC.
SSL Certificates: If you are using SSL for your connection, check if the SSL certificates are correctly configured. Sometimes, issues with SSL certificates can cause connection problems.
Network Configuration: Ensure that there are no network issues or firewalls blocking the connection. You might need to adjust TCP/IP timeout settings on your client machine1.
ODBC Driver: Make sure you are using the latest version of the ODBC driver for Amazon Redshift. Sometimes, updating the driver can resolve connectivity issues.
Cluster Endpoint: Double-check the endpoint and port number you are using to connect to the cluster. Any changes during the restoration process might have altered these details.
Best Regards
Saud Ansari
If this post helps, please Accept it as a Solution to help other members find it. I appreciate your Kudos!
Here are a few steps you can take to troubleshoot this problem:
Check Cluster Status: Ensure that your Redshift cluster is up and running. Sometimes, even after restoration, the cluster might not be fully operational.
Security Group Settings: Verify that the security group settings for your Redshift cluster allow inbound traffic from your IP address. Make sure the necessary ports (default is 5439) are open.
Public Accessibility: If your cluster is in a VPC, ensure that it is set to be publicly accessible if you are connecting from outside the VPC.
SSL Certificates: If you are using SSL for your connection, check if the SSL certificates are correctly configured. Sometimes, issues with SSL certificates can cause connection problems.
Network Configuration: Ensure that there are no network issues or firewalls blocking the connection. You might need to adjust TCP/IP timeout settings on your client machine1.
ODBC Driver: Make sure you are using the latest version of the ODBC driver for Amazon Redshift. Sometimes, updating the driver can resolve connectivity issues.
Cluster Endpoint: Double-check the endpoint and port number you are using to connect to the cluster. Any changes during the restoration process might have altered these details.
Best Regards
Saud Ansari
If this post helps, please Accept it as a Solution to help other members find it. I appreciate your Kudos!
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Power BI update to learn about new features.
User | Count |
---|---|
72 | |
70 | |
55 | |
37 | |
31 |
User | Count |
---|---|
83 | |
64 | |
63 | |
49 | |
45 |