Showing results for 
Search instead for 
Did you mean: 

Alteryx Designer Knowledge Base

Definitive answers from Designer experts.

The highly anticipated Alteryx Community tradition is back! We hope you'll join us!

Learn More
We will be upgrading the Gallery to our 2019.4 release this Saturday, December 7th beginning at 9:00am MT. We expect the outage to take last approx. 2.5 hours.

GSSAPI Error: Internal Credentials Cache error when connecting to Hive or Impala via ODBC

Created on



When trying to connect to Impala or Hive using a Kerberized instance, an error appears: SASL(-1): generic failure: GSSAPI Error: Unspecified GSS failure. Minor code may provide more information (Internal Credentials Cache error).










Confirm that you are using Kerberos SSPI by asking your DB Admin and/or IT. 

If you manually generate a Kerberos ticket through the MIT Kerberos client or a kinit command, you are not using Kerberos SSPI.  





The "Internal Credentials Cache error" means that Alteryx cannot find the Kerberos ticket needed for authentication to connect to the Hadoop instance. By default, the ODBC driver uses the GSSAPI library to handle Kerberos authentication. With the GSSAPI library, Alteryx is trying to located a Kerberos ticket in the credentials cache but is unable to do so because Kerberos SSPI does not use the credentials cache.






Make sure you have the latest Simba Impala or Hive driver for the next steps.


1. Open the Windows ODBC AdministratorODBC Admin.png



2. Select the User or System Impala DSN that you have configured and press Configure:DSN.png



3. Once in the Simba Impala ODBC Driver DSN Setup window, press on Advanced Options:




4. Under Advanced Options, check the Enable for this DSN for the Use Only SSPI:

For Impala: 


For Hive:



5. Press OK.


6. Click "Test" in the main ODBC DSN Window to make sure the connection works. 


7. Start Alteryx and test your connection in an Input tool. 




Got the below error for HIVE using SIMBA HIVE ODBC driver. I have enabled the SSPI and ODBC test has succeeded but Designer failed. Any config need to be further tuned. 



Sorry wrong post.