> 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/rdm/fr/knowledge-base/troubleshooting-articles/login-failed-for-userx-with-sql.md).

# Échec de la connexion pour UserX avec SQL

Corrigez l'erreur SQL 0x80131904 « Login failed for UserX » dans Remote Desktop Manager en déverrouillant le compte SQL verrouillé et en réinitialisant son mot de passe.

Si le code d'erreur `(0x80131904): Login failed for user 'UserX'` apparaît lors d'une tentative de connexion à l'espace de travail, il est possible que le compte ait été verrouillé après plusieurs tentatives de connexion. Cela dépend de l'application de la politique de mot de passe configurée.

### Déverrouiller la base de données SQL

La requête SQL suivante permet de confirmer si l'utilisateur a été verrouillé :

`SELECT LOGINPROPERTY('UserX','islocked')`

L'utilisateur peut être déverrouillé manuellement en allant dans les ***Propriétés*** – ***État*** de l'utilisateur et en décochant ***Verrouiller l'utilisateur SQL***. Ensuite, changez le mot de passe et exécutez finalement les changements.

#### Solution de rechange

Autrement, la requête suivante peut être utilisée :

`ALTER LOGIN [SQLID] WITH PASSWORD = '****' UNLOCK`

{% hint style="info" %}
Pour en savoir plus, consultez la [documentation SQL](https://learn.microsoft.com/en-us/sql/sql-server/?view=sql-server-ver16) de Microsoft.
{% 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/rdm/fr/knowledge-base/troubleshooting-articles/login-failed-for-userx-with-sql.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.