Impala ODBC error with Power BI, though Kerberos

[#1]

Hi Everyone;

I have an issue with our PowerBI reports accessing Impala with Kerberos authentication via ODBC (64bit). We are using the Cludera ODBC Driver (64bit) for Impala v2.06.05.1005; PowerBI May 2020 version; and Impala v3.2x / CDH 6.3.3 and Kerberos .

Error #1:

[0] -1055784932: ODBC: ERROR [HY000] [Cloudera][KerberosSupport] (0) Error occurred during Kerberos library operation: Internal credentials cache error
ERROR [HY000] [Cloudera][KerberosSupport] (0) Error occurred during Kerberos library operation: Internal credentials cache error. The exception was raised by the IDbCommand interface.

I'm also seeing sporadic "Unexpected response" exceptions...

Error #2:

[0] -1055784932: ODBC: ERROR [HY000] [Cloudera][DriverSupport] (1170) Unexpected response received from server. Please ensure the server host and port specified for the connection are correct.
ERROR [HY000] [Cloudera][DriverSupport] (1170) Unexpected response received from server. Please ensure the server host and port specified for the connection are correct.. The exception was raised by the IDbCommand interface.

These are sporadic.   Is there a solution to this?

Thanks in advance...

[#2]

Hi,

These errors are generic errors that can see in the front end and these errors doesn't shows exact issue.

Regarding the Error #1:

Please check "Setting Up the Kerberos Credential Cache File"  for  credential cache for windows in the below documentation.

https://www.cloudera.com/documentation/other/connectors/impala-odbc/latest/Cloudera-ODBC-Driver-for-...

Also upgrade the ODBC connector to the latest version.

Regarding the Error #2:

It says "Unexpected response received from server" you need to check the below things to identify the issue: ( Power BI -> ODBC Driver -> LB -> Impala Daemon )

a. Check the ODBC driver logs at the time of issue , If you do not find anything enable trace level logs and check the errors.

b. If you have LB configured check the LB logs.

c. Try to connect manually for every impala daemon to find out if there is any issue with particular daemon.

d. If you faced an issue with connecting any daemon check the logs for more details.