Enable Failed Request Tracing (FRE) for a specific website in Internet Information Services (IIS) to capture detailed information about requests that result in errors. This allows you to identify the specific modules or configurations causing issues like 500-series errors.
Before you begin
You will need:
Administrator access to the Windows Server.
Access to the Internet Information Services (IIS) Manager console.
Enable Failed Request Tracing for a specific website
Open Internet Information Services (IIS) Manager.
In the Connections pane, expand the server node and select the Sites folder.
Select the specific website for which you want to enable tracing.
In the Features View pane, double-click Failed Request Tracing.
In the Failed Request Tracing window, click Get Folder Settings in the Actions pane.
In the Failed Request Tracing Feature Properties window, click Add in the Actions pane.
Select the specific HTTP status codes you wish to track (e.g., 500, 503, 404) and click OK.
Click Apply in the Actions pane to save the settings.
Confirm the result
The Failed Request Tracing window will now show the selected status codes under the Selected Status Codes section.
When a request fails with one of the selected codes, a
.xmlfile will be generated in theC:\inetpub\_failuresfolder (unless a custom path was specified in the configuration).
If a request still does not generate a trace file
If you receive a 500 error but no trace file is generated, verify the following:
Permissions: Ensure the IIS worker process has permission to write to the destination folder.
Module Presence: Ensure the "Request Filtering" and "IIS Web Farm" features are enabled in the Windows Server features.
Configuration Scope: Ensure you applied the settings at the Site level rather than the Server level if you only want to track one specific website.
Limitations
Failed Request Tracing logs are generated as XML files. These files are intended for technical analysis of server-side errors and do not contain information regarding client-side issues, such as incorrect passwords or local browser errors.
