Comments on: Re-running SSRS subscription jobs that have failed

By: Joseph Arechiga

Joseph Arechiga — Mon, 17 Oct 2016 07:09:49 +0000

So simple!!! Thanks!!! I used to change the time on each subscription. Oyyyy.

By: Vishnu Menon

Vishnu Menon — Thu, 17 Mar 2016 20:49:09 +0000

Great article.. informative and very useful! Thanks!

By: Rob Farley

Rob Farley — Tue, 29 Dec 2015 06:34:49 +0000

Sankar – this is what you are trying to do? SSRS doesn’t do multiple attachments like that. I would suggest using the web services and constructing an email yourself in .Net code.

By: Sankar

Sankar — Tue, 29 Dec 2015 04:36:56 +0000

i got a situation like different parameter for same one report subscription in ssrs Email subscription but same recipient address, which means all diff. parameter attachments in One Email because same recipient name. can any one help me on this.
thanks
sankar

By: joe

joe — Wed, 21 Jan 2015 20:56:10 +0000

the addevent procedure will always return positive (and immediately), which doesn't make it easy for error handling. if instead you would call a thing that waits for the report completion and throws errors, then you can start exception handling. having tried all this out at the places i worked, i'd recommend anyone who has a lot of emailing going on to avoid the subscriptions and go for the web services. maybe it's a bit unusual at the beginning but it makes the processes clean, with errors handled or thrown, and the subscriptions managed centrally. i built this tool but there are others. http://busyreports.codeplex.com/. you can also start from the MSDN documentation which has good examples on running reports.

By: Rob Farley

Rob Farley — Sat, 11 Oct 2014 00:20:04 +0000

Excellent work!

By: Kieth Stewart

Kieth Stewart — Fri, 10 Oct 2014 17:44:44 +0000

OK,
It took me a while and a lot of resources, but I eventually figured it out on my own.
We use forced error as a way to stop a subscription from firing if the report is empty, usually, if it is empty, that means there was some sort of data integrity issue that needs to be sorted out, then we have to run the subscription.
I built a little application that makes this user friendly, but here is the jest of what it does:
1) Get the list of subscriptions from the Reporting Database
Select SubscriptionID, EventType from Subscriptions
This will give you the data needed to fire the event. Important.
2) Fire the ‘AddEvent’ Stored procedure from the same database using the
SubscriptionID and EventType as the parameters.
3) The SQL Job will pick up the new event from the table and fire the
subscription then delete the entry from the table.
You can see how it is easy to put an interface around this. It works very well and there is not a whole lot to it. I put in some other features, like being able to stop or start the subscription and what not.

By: Donovan

Donovan — Wed, 27 Aug 2014 16:00:47 +0000

Yea, we do have everything backed up from time to time.
I am going to use this code now to identify which reports have still failed after 12pm:
SELECT s.Description ,
s.laststatus ,
c.Path ,
c.Name ,
LastRunTime ,
ScheduleID
FROM ReportServer.dbo.subscriptions s WITH ( NOLOCK )
JOIN ReportServer.dbo.Users u WITH ( NOLOCK ) ON s.ownerid = u.userid
JOIN ReportServer.dbo.catalog c WITH ( NOLOCK ) ON s.report_oid = c.itemid
JOIN ReportServer.dbo.ReportSchedule rs WITH ( NOLOCK ) ON rs.SubscriptionID = s.SubscriptionID
WHERE (( ( s.laststatus LIKE ( ‘Done: %’ )
AND s.laststatus NOT LIKE ( ‘% 0 errors.’ )
)
OR s.laststatus LIKE ( ‘Failure%’ )
)
OR s.laststatus LIKE ‘%not valid%’)
AND DATEPART(HOUR,LastRunTime) >= 12
AND DATEPART(DAY,LastRunTime) > DATEPART(DAY,GETDATE()-1)
Most of our reports are sent out by 10:30AM, so if they are still failing after 12PM, there is a problem.
I can then extract those email addresses and send them a fail notification and let the admins know so they can fix the reports.
Thanks again for your initial code Rob – It has really helped me.

By: Rob Farley

Rob Farley — Wed, 27 Aug 2014 15:42:47 +0000

You’d have to give the jobs a bit of time to run. Why not have a third job which queries the status again, but instead of generating start statements, try having send_dbmail?

By: Donovan

Donovan — Wed, 27 Aug 2014 14:46:15 +0000

Thanks Rob, I have actually started that already.
A more complex idea that I have though is to rerun the reports only once, and then, if it still fails, to send an email notification to the reporting services team as well as the recipients of the reports.
Any ideas?