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

# Installation

Provides step by step instructions for installing the failed request tracing feature in IIS on Windows Server to troubleshoot Devolutions Server.

Follow these instructions to enable failed request tracing in IIS:

{% hint style="info" %}
The following steps apply to Windows Server 2016 and later.
{% endhint %}

1. Open the ***Server Manager***.
2. In the ***Manage*** tab, select ***Add Roles and Features***.
3. In the **Installation Type**\* section, select the installation type that applies to your situation, then click ***Next***.
4. In the ***Server Selection*** section, select the destination server, then click ***Next***.
5. In the ***Server Roles*** section, expand ***Web Server (IIS)*** role, ***Web Server***, then ***Health and Diagnostics***. Check the ***Tracing*** box and click ***Next***.
6. In the ***Features*** section, simply click ***Next***.
7. In the ***Confirmation*** section, click ***Install***.
8. In the ***Results*** section, click ***Close***.


---

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