How to connect with the Qlik Google BigQuery connector to the GBQ High-Throughput API?

[Andreas_Giesbrecht]

This article explains how to use/ troubleshoot connection issues with the Qlik GBQ connector when trying to connect to the Google BigQuery High-Throughput API (https://cloud.google.com/bigquery/docs/reference/storage/).

Some customers reported the following errors when trying to connect via Qlik GBQ connector (within the Qlik ODBC connector package) to that mentioned GBQ API:

Connection failed:
Please check the values for Username, Password, Host and other properties.
Details
Connection timeout expired

Or also errors like (after increasing the timeout):

Environment

• All QlikView and Qlik Sense environments 

Resolution

1. If you are facing issues like this, the first step would be to verify if the connection to the GBQ High-Throughput API works via an ODBC System DSN (based on a Google BigQuery third party driver like for example from here https://www.simba.com/products/BigQuery/doc/ODBC_InstallGuide/win/content/odbc/bq/features/ht-api.ht...)
   
   
2. Also it is helpful to verify if the reloads via ODBC System DSN are working outside of the Qlik product, here you can find detailed steps for a third party tool test: https://community.qlik.com/t5/Knowledge-Base/How-to-verify-ODBC-OLE-DB-connections-using-Excel/ta-p/...
   
   
3. If steps 1) and 2) were successfully verified please make sure on the Qlik GBQ connector side that the GBQ High-Throughput API is enabled, copy and paste the "HTAPI Minimum results size", the "HTAPI Minimum activation ratio" and "Trusted certificate path" from the ODBC system DSN settings (also try at the same time with "Allow Large Result Sets" option as well):
   
   
   
   
4. If the Qlik GBQ connector is still not working, please enable the logging level of the Qlik ODBC connector package to "ALL" (https://support.qlik.com/articles/000043270), rename the current file "QLIKSERVER3_QvOdbcConnectorPackage.log" in C:\ProgramData\Qlik\Custom Data\QvOdbcConnectorPackage\Log so that a fresh log file gets created, reproduce the issue and contact Qlik Support.