SSRS 2005 uses a Agent for the schedules of reports subscriptions. For each subscription there is one Job (it's name is GUID of the schedule) created and scheduled and this job simply inserts an event in the reporting services database which is periodically checked by the SSRS service process.
Unfortunatelly, when you delete this job by mistake, then you will not be able do delete particular schedule using the management studio or reporting services pages.
The problem is caused by a trigger
This trigger simply tries to delete a job using
The original trigger looks like:
Shouldn't be there a check for the existence of the trigger?
I have encountered the problem when moving the SSRS database from one SQL server instnce to another as on the new instance you do not have the jobs for schedules stred in the SSRS database. Solved the issue by adding the check.
The same code and the same problem exists not only in SSRS 2005 but also 2008 (didn't checked 2000). Do you think it is a bug in the reporting services?
It looks like a bug to me - apparently they just didn't think of that use case. I would report it via connect.
answered Dec 18, 2009 at 04:38 PM
Matt Whitfield ♦♦