The first month, the report was embedded as planned.
The second month, the wrong report was sent. The PDF that was generated in the prior month was resent, not a new instance of a PDF based on the current data. The emailed link to the report on the server worked fine, and the history shows that the snapshot was recorded at the appropriate time?
Wa happen? Why would it embed the prior/old instance of the report?Hi there, I'm trying to recreate this problem so I can try and figure it out but I need a little bit more info.
When you say you have set it to record a snapshot every time the report is run do you mean that it records a snapshot on the same schedule as the subscription?|||Specifically, on the History Properties of the report, I have the following options selected:
Allow history to be created manually.
Store all report execution snapshots in history.
Use the following schedule to add snapshots to report history
Shared Schedule: MonthEndProcessing-At 2:00 AM on day(s) 1 of every month starting 6/3/2005.
Keep an unlimited number of snapshots in report history.
On the Execution Properties, I have the following options selected:
Render this report from an execution snapshot
Use the following schedule to create execution snapshots:
Shared Schedule: MonthEndProcessing-At 2:00 AM on day(s) 1 of every month starting 6/3/2005.
Report Execution Timeout: Use default setting
On the Subscription Processing options:
Delivered by: Report Server E-Mail
Include Report Render Format: Acrobat (PDF) file
Run the subscription:
On a shared schedule: MonthEndProcessing-At 2:00 AM on day(s) 1 of every month|||I've not had time to try and test this theory but I believe it may be somethig to do with the time it takes to process the report.
I think what may be happening is that when the schedule kicks in and starts to generate the report the subscription doesn't wait for the report to be completed because of the time it takes to generate it so it sends the last generated report.
It was probably fine for the first report because by default when you create a snapshot schedule it automatically creates a snapshot when you apply the settings but when it was run the next time it sent the first report while the second was being generated.
If this is the problem you should be able to fix it by creating a schedule that runs before the subscriptions to generate the report so it is ready when the subscription schedule kicks in.|||
This is the behavior I am experiencing with large reports, and it is getting me burned!
The "Render the report with most recent data" switch does nothing in this case, as in our environment all reports run with most recent data and snapshots are not useful.
So for all my monthly and weelky reports I have to schedule a snapshot (with a limit history of 1) a fixed time (10minutes?, 1 hour?) on the report history page before building the subscription separately to send them?
If Render most recent is on, the sub should wait for the report to finish, before sending.
THIS IS A BUG. No matter how it's sliced.
