> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/server/knowledge-base/troubleshooting-articles/maintenance-tool-database-connection-is-invalid.md).

# Maintenance Tool database connection is invalid

Fixes an invalid maintenance tool database connection error in the Devolutions Server Console caused by missing read access to the encryption config file.

This error message occurs when trying to make changes in the Devolutions Server Console while being unable to access the `encryption.config` file:

```
Maintenance Tool database connection is invalid
```

### Solution

1. Open command prompt and type `whoamI`. It might simply be that you are connected as a user without permission to access the encryption file.
2. Make sure you have the ***Read*** permission on the `encryption.config` file located in `C:\inetpub\wwwroot\dvls\App_Data`.
3. Once the correct permission has been granted, restart the Devolutions Server Console.

{% hint style="info" %}
If the issue persists, refer to the DVLS\_Owner account in the [Pre-deployment account survey](/server/knowledge-base/knowledge-base-articles/pre-deployment-account-survey.md) article.
{% endhint %}


---

# 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.devolutions.net/server/knowledge-base/troubleshooting-articles/maintenance-tool-database-connection-is-invalid.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.