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

# Fejlfinding af SQL Azure

Fejlfind fejl i SQL Azure-arbejdsområder i Remote Desktop Manager, herunder at adalsql.dll ikke kan indlæses, og at brugeren ikke kan gemmes i databasen.

### Problem 1: kan ikke oprette forbindelse til databasen

Når De prøver at bruge et Azure SQL-arbejdsområde, får De denne fejlmeddelelse:

```
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
```

### Løsning 1

For at løse problemet skal De se [Azure SQL](/rdm/da/getting-started/workspaces/workspace-types/alternative-workspaces/microsoft-azure-sql.md).

### Problem 2: kan ikke gemme brugeren i databasen

Når De opretter en bruger med godkendelse via en Entra ID-konto, får De denne fejlmeddelelse:

```
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.
```

### Løsning 2

De skal først definere Deres SQL Server Entra ID-administrator via Azure Portal og derefter logge på Remote Desktop Manager med den Entra ID-konto. Derfra kan De oprette nye Entra ID-konti (administrator og ikke-administrator). De nye administratorer kan også gøre det samme.

Se [Konfigurer Entra ID-administratoren](/rdm/da/getting-started/workspaces/workspace-types/alternative-workspaces/microsoft-azure-sql/enable-entra-id-authentication/configure-the-entra-id-administrator.md) for at få flere oplysninger.


---

# 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/da/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 `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.