Better error reporting for Data Driven Subscriptions
Data Driven subscriptions currently just report a count of reports that succeeded or failed. When only some of the reports of the subscription fail, it's very difficult to determine which particular reports failed, and there appears to be no logging of delivery errors anywhere to aid in diagnosing the root cause.
I want to be able to find any delivery errors that occur, and be able to find the individual reports in the subscription that failed to diagnose and rerun them.
Without knowing which reports failed or knowing why delivery failed makes it somewhat difficult to recommend using Reporting Services subscriptions for high profile reports where reliable delivery is a must have--something I'd hope to get from an Enterprise edition feature.
Upvotes: 3<=-=Sep 9 2009 9:24AM=-=>
Thank you for filing this issue. We will consider it as a new feature for a future version of Reporting Services.
I very much appreciate you taking the time to offer suggestions for how to improve Reporting Services.
Thanks, I’ll look forward to this being addressed! As for workarounds, I’m already aware of the text log, but unfortunately to get the information we need we needed to turn on verbose logging, which produced such a large logfile it was impractical—multiple GB in our case per day. I was able to just turn on verbose logging for just the affected component, but that was still impractical. There may be a bug where even though we have our configuration is set to log errors (the default), some errors are being filtered out inadvertently like the delivery errors.
Thanks Greg! Can you file a new bug on the errors that missing from the error level. An example of the log lines you expected to see in the trace file by default would be very much appreciated. I know opening a new bug on that limited case may seem like it is just accounting, but it will help us as we triage issues – more constrained issues are more likely to be fixed than broader ones.
Thanks! I submitted the delivery error issue as this new bug report:
Thank you for filing this issue. There are several parts to your issue. The missing log entries, we believe we have addressed in SQL Server 2008 R2 (available first half 2010). However there is a second part to the issue related to storing parameter combinations that are filing. We will keep this issue open as a potential design change to make it easier to know which parameter combinations are causing report subscriptions to fail.