> 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/login-failed-for-userx-with-sql.md).

# Login failed for UserX with SQL

Fixes a SQL login failed error in Devolutions Server caused by an account locked after repeated failed login attempts, with steps to unlock it.

If the `(0x80131904): Login failed for user 'UserX'` error code appears when attempting to connect to the workspace, it is possible that the account has been locked after multiple login attempts. It depends on the configured password policy enforcement.

### Unlocking the SQL Database

The following SQL Query will confirm if the user has been locked:

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

The user can be manually unlocked by going to the user ***Properties*** – ***Status*** and unchecking ***Lock SQL user***. Then changing the password and finally executing the changes.

#### Alternative

Alternatively, the following query can be used:

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

{% hint style="info" %}
To learn more, read the Microsoft [SQL documentation](https://learn.microsoft.com/en-us/sql/sql-server/?view=sql-server-ver16).
{% 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/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.