> 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/troubleshooting-and-faq/database-error.md).

# Database Error

This page focuses on issues encountered while using the **WriteBackExtreme Management Console**.

It includes troubleshooting steps for login failures, authentication problems, missing configuration options, permission errors, and unexpected behaviour within the console interface. You’ll also find guidance on validating configuration changes and ensuring they are correctly applied.

Use this page when you can access WriteBackExtreme, but experience issues managing or configuring it.

<table><thead><tr><th>Error</th><th width="148">Component</th><th>Probable cause</th></tr></thead><tbody><tr><td>Unexpected response from server during a HTTP connection: Could not refill buffer.</td><td>Databricks</td><td>SSL Option is not selected in odbc settings</td></tr><tr><td>Driver not found</td><td></td><td>This error can happen when using an ODBC driver like snowflake, databricks, teradata on linux systems. It indicates there is probably a problem in the installation of the php dependency of WriteBackExtreme that has been compromised. Run `php -m` command to check what version you are on and run the install.sh again. </td></tr></tbody></table>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.infotopics.com/writebackextreme/troubleshooting-and-faq/database-error.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.