Failed Request Tracing error LOG_FILE_MAX_SIZE_TRUNCATE

Date posted: 2011-11-10
Last updated: 2026-10-03

Learn how to resolve the Failed Request Tracing (FREB) error LOG_FILE_MAX_SIZE_TRUNCATE in IIS by increasing the maximum log file size with AppCmd.

As you've probably read in my post AppCmd introduction and examples, AppCmd is a very extensive tool to administer Windows Server IIS hosting environments. So here is a bit more about a common error message you might get using Failed Request Tracing (FREB): LOG_FILE_MAX_SIZE_TRUNCATE.

A Failed Request Tracing log file is 512 KB at most by default; when it's full, the trace is truncated and LOG_FILE_MAX_SIZE_TRUNCATE is logged. Raise siteDefaults.traceFailedRequestsLogging.maxLogFileSizeKB server wide with AppCmd.exe.

FREB error LOG_FILE_MAX_SIZE_TRUNCATE

If you've set up Failed Request Tracing - also known as "FREB" - for a website in IIS, and you've configured FREB with verbose information, a common error message you'll probably get is:

LOG_FILE_MAX_SIZE_TRUNCATE

The maximum size of a FREB log file in IIS 7+ is 512 KB by default. Once that size is reached, the log file is cut off (truncated) and a message LOG_FILE_MAX_SIZE_TRUNCATE is logged.

Did you know you can easily increase the FREB log file size server wide? The following AppCmd.exe command doubles the size to 1024 KB, or 1 MB:

# increase the maximum size for failed request logs
AppCmd.exe set config /section:sites `
 -siteDefaults.traceFailedRequestsLogging.maxLogFileSizeKB:1024

or 2 MB:

# increase the maximum size for failed request logs
AppCmd.exe set config /section:sites -siteDefaults.traceFailedRequestsLogging.maxLogFileSizeKB:2048

Interesting detail: FREB was first called Failed Request Event Buffering, and this is why the acronym doesn't match its name in Windows Server IIS.

When using a PowerShell command prompt you may have to quote the command:

C:\Windows\system32\inetsrv\appcmd.exe set config /section:sites `
  /"siteDefaults.traceFailedRequestsLogging.maxLogFileSizeKB:2048"

Verify the configuration change in the IIS Manager GUI: in the Configuration Editor for the system.applicationHost/sites section, siteDefaults > traceFailedRequestsLogging shows the new maxLogFileSizeKB value.

Install Failed Request Tracing IIS module

If you need to install the Failed Request Tracing module in IIS to enable it, use the Install-WindowsFeature cmdlet and the following command:

Install-WindowsFeature -Name Web-Http-Tracing

Notice the module is called "Web-Http-Tracing". See Install IIS in Windows 11 using PowerShell for additional IIS modules and features.

Analysing traces and logs is half the work. Here is how to use grep for forensic log parsing and analysis on Windows Server IIS.

This post is part of my IIS administration & hardening guide.

I write these posts in my spare time, based on real problems from my day job as a sysadmin. If this one saved you some debugging time, a small donation is much appreciated. Thanks! 🙏

Leave a Comment