SSRS Data-Driven Subscription stuck in Processing State - reporting-services

I have configured a report with 14 Data-Driven Subscriptions that get executed every month. They aren't executed by schedule. They get executed by a tool who knows the SubscriptionIds.
Now I ran into the problem that all subscriptions changed to done except one subscription.
When I query the very subscription on the ReportServer DB in the ExecutionLogStorage, I can see that the Subscription got executed 6 times with the correct parameters.
Even if I manually rerun the subscription, I get 6 produced reports but the status doesn't change.
The subscriptions are data-driven because I query a Database View with dynamic information and based on the output, there are x Reports per Subscription that get sent to a recipient.
Do I have to re-create the subscription or is there a way to fix the Last Status of the subscription?

Related

How can we use a bot to check with SSRS if the reports ready to view in certain time intervals

How can we use a "bot" to check with SSRS if the reports are ready to view in certain period of time intervals. for example like every 3 minutes the bot will check with SSRS if the reports are ready. If the reports are ready the bot can send a message back to client saying the reports ready to view.
Thanks
I am not entirely sure why you want to do this, but you can track every execution of every report in SSRS via the ReportServer database. You can have a look through the database and roll your own script, though there is already a helpful view available called ExecutionLog3, which holds the report name, user that ran it, when, with which parameters set, the render type, execution failure/success, etc.

Configuring a SSRS Data Driven Subscription to run on multiple CRM records

I have a report that takes a single crm record as a parameter and I would like to configure a data-driven subscription for it such that each time this subscription runs it produces multiple PDF files, one for each record returned in the parameter query. I noticed that when the subscription runs it produces multiple PDFs, but only the first of the parameter results is used. Is there a workaround for this behavior?

SQL Server Agent Job for SSRS subscription loses schedule config

We have a series of subscriptions on SSRS that email out reports in Excel format every 30 minutes. I have edited these via SQL Server Agent in Management Studio so the schedule only runs between certain times on weekdays only - as I don't believe this is possible via SSRS.
One particular subscription, a couple of times a day, reverts back to running once per week at 8:00 on Mondays. I then have to edit the schedule again. No errors occur and it does work for a few hours at a time.
I imagine it's related to me editing the schedule via the 'back-end' but all the other similar subscriptions where I have done the same work fine.
Can anybody suggest where I should be looking to investigate this? What other detail would be useful to help to resolve this issue?

SSRS - Recovering report on smtp failure

Shortly, is it possible to recover the report that was generated by SSRS when SMTP fails?
Sometimes we have network problems with SMTP and even the report was generated it couldn't be sent. We can send them manually later, but the problem is that most reports needs to be generated at a specific time, otherwise data my not be correct (for example, end of day reports needs to be generated at 12:00am, otherwise some updated numbers may not be correct. But we want to resend the report generated at 12:00am when we come to work in the morning)
I considered sending these reports though snapshots but some report subscriptions have parameters, and I couldn't find how to take snapshot for each subscription.
Any ideas?
Thanks in advance,
Onur
You could capture the data each day at 12am using a sql agent job which executes a stored procedure to populate a table/tables with the data.
If this is a report which can also be run live, you would run the report based on a hidden parameter #extract_type indicating whether or not this is live or snapshot. The default would be "live" and the subscription would pass "snapshot" for this parameter. The code in each dataset would filter based on #extract_type, perhaps through a view.
This way, the subscription could be re-run at any time of day with the same report results.
well, first you're not alone. i had issues with smtp errors in all places i worked.
there is a LastStatus column in [dbo].[Subscriptions] table. you can make a job that runs every few minutes, checks this table and restarts all subscriptions which have smtp errors.
like SQLDiver, i think it's a good idea to store the data behind reports in a table. it's not a job for a reporting tool to store your data.

Reporting Services Subscription fails but manually running report works

Our company has a huge nasty report that takes about 50-60 minutes to run (it's for a university and lists all sorts of payment information for all students registered in courses). While it has been running each morning at 5am as a subscription, it recently stopped working and displays "An error has occurred during report processing." in the properties window for the subscription.
If I manually run the report from inside Visual Studio it will work every time, but the subscription will now always fail. I had our DBA turn on trace logging and it gave us no helpful information whatsoever. I've also set the subscription to run at different times throughout the day, with no success. The report is supposed to put an Excel file on a file share and it works for the other 5 subscriptions to this report (I have 6 subscriptions, only 1 of the 6 has a parameter set that returns values from a larger dataset). So this means that it has permission to write to the file share. Any ideas?
Could it be trying to write more than 65536 rows to the Excel file? If so it will just fail.
Also you might check the configuration for IIS to see if the report is causing a timeout.