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.

"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:...

Update the SSH_HOST_KEY_FP parameter in your DSN with the correct fingerprint shown in the log, or remove it to accept any host key.

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 7 days ago