> 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/da/knowledge-base/troubleshooting-articles/devolutions-server-unavailable-after-reboot.md).

# Devolutions Server er ikke tilgængelig efter genstart

Retter, at Devolutions Server bliver utilgængelig efter en genstart, ved at konfigurere planlægningstjenesten og W3SVC til at afhænge af opstarten af SQL Server.

Den SQL Server, hvor Devolutions Server er placeret, er muligvis ikke startet, når instansen af Devolutions Server starter. Derfor kan planlægningstjenesten eller webprogrammet for Devolutions Server ikke oprette forbindelse til databasen og returnerer en fejlmeddelelse, som kan se sådan ud i Windows-hændelsesloggene:

Tjenesten DevolutionsSchedulerService (DVLS) blev afsluttet med følgende fejl:\
`An exception occurred in the service when handling the control request.`

#### Løsning

Kør kommandoerne nedenfor for at konfigurere planlægningstjenesten for Devolutions Server og W3SVC (som er en integreret del af IIS-funktionaliteten), så de afhænger af SQL Server. Denne justering sikrer, at de først starter, når SQL Server er fuldt startet.

* Planlægningstjeneste for Devolutions Server: `sc config <Devolutions Scheduler Service Name> depend= "<your SQL Server Instance service>"`
* W3SVC: `sc config W3SVC depend= "WAS/HTTP/<your SQL Server Instance service>"`\
  Bemærk, at WAS og HTTP er standardafhængigheder for W3SVC.

Sådan ryddes afhængigheder for tjenester: `sc config <service name> depend= ""`


---

# 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/da/knowledge-base/troubleshooting-articles/devolutions-server-unavailable-after-reboot.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.