I have a report subscription that throws an error when trying to view so I can't disable it, I have disabled it from the My Subscriptions screen on Report Manager but it is still being delivered.
I am thinking of disabling it from the reporting database, as it shows it is still running.
Has anyone done this or know how best to do this?
Related
For some reason our SSRS schedules appear to have stopped running over the weekend.
I checked the schedules on our SSRS portal, these appear to have disappeared "There are no items to show in this view". I get the same under my subscriptions, too.
The agent jobs appear to be running, but not emailing reports. When I check the Subscriptions on SSMS, it has run dates for today but no emails.
I have sysadmin and full rights to the server and the SSRS portal.
Anyone come across this issue? I've been searching google all morning to no avail.
Thanks,
Russ
Resolved
Our SSRS dba had only place schedules onto reports locally - you can see this by clicking on the drop down arrow of the report, selecting manage, and then subscriptions from there.
The reason our reports weren't sending is because there was mail delivery had been suspended whilst IT carried out maintenance.
Thanks for your help in trying to get to the bottom of this.
We have an SSRS report that connects to an SSAS cube. The report and the Data Source (to the SSAS cube) had been deployed. Unfortunately, nobody could see the report (error: either the user does not have access to the DB or the DB does not exist).
After many changes to the datasource, I deleted the datasource and I received a rsInvalidDataSourceReference, which is correct. I then deleted the report.
Once I deleted both of them I cleared IE's cache. Then I redeployed both the report and the datasource, and went to the report's properties to make sure it was pointing to the correct datasource. I have not made any changes to the datasource so I should now get the user access error.
Unfortunately, I continue getting an rsInvalidDataSourceReference. I've done this many times (deleted & redeploying datasource and report) but still nothing.
What can the problem be? At the very least I should get denied connection error once again.
I have seen issues like this with no reason or solution.
The workaround was to manually set the datasource in Report Manager. :(
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/7f06e400-e803-4070-b272-4eb5d3d55efd/rsinvaliddatasourcereference-error?forum=sqlreportingservices
http://ok-sandbox.com/2013/12/ssrs-fix-rsinvaliddatasourcereference/
Our reports in SSRS stopped sending. The last report was sent 2 days ago, and was send successfully, but since then none of the reports are being sent.
If I look at the SSRS web page for each report, there is no error. Simply showing the last run time as 2 days ago, so seems it didn't even try send.
Yesterday we did make some changes. But only moving a database from the Express version, to the regular version. We did not do anything that would affect the SSRS metadata (or at least we don't think we did...)
Where should we start looking to see why the report subscriptions stopped? Is there a process that could have accidentally been disabled? Thank you!
The Report subscriptions are created as jobs for the SQL Agent. You should see a long list of jobs with GUIDs as the names. Make sure that the SQL agent jobs are running. Going through the Steps of the SQL Reporting Services Configuration tool will recreate these jobs if you were to move the Reporting Service installation to another server. (I don't recall which step recreates the subscriptions. Just go through each pane and click "Apply.")
Depending on how you move things, you may need to backup and restore encryption keys, and you can easily end up in a state where two copies of subscription exist and are executed ( on different servers.) But in your case, where you didn't move SSRS, I'd look at the SQL Agent properties on the original server (Express) to see that the SQL agent is enabled and running, and check the history of the SQL Agent jobs, to see if there are any problems.
I have a problem with Sql Server 2005 Reporting Server where people are receiving old versions of a report whenever the report is sent through a subscription.
I've added a date to the footer of the report, build and deployed it but subscribers still receive an older report.
I am not able to find any known issue or someone with a similar problem and could use some guidance on what to do.
Check Properties -> Execution. There are options there to have the report run based on a cached copy or from a snapshot. If these options are selected, the report will be run from older data in order to increase performance. Disable these to get the latest data.
I've created a Reporting Services report and set it to run on a subscription. (SQL Server 2005, if it makes a difference.)
Unfortunately, it looks like I've made some sort of error in the parameters, and it seems to have stalled, but it isn't actually failing, just sitting on "0 processed".
I want to cancel it to fix the error, but I can't figure out how. Stopping/restarting the services seems to make no difference.
What do I need to do to stop it?
A subscription is a SQL-Server Agent job, and is given a GUID as a title. Check the SQL-Server Agent job history, and if necessary stop the job.
If you have more than one subscription, check this link for a useful View on which jobs correspond to which subscription.
http://www.sqlservercentral.com/Forums/Topic254010-150-1.aspx