Post reply

Subscriptions have stopped working

  • May 23, 2007 at 12:14 pm

    #172520

    We have several in-house generated management reports based on our trouble-ticket system. The support manager is making changes to the ticket system thata also changes the underlying database, to the point that she recently broke the reports. It was easy to fix the reports and procs that populate them. Yesterday, I re-deployed the project to the SQL and SSRS servers, and everything worked fine - we could all run the reports manually, but ...

    The scheduled subscriptions are no longer running. The Subscription Management screen shows the last run at 8:00am yesterday, when all the reports failed. I created test subscriptions, against the newly deployed reports, but they didnt run either.

    All of the SQL Agent jobs that run for the subscriptions ran when they were supposed to, but the subscriptions themselves never ran. Does anyone have any ideas what happened?

    TIA for your help...

  • May 24, 2007 at 8:10 am

    #708661

    Apparently, one of our Network Admins was making changes on the box and broke SSRS, once he fixed his errors everything started to work again.

    However, if anyone knows the mechanism of running timed subscriptions, I'd really like to hear from you. What I've got so far is :

    (1) Create the Timed Subscription;

    (2) A SQL Agent job is created on the supporting SQL Server;

    (3) The job runs at the scheduled time to insert a record into the [Event] table in the [ReportServer] database (this was as far as we were getting before the errors on our web farm were fixed);

    (4) Then a miracle happens and reports magically appear in the inboxes of various people, I think 

  • July 31, 2007 at 8:31 am

    #723601

    I know this is a bit late but I ran across this as I was researching another SSRS issue.

    Another reason subscriptions will stop running, which bit us a few times,  is if they were originally configured ('owned') up by a specfic individual whose network (active directory) account is no longer valid.  At execution time the SSRS subscription engine validates the subscription's owner ID against A\D and if it is not valid the process stops and the only clue is in the SQL server execution logs.  Best to set up subscriptions under a non-expiring service account.


    maddog

Viewing 3 posts - 1 through 2 (of 2 total)

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