/ssrstracelog-review

name: ssrstracelog-review
description: Analyze SQL Server Reporting Services (SSRS) report server trace logs, RSReportServer.config / ReportingServicesService.exe.config excerpts, ExecutionLog3 query output, and related Windows Event Log entries to diagnose failed report server startups, database connectivity errors, memory pressure and AppDomain recycling, slow or aborted report processing, subscription delivery failures, and scale-out/encryption-key problems. Applies 24 checks (G1–G24) covering trace configuration health, startup and report-server-database connectivity, memory management and recycling, report execution performance from ExecutionLog3, subscription and delivery extensions, and scale-out deployment key management. Use this skill whenever a user pastes ReportServerService_<timestamp>.log content, RSReportServer.config/ReportingServicesService.exe.config XML, ExecutionLog3 output, or describes SSRS symptoms such as "report server unavailable", slow reports, failed subscriptions, or scale-out join errors.
triggers:
  - /ssrstracelog-review
  - /ssrs-trace-review
  - /rs-trace-review

SSRS Trace Log Review Skill

Purpose

Analyze SQL Server Reporting Services (SSRS) diagnostic artifacts to find why a report server fails to start, can't reach its report server database, runs reports slowly or aborts them, drops subscription deliveries, or fails to join a scale-out deployment. Applies 24 checks (G1–G24) across six categories:

• **G1–G4** — Trace configuration and log health: `DefaultTraceSwitch` level, file size

and retention settings, restart/recycle frequency visible in trace file rollover, and stale component-level trace overrides

• **G5–G9** — Startup and report server database connectivity:

`rsReportServerDatabaseUnavailable`, `rsReportServerDatabaseLogonFailed`, `rsErrorOpeningConnection` sub-causes, orphaned database pointers, and `rsServerConfigurationError`

• **G10–G13** — Memory pressure and AppDomain recycling: `MemorySafetyMargin` /

`MemoryThreshold` / `WorkingSetMaximum` configuration, hard recycles from memory allocation failures, and `RecycleTime` / `MaxAppDomainUnloadTime` tuning

• **G14–G18** — Report processing and rendering: `ExecutionLog3` time-phase breakdown,

legacy processing engine usage, `rsProcessingAborted` and error statuses, and external image fetch latency

• **G19–G21** — Subscriptions and delivery: file share and email delivery extension

failures, and subscription scheduling clustering

• **G22–G24** — Scale-out and encryption keys: `rsInvalidReportServerDatabase` after

upgrade, `rskeymgmt -j` join failures, and missing symmetric key backups

This skill is the SSRS counterpart to `sqlerrorlog-review` (Database Engine ERRORLOG) — use both together when SSRS symptoms trace back to the report server database engine.

Input

Accept any of:

• **Trace log excerpts** — `ReportServerService_<timestamp>.log` or (SSRS 2017+)

`Microsoft.ReportingServices.Portal.WebHost_<timestamp>.log` content, pasted as text. Lines follow the format `<component>!<thread>!<pid>!<MM/DD/YYYY-HH:MM:SS> <severity> <LEVEL>: <message>` (e.g. `library!WindowsService_10!4c7c!05/24/2016-01:05:06 e ERROR: ...`)

• **`ReportingServicesService.exe.config`** excerpts — the `DefaultTraceSwitch` value

(in the `<system.diagnostics><switches>` block) plus the `<RStrace>` section (`FileName`, `FileSizeLimitMb`, `KeepFilesForDays`, `TraceListeners`, `TraceFileMode`, and the `Components` setting that carries per-component trace overrides)

• **`RSReportServer.config`** excerpts — the `<Service>` section (`MemorySafetyMargin`,

`MemoryThreshold`, `WorkingSetMaximum`, `WorkingSetMinimum`, `RecycleTime`, `MaxAppDomainUnloadTime`, `PollingInterval`, `MaxQueueThreads`, `UrlRoot`)

• **`ExecutionLog3` query output** — results of

`SELECT * FROM ExecutionLog3 ORDER BY TimeStart DESC` against the report server database

• **Windows Application Event Log entries** for source "Report Server Windows Service" or

"ReportServer" (commonly Event ID 107 and related startup/connectivity events)

• A natural-language description ("SSRS shows 'report server can't open a connection to

the report server database' after a restart")

Where the files live

SQL Server 2016 (default instance MSSQLSERVER):
  Trace logs:   C:\Program Files\Microsoft SQL Server\MSRS13.MSSQLSERVER\Reporting Services\LogFiles\
  Trace config: C:\Program Files\Microsoft SQL Server\MSRS13.MSSQLSERVER\Reporting Services\ReportServer\bin\ReportingServicesService.exe.config
  Server config: C:\Program Files\Microsoft SQL Server\MSRS13.MSSQLSERVER\Reporting Services\ReportServer\RSReportServer.config

SQL Server Reporting Services 2017+ / Power BI Report Server (standalone installer):
  Trace logs:   C:\Program Files\Microsoft SQL Server Reporting Services\SSRS\LogFiles\
  Trace config: C:\Program Files\Microsoft SQL Server Reporting Services\SSRS\ReportServer\bin\ReportingServicesService.exe.config
  Server config: C:\Program Files\Microsoft SQL Server Reporting Services\SSRS\ReportServer\RSReportServer.config

Trace logs are created daily starting at the first entry after local midnight (UTC timestamp in the filename) and whenever the service restarts — a burst of new trace log files on the same day is itself a signal (see G3). `ExecutionLog3` is a view in the report server database (default name `ReportServer`).

How to Run

1. **Identify the artifact type(s)** in the input: trace log lines, trace config XML, server config XML, `ExecutionLog3` rows, Event Log entries, or a mix. 2. **Run G1–G4** against `ReportingServicesService.exe.config` / trace log filenames and header lines when present. 3. **Run G5–G9** against trace log error lines and Event Log entries — search for `rsReportServerDatabaseUnavailable`, `rsReportServerDatabaseLogonFailed`, `rsErrorOpeningConnection`, `rsServerConfigurationError`, and Event ID 107 first; these are usually the root cause of