> 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/fr/knowledge-base/troubleshooting-articles/maintenance-tool-database-connection-is-invalid.md).

# Maintenance Tool database connection is invalid

Corrige une erreur de connexion à la base de données de l'outil de maintenance dans la Devolutions Server Console causée par un accès en lecture manquant au fichier de configuration du chiffrement.

Ce message d'erreur survient lorsqu'on tente d'apporter des modifications dans la Devolutions Server Console sans pouvoir accéder au fichier `encryption.config` :

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

### Solution

1. Ouvrez l'invite de commande et tapez `whoamI`. Il est possible que vous soyez simplement connecté en tant qu'utilisateur n'ayant pas la permission d'accéder au fichier de chiffrement.
2. Assurez-vous d'avoir la permission ***Read*** sur le fichier `encryption.config` situé dans `C:\inetpub\wwwroot\dvls\App_Data`.
3. Une fois la bonne permission accordée, redémarrez la Devolutions Server Console.

{% hint style="info" %}
Si le problème persiste, consultez le compte DVLS\_Owner dans l'article [Sondage sur les comptes de pré-déploiement](/server/fr/knowledge-base/knowledge-base-articles/pre-deployment-account-survey.md).
{% 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/fr/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.