> 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/fr/knowledge-base/troubleshooting-articles/failed-request-tracing-with-iis.md).

# Traçage des requêtes ayant échoué dans IIS

Présente le suivi des requêtes ayant échoué dans IIS pour résoudre les erreurs HTTP 500 dans Devolutions Server, en couvrant l'installation, la configuration et les journaux.

Apprenez à installer et à configurer une règle de journal de suivi des requêtes ayant échoué pour résoudre les problèmes d'erreur HTTP 500 sur le site IIS.

* [Activer le suivi des requêtes ayant échoué dans IIS](/server/fr/knowledge-base/troubleshooting-articles/failed-request-tracing-with-iis/installation.md) : Instructions détaillées étape par étape pour ajouter le rôle sur un Windows Server.
* [Configurer le suivi des requêtes ayant échoué dans IIS](/server/fr/knowledge-base/troubleshooting-articles/failed-request-tracing-with-iis/configuration.md) : Configuration nécessaire pour résoudre les problèmes d'erreur HTTP 500.
* [Consulter le journal de suivi des requêtes ayant échoué](/server/fr/knowledge-base/troubleshooting-articles/failed-request-tracing-with-iis/logs.md) : Comment consulter les journaux de suivi des requêtes ayant échoué.

Pour plus d'information, veuillez consulter la documentation de Microsoft sur le [suivi des requêtes ayant échoué](https://learn.microsoft.com/en-us/iis/configuration/system.webServer/tracing/traceFailedRequests/).


---

# 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/fr/knowledge-base/troubleshooting-articles/failed-request-tracing-with-iis.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.