> 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/es/knowledge-base/troubleshooting-articles/sql-azure-troubleshooting.md).

# Resolución de problemas de SQL Azure

Solucione errores de espacios de trabajo de SQL Azure en Remote Desktop Manager, incluidos los fallos de carga de adalsql.dll y los errores de imposibilidad de guardar la base de datos de usuarios.

### Problema 1: no se puede conectar a la base de datos

Al intentar usar un espacio de trabajo de Azure SQL, recibe este mensaje de error:

```
Unable to connect to the database!

Unable to load adalsql.dll (Authentication=ActiveDirectoryPassword). Error code: 0x2. For more information, see http://go.microsoft.com/fwlink/?LinkID=513072
```

### Solución 1

Para resolver este problema, consulte [Azure SQL](/rdm/es/getting-started/workspaces/workspace-types/alternative-workspaces/microsoft-azure-sql.md).

### Problema 2: no se puede guardar el usuario en la base de datos

Al crear un usuario con autenticación de cuenta de Entra ID, recibe este mensaje de error:

```
Unable to save the user in the database!

Principal '...' could not be created. Only connections established with Active Directory accounts can create other Active Directory users.
```

### Solución 2

Primero debe definir el administrador de Entra ID de su SQL Server a través del Azure Portal y, a continuación, iniciar sesión en Remote Desktop Manager con esa cuenta de Entra ID; desde allí podrá crear nuevas cuentas de Entra ID (administradoras y no administradoras). Esos nuevos administradores también podrán hacer lo mismo.

Para más información, consulte [Configurar el administrador de Entra ID](/rdm/es/getting-started/workspaces/workspace-types/alternative-workspaces/microsoft-azure-sql/enable-entra-id-authentication/configure-the-entra-id-administrator.md).


---

# 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 dynamically 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/es/knowledge-base/troubleshooting-articles/sql-azure-troubleshooting.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 `build a script that syncs our docs to a CMS` 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.