You need to identify the reports that produce the errors that Marc is receiving. What should you do?

The Subscriptions table stores subscription definitions and delivery configuration metadata, not runtime execution outcomes or error details, so it cannot identify which reports produced errors during execution.

Windows Event Viewer captures system-level and application-level events but does not record individual SSRS report execution results with enough granularity to map errors back to specific report names.

The ExecutionLog3 view in the report server database records one row per report execution and includes columns for report name, user, execution status, error messages, and parameters. Filtering this view by user and error status pinpoints exactly which reports are failing for Marc without manual log parsing.

The ReportServerService trace log records internal service-level diagnostics and exceptions but is a flat text file - it does not provide a structured, queryable mapping of errors to specific report names and users.