Amazon Redshift Linux ODBC Driver Connection fails with SSL

Published: 25 Feb 2019
Last Modified Date: 03 Mar 2020


When publishing an Amazon Redshift data source with 'Required SSL' enabled to Tableau Server on Linux, or opening a published workbook that connects to a Redshift data source with 'Required SSL' enabled on Linux the following error may occur:

Unable to connect to the data source.

Try connecting again. If the problem persists, disconnect from the data source and contact the data source owner.

The connection to the data source might have been lost
ReadBytes: Communication with the Tableau Protocol Server process was lost.
Unable to connect to the Amazon Redshift server ".......". Check that the server is running and that you have access privileges to the requested database.



  • Tableau Server 2018.3.3. 2019.2
  • Linux (Amazon Linux 2, CentOS, RHEL and Ubuntu)
  • Amazon Redshift
  • Amazon Redshift driver version: AmazonRedshiftODBC-64-bit-


To workaround the issue:
  1. Remove the Amazon Redshift driver version (AmazonRedshiftODBC-64-bit- from the Linux machine hosting Tableau Server.
  2. Install a previous version of the Amazon Redshift driver (e.g. AmazonRedshiftODBC-64-bit- Redshift driver versions are available here
Example remove command on Ubuntu Linux:
  1. To remove the Redshift driver run the following command:
    sudo apt-get remove --purge amazonredshift-64bit
  2. Download and install the earlier Redshift driver version following the instructions noted here.


Amazon Redshift driver version (AmazonRedshiftODBC-64-bit- includes ThirdParty SSL libraries that interfere with the Tableau Server provided SSL libraries.

Additional Information

The following warning message may appear in 'tabprotosrv_vizqlserver' log:

"excp","v":{"class":"redshift","dse-type":"NoDriver","excp-msg":"The drivers required to connect to the data source are not installed.\n","excp-type":"19DataSourceException","is-bad-request":false,"is-local-configuration-error":true,"is-remote-configuration-error":false,"msg":"DataSourceException::Throw"},"ctx":{"client-type":"vizqlserver","procid":"3569","requestID"

Discuss this article... Feedback Forum
Did this article resolve the issue?