> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/writebackextreme/features/database-connections/databricks/windows.md).
# Windows
{% hint style="info" %}
For WriteBackExtreme 6.x and later, use a 64-bit **System DSN** when configuring DSN-based Databricks connections.
WriteBackExtreme 6.x runs as a Windows service, so User DSNs should not be used. A User DSN is only available to the Windows user that created it, while the WBE service needs access to the DSN from the service context.
For WriteBackExtreme 5.x, User DSNs may still be used only when WriteBackExtreme is not running as a Windows service, and the connection is executed under the same Windows user that created the DSN.
{% endhint %}
### 1. Create a System DSN
Open the 64-bit ODBC Data Source Administrator:
`C:\Windows\System32\odbcad32.exe`
Go to the **System DSN** tab and create a new DSN using the Databricks ODBC Driver.
### 2. Configure the main DSN settings
Fill in the main connection details in the Databricks ODBC Driver DSN setup window.
| Field | Value |
| ---------------- | ----------------------------------------------------------- |
| Data Source Name | Choose a clear DSN name, for example `databricks_writeback` |
| Host | Databricks server hostname |
| Port | `443` |
| Database | Databricks database/schema, or `default` |
| Authentication | User Name and Password |
| User Name | `token` |
| Password | Databricks personal access token |
| Thrift Transport | HTTP |
### 3. Configure HTTP options
Click **HTTP Options** and enter the Databricks HTTP Path.
| Field | Value |
| --------- | --------------------------------------------- |
| HTTP Path | Databricks SQL Warehouse or cluster HTTP Path |
### 4. Configure SSL options
Click **SSL Options** and enable SSL.
### 5. Configure Advanced Options (optional)
{% hint style="info" %}
This setting can help prevent issues when string values are longer than the driver’s default length. If your environment does not require larger text values, you can leave the default value unchanged. [Malformed UTF-8 characters. Possibly incorrectly encoded](https://docs.infotopics.com/writebackextreme/troubleshooting-and-faq/extension-errors/malformed-utf-8-characters.-possibly-incorrectly-encoded)
{% endhint %}
Click **Advanced Options**.
The following setting is optional, but can be useful when working with larger text values.
| Field | Recommended value |
| ---------------------------- | ----------------- |
| Default string column length | `4000` |
### 6. Configure password options
Click **Password Options** and set the password encryption option.
| Field | Value |
| ----------- | ------------------------- |
| Encrypt For | All Users of this Machine |
If WriteBackExtreme is running as a Windows service, the Databricks token/password must be encrypted for all users of the machine.
In the DSN setup:
1. Click **Password Options**.
2. Set **Encrypt For** to **All Users of this Machine**.
3. Save the DSN.
This is important because the DSN may be created by one Windows user, while WriteBackExtreme runs under a different Windows service account. If the password is encrypted for the current user only, WriteBackExtreme may not be able to decrypt it.
If you are using an older WriteBackExtreme 5.x setup that does not run as a Windows service, **Current User Only** may work, but only when the same Windows user creates and uses the DSN.
### 7. Test the DSN connection
After saving the DSN, test the connection from the ODBC Data Source Administrator.
Then go to the WriteBackExtreme management console, create the Databricks connection, and test the connection there as well.
### Create the connection in WriteBackExtreme
In the WriteBackExtreme management console:
1. Create a new connection.
2. Select Databricks.
3. Select **Use DSN**.
4. Enter or select the DSN name created in the ODBC Data Source Administrator.
5. Fill in the required connection fields.
6. Click **Test Connection**.
7. Save the connection.
### Troubleshooting
| Error | Possible cause | Resolution |
| ---------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
| Data source name not found and no default driver specified | The DSN name is incorrect, the DSN was created as a User DSN instead of a System DSN, or the driver is not installed on the WBE server | Create a 64-bit System DSN, make sure the DSN name matches exactly, and confirm the Databricks ODBC Driver is installed on the WBE server |
| Failed to decrypt data | The password/token was encrypted for the current Windows user only | In Password Options, set **Encrypt For** to **All Users of this Machine** |
| Unauthorized or forbidden | The Databricks token or permissions are incorrect | Verify the token, warehouse access, catalog, schema, and table permissions |
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.infotopics.com/writebackextreme/features/database-connections/databricks/windows.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.