Guides
  1. BEEM ODBC Driver

Troubleshooting

Troubleshooting

Enable debug logging

Set these environment variables before launching your application:

BEEM_ODBC_LOG=/path/to/beem_odbc.log
BEEM_ODBC_LOG_LEVEL=debug

On Windows, you can set them permanently via System Properties or PowerShell:

[System.Environment]::SetEnvironmentVariable("BEEM_ODBC_LOG", "C:\ODBC\BEEM\beem_odbc.log", "User")
[System.Environment]::SetEnvironmentVariable("BEEM_ODBC_LOG_LEVEL", "debug", "User")

Restart the application after setting the variables.

Common issues

"Driver not found" or "Data source name not found"

The driver is not registered with the ODBC Driver Manager.

  • Windows: Run the odbcconf registration command as Administrator. Verify the driver appears in ODBC Data Sources (64-bit) > Drivers tab.
  • macOS/Linux: Run odbcinst -q -d to list registered drivers. Re-run the odbcinst -i -d command if the driver is missing.

Connection hangs or times out

This typically means the secure tunnel established but the backend connection is failing silently.

  • Check that SSL_MODE is not set to verify-full when connecting through a tunnel. The driver automatically downgrades to require when a tunnel is detected, but manual DSN entries may override this.
  • Verify the backend ODBC driver (Amazon Redshift or PostgreSQL) is installed and accessible.
  • Check the log file for SSH channel opened followed by TCP side closed — this indicates the data warehouse rejected the connection.

"No database username"

The connection carried no UID. In Power BI this means Anonymous was chosen
for a DSN that has no credentials stored in it: Anonymous sends nothing but the
DSN name, and setup does not write UID/PWD into the DSN.

Pick the UsernamePassword option instead and enter your warehouse
credentials. To clear a remembered choice, go to File > Options and settings >
Data source settings, select the BEEM source and Clear Permissions.

The BEEM connector does not appear in Power BI

The installer copies BEEM.pqx into the Custom Connectors folder of the account
that ran it. Check what it did:

Get-Content "$env:ProgramData\BEEM\connector-install.log"

You can re-run the copy for the current user at any time:

powershell -ExecutionPolicy Bypass -File "C:\Program Files\BEEM\ODBC\install-connector.ps1"

Restart Power BI Desktop afterwards. If someone else signs in to the same
machine, they need their own run — see
Offline and silent installation.

"Invalid password" or authentication errors

  • Double-check your username and password.
  • Check the log for the exact SQLSTATE and error message — it will show what the backend reported.

Power BI shows "We couldn't authenticate with the credentials provided"

  • Verify the connection works outside Power BI first (use the Test Connection button in ODBC Data Sources).
  • In Power BI, try deleting the cached credentials: File > Options > Data source settings > select the BEEM source > Clear Permissions.

Power BI navigator is empty or shows no tables

  • The driver only shows your workspace tables. If your account has no workspace schemas assigned, no tables will appear.
  • Check the log for SQLTablesW calls to see what the backend returned.

SSH host key verification failed

The log will show:

SSH host key MISMATCH: expected SHA256:..., got SHA256:...

This means SSH_HOST_KEY_FP is set in your DSN and the bastion presented a
different key.

Confirm the expected fingerprint against your BEEM warehouse configuration, then
correct SSH_HOST_KEY_FP. Do not copy the got SHA256:... value out of the log to make
the error go away, and do not remove the parameter — a mismatch is exactly what
this check exists to report.

SSH HOST KEY CHANGED

SSH HOST KEY CHANGED for bastion.example.com:22 — refusing to connect.

You are not using SSH_HOST_KEY_FP, so the driver recorded the bastion's key the
first time it connected, and the key has since changed. Either the bastion was
rebuilt or the connection is being intercepted.

The recorded keys live in %APPDATA%\BEEM\known_hosts (Windows) or
~/.config/BEEM/known_hosts, one line per host:port. The error names the line.

Confirm the new fingerprint against your BEEM warehouse configuration before
doing anything else. If it is legitimate, delete that line and reconnect to record the
new key. Deleting the whole file also works but discards every other bastion you
have connected to, so you would re-trust them all blindly on the next connect.

First connection recorded a key you did not expect

The log line First connection to … — recorded host key SHA256:… appears once
per bastion. If that fingerprint does not match your BEEM warehouse
configuration, treat it as an interception: delete the line from known_hosts, set
SSH_HOST_KEY_FP to the correct value, and report it.

Getting help

If you're still stuck, email our team at [email protected] with:

  1. Your log file (with BEEM_ODBC_LOG_LEVEL=debug)
  2. The connection parameters you're using (redact passwords)
  3. The error message or behavior you're seeing

Updated about 1 month ago