Windows Installation
Windows Installation
Install with the installer
Run it and follow the prompts. This is the supported path and the one to use
unless you have a specific reason not to. The installer:
- installs and registers the BEEM ODBC Driver
- installs the Power BI connector, signed, into the Custom Connectors folder
of the account running the installer, and trusts its certificate so Power BI
loads it without you changing any security settings. If several people sign in
to the same machine, see
Offline and silent installation. - registers the
beem://handler used by the setup page
The installer is signed by BEEM Technologies Inc. Windows may still show a
SmartScreen prompt — if it does, choose More info > Run anyway.
Prerequisites
- Windows 10 or later (64-bit)
- A backend ODBC driver — Amazon Redshift ODBC Driver (x64) is recommended.
The installer checks for it and offers a download link if it is missing.
Silent install
For SCCM, Intune or scripted deployment, see
Offline and silent installation.
Configure the connection
After installing, create a DSN:
- Open ODBC Data Sources (64-bit) from the Start menu, as administrator
- On the System DSN tab click Add — use System DSN, not User DSN, so
Power BI and the on-premises gateway can both read it - Select BEEM ODBC Driver and click Finish
- Fill in the dialog:
- DSN Name — a name for this connection (e.g.
BEEM) - Server, Port, Database — from your BEEM settings
- Backend Driver — your installed backend ODBC driver
- SSH settings — bastion host, user and key file, from your BEEM
warehouse configuration
- DSN Name — a name for this connection (e.g.
- Click Test Connection
- Click OK to save
The first connection records the bastion's host key and refuses to connect if it
ever changes. If your BEEM warehouse configuration lists a fingerprint, set
SSH_HOST_KEY_FP on the DSN to pin it explicitly — see
Connection Reference.
Manual installation
Only needed for custom deployments or troubleshooting. The installer does all of
this for you, including the Power BI connector, which the steps below do not
cover.
-
Download
beem_odbc.dllfrom the
latest release -
Copy the DLL to a permanent location:
mkdir "C:\ODBC\BEEM" -Force copy beem_odbc.dll "C:\ODBC\BEEM\" -
Register the driver (run as Administrator):
odbcconf /a {INSTALLDRIVER "BEEM ODBC Driver|Driver=C:\ODBC\BEEM\beem_odbc.dll|Setup=C:\ODBC\BEEM\beem_odbc.dll||"} -
Verify the driver appears in ODBC Data Sources (64-bit) > Drivers tab,
then create a DSN as above.
Enable logging
Set the BEEM_ODBC_LOG environment variable to a file path:
[System.Environment]::SetEnvironmentVariable("BEEM_ODBC_LOG", "C:\ODBC\BEEM\beem_odbc.log", "User")By default, the driver logs to C:\ODBC\BEEM\beem_odbc.log or %TEMP%\beem_odbc.log.
Control the log level with BEEM_ODBC_LOG_LEVEL:
| Value | What is logged |
|---|---|
error | Connection failures, backend errors |
info | Connection lifecycle, configuration (default in release builds) |
debug | Per-call tracing, attribute queries, row fetches |
debug writes connection strings to the log with passwords masked. Review a log
before sharing it.
Updated about 1 month ago
