DOCUMENT & DATA TOOLS

Turn IIS errors into a reviewable report.

Analyze W3C and FREB files locally. Summarize error paths, UTC time buckets, status codes, and recorded module evidence for your developer or hosting team.

Open workspace

Files and text are processed in your browser.

↔
Evidence-led troubleshootingIllustrative workflow
Group500.19Configuration errors
LocateRequest pathsWhere errors concentrate
ReportFREB modulesRecorded evidence

Investigation directions; no automatic root-cause guarantee

WORKSPACE

IIS Log Analysis Report

Upload redacted W3C .log or FREB .xml files. Queries, IP addresses, and usernames are omitted from the output.

Ready when you are.
ABOUT THIS TOOL

Use the report to guide a targeted investigation.

W3C files require a #Fields header including cs-uri-stem and sc-status. Time buckets use logged UTC dates and times. FREB evidence is summarized separately because it can describe requests already in W3C logs. Limit: 20 files, 20 MB each, 50 MB total, and 200,000 W3C rows. Source line numbers are retained, but raw logs and query strings are not packaged. Paths and filenames can still contain identifiers; redact before sharing.