Post reply

find cause for subscription fail

  • September 30, 2010 at 10:54 am

    #228922

    Hi,

    How are you?

    I have created data driven file share subscription for some reports. It directly delivers reports to clients. Subscriptions are failing some times. Clients are coming back to us for reports. Is there any way to find cause for subscription fail? Is there any way to send alert to my email when data driven file share subscription fails?

    Thank you for your help,

    BMR

  • September 30, 2010 at 11:08 am

    #1229748

    If you check the Status on the My Subscriptions page it will sometimes give you information about a failure. But it only tells you about the last event, if it has run successfully since the failure you won't see anything helpful. You may be able to check in the Windows event logs for more details.

  • October 1, 2010 at 1:34 pm

    #1230479

    Thanks for reply

  • October 4, 2010 at 1:19 pm

    #1231229

    Try looking in the log folder here: C:\Program Files\Microsoft SQL Server\MSRS10.MSSQLSERVER\Reporting Services\LogFiles. There should be complete information there about what went wrong.

    As for notification, RS is not proactive when it comes to telling you a report failed. You could check the SQL Server Agent job history for whatever schedule is tied to the report, but that will only tell you if the schedule failed. More informative is the ExecutionLogStorage table in the ReportServer database. You can set something up to check for records where Status != 'rsSuccess'.

  • October 4, 2010 at 2:47 pm

    #1231294

    Doug Lane (10/4/2010)

    Try looking in the log folder here: C:\Program Files\Microsoft SQL Server\MSRS10.MSSQLSERVER\Reporting Services\LogFiles. There should be complete information there about what went wrong.

    This is by far the most info you can find about it. Probably the only info that will actually point you toward the actual problem actually...

    As for notification, RS is not proactive when it comes to telling you a report failed. You could check the SQL Server Agent job history for whatever schedule is tied to the report, but that will only tell you if the schedule failed. More informative is the ExecutionLogStorage table in the ReportServer database. You can set something up to check for records where Status != 'rsSuccess'.

    Alternatively, you can use the ExecutionLog2 View that puts the ExecutionLogStorage table in a much more readable format.

  • October 4, 2010 at 8:47 pm

    #1231430

    Thank you all for valuable information,

    BMR

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply