← ClaudeAtlas

ssrstracelog-reviewlisted

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.
vanterx/mssql-performance-skills · ★ 5 · API & Backend · score 77
Install: claude install-skill vanterx/mssql-performance-skills
# 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 fa