(1170) Unexpected response received from server

[#1]

I'm able to create a System DSN using the "ODBC Data Source Administrator" with a successfull test.

My Authentication mecanism is "User Name and Passowrd"

SASL checked

SSL Options: "Enable SSL" checked

SSL Options: I'm providing the path to a certificate

BUT, trying to connect using pyodbc with the same parameters (server, port, username and password) gives always the same error below whatever the auth_mechanism provided:

pyodbc.connect("DRIVER={Cloudera ODBC Driver for Impala};\
host={server_address};\
port=21051;\
SSL=1;\
auth_mechanism=GSSAPI;\
user=myusername;\
password=mypassword;\
trustedcerts=cert.pem;\
")

Error: ('HY000', u'[HY000] [Cloudera][DriverSupport] (1170) Unexpected response received from server. Please ensure the server host and port specified for the connection are correct. (1170) (SQLDriverConnect); [HY000] [Cloudera][DriverSupport] (1170) Unexpected response received from server. Please ensure the server host and port specified for the connection are correct. (1170)')

I'm using:

ODBC Version: 03.80
Driver Version: 2.6.0.1000
Bitness: 64-bit
Locale: fr_CA

OS: Windows 10 Pro

[#2 · Accepted solution]

I finally resolved the issue by enclosing UID, PWD, and trustedcerts in braces:

UID={MY USERNAME}

PWD={MY PASSWORD}

trustedcerts={path to file}

[#3]

Hi,

I had the same error and I tried the solution you have provided.

Now it's showing a different error code saying ERROR [HY000] [CLOUDERA] [Driver Support] (1140).

Unable to load CA certificates from the location.

Could you provide a solution for this?

Thanks in advance.

Vinay

[#4]

...but WHERE did you put those parameters?

I am having the same issue. My file DSN will connect just fine in the ODBC Administrator applet, but in pyodbc it gives the same error. Did you add those parameters to your DSN?

[#5]

@pudnik26354 

As this thread was marked 'Solved' in Jan 2019 you would have a better chance of receiving a useful response by starting a new thread. This will also provide you with the opportunity to provide details specific to your environment that could aid others in providing a more accurate answer to your question. 

[#6]

@pudnik26354 Did you already solve your problem. I have the same issue using iodbc and pyodbc on a debian based system.

[#7]

I think it was because if you use kerberos, the kerberos credentials have to be in upper case because they are case sensitive