Using Windows ODBC client to connect to cluster fails with “Bad Status” error

Remove any custom HTTP header entries referencing the HTTP path.

Written by allia.khosla

Last published at: August 12th, 2025

Problem

When you attempt to connect to a Databricks cluster from an on-premises machine using the Windows ODBC client, the attempt fails with the following error.

[Simba] (DSI] An error occurred while attempting to retrieve the error message for key 'TEHTTPClientDetailedException' with message parameters [Bad Status: Unrecognized
response with no error message header. Status code: 400] and component ID 200: Could not open error message files - Check that *C: Program Files \Simba Spark ODBC Driver Vib len-US \ThriftExtensionMessages.xml" or "C: Program Files (Simba Spark ODBC Driver Vib \ThriftExtensionMessages _en-US.xml* exists and are accessible.

 

Cause

Your custom HTTP header is configured with the HTTP path information. 

The HTTP path should only be specified in the connection parameters, not set as a custom header. Setting the HTTP path in both places results in duplicate configuration and the driver failing to authenticate the connection, leading to error 400.

 

Solution

Remove any custom HTTP header entries referencing the HTTP path. 

  • Open your ODBC client in Windows.
  • At the bottom of the window, click the HTTP options… button.
  • Ensure that the HTTP path is only specified in the standard connection parameter field. 
  • If you see the HTTP path in the Custom HTTP Headers field, click the path to select, and then click Remove.
  • Click OK to save and exit.