> 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/beyondtrust-issues.md).

# Problemer med BeyondTrust

Løs almindelige fejl i BeyondTrust Password Safe-dashboardet, herunder URI-format samt fejl 404, 500 og 401, ved at rette felterne for vært og API-nøgle.

### Problem 1

System.uriformatexception: invalid uri: the format of the uri could not be determined.

#### Løsning

I feltet ***Vært*** i posten BeyondTrust Password Safe-dashboard skal De sørge for at angive servernavnet som <https://beyondtserver>.

Angiv ikke serverens IP-adresse. Hvis De angiver IP-adressen i stedet for servernavnet, returneres denne fejl.

### Problem 2

System.net.webexception: the remote server returned an error: (404)

#### Løsning

I feltet ***Vært*** i posten BeyondTrust Password Safe-dashboard skal De sørge for at angive servernavnet som <https://beyondtserver>.

Angiv ikke web-URL'en til at åbne konsollen fra en webbrowser, f.eks. <https://beyondtserver/eEye.RetinaCS.Server/PasswordSafe>.

### Problem 3

Not found system.net.webexception: the remote server returned an error: (500) internal server error.

#### Løsning

I feltet ***Vært*** i posten BeyondTrust Password Safe-dashboard skal De sørge for at angive servernavnet som <https://beyondtserver>.

Angiv ikke web-URL'en til at åbne konsollen fra en webbrowser, f.eks. <https://beyondtserver/eEye.RetinaCS.Server/PasswordSafe>.

### Problem 4

System.net.webexception: the remote server returned an error: (401) unauthorized.

#### Løsning

I feltet for ***program-API***-nøglen i posten BeyondTrust Password Safe-dashboard skal De sikre, at De har angivet den rigtige nøgle.

### Problem 5

Beyond Trust Password Safe eller BeyondTrust Password Safe-dashboardet er tomt, og der returneres ingen fejl.

#### Løsning

Sørg for, at valgmuligheden ***Aktivér til API*** er markeret for Deres privilegerede konto i BeyondTrust.

Sørg for, at kontoen har tilladelsen ***Password Safe System Management*** til REST-API'en i BeyondTrust. Denne tilladelse kræves for at læse, skrive, ændre eller udløse opdateringer og genindlæsninger af administrerede systemer via den offentlige REST-API. Når den mangler, kan BeyondTrust returnere følgende fejl uden at vise den, så Password Safe eller dashboardet forbliver tomt, og der vises ingen fejl:

System.Net.WebException: The remote server returned an error: (403) Forbidden.


---

# 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/beyondtrust-issues.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.