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.
Related
I am pretty experienced in SSRS, I have been doing it for quite some time so I know when I see the error:
"An error has occurred during report processing. (rsProcessingAborted)
An attempt was made to set a data set parameter '#SiteId' that is not defined in this data set. (rsUnknownDataSetParameter)"
I know what causes this error and can fix it. However, this error randomly happens every so often. What I end up doing is simply rebuilding the project and redeploying it and all is well for a few days, then suddenly again this same error will pop up again.
I know there is no issue with the parameter as I have a #SiteId parameter as shown:
So when I get an email from a user that "The Report Is Down" I just go to my report and rebuild and republish and the error vanishes without ANY other changes. A few days later when they want to run the report again this same error happens. What is causing this issue to come back over and over. We are running SQL Server 2016 with SSRS. It happens to ANY one of my reports on the report server. Its not a specific project it randomly happens on any project.
EDIT
What I did notice does happen is when a user reports this issue I go to the "Manage" of a report on the report server url. This area is where you find the properties, data sources, and parameters. When I click parameters I see this error:
So obviously something is destroying the parameters - that is where I am confused what is causing that. This is probably why I am getting the error message. So to reiterate a report is published works...suddenly the parameters go missing. User reports "the report no longer works" I rebuild and redeploy the report...it then works again for a day or so maybe more than a day I never investigated how long it takes for it to break again (as these are not urgent reports). Days later user says report is dead again...if I go to the report server using the report server url and click "Manage" and then click "Parameters" for some reason the parameters have disappeared...causing me to yet again redeploy. This happens over and over and over. It never ends...
The short of it is you cannot have the same shared dataset name across different SSRS Projects that are on the same SSRS server.
So within our SSRS "repository" we have several different SSRS projects. Both projects are very specific to certain functionality. What I noticed is everytime I deployed one of these SSRS projects the reports on the other project would stop working.
When the email would come from the user stating Application A's reports werent working I'd go to Application A's SSRS project and redeploy it and it would fix the issue. Days later a different user said Application B's reports weren't working so I would redeploy application B's. Not knowing that when I deployed A's reports B's would break, and vice versa deploying B's broke A's.
Come to find out....both projects had a shared dataset with the SAME NAME (dsEmployees). Same name however these datasets pointed to different sprocs with different parameters. Well when you deploy and look at the back end db the Catalog table only has one entry for dsEmployees. Everytime I redeployed this would overwrite with the other dataset since the names were the same.
Lesson learned across different SSRS projects be careful with the shared dataset name, they must be different. I was able to spot the difference by running the following query:
SELECT
c.Name,
c2.*,
c2.Parameter
FROM
DataSets d
INNER JOIN
[Catalog] c
ON
c.ItemID = d.ItemID
INNER JOIN
[Catalog] c2
ON
c2.ItemID = d.LinkID
WHERE
--one specific report for now
d.ItemID='C3008EF4-E544-48F3-92C1-2222C6148B13'
When the report was stated not to work. Then I would redeploy the report and rerun that sql statement I wrote and dumped the rows to an excel sheet to compare. One of those columns is Parameters and I noticed the parameters were slightly different. Immediately I was onto something and this ended up being it. Thanks to comment posted it helped me relook at this! This has bugged me for years!
I'm writing you because I need some advice.
I'm working on SSRS reports and SQL Server 2012 during my internship for an enterprise. I wrote reports with interaction parameters, but some reports are very slow when someone wants to use/run them on SQL Server Reporting Services. As the enterprise uses Windows integrated security, I can't configure cached reports in order to improve execution time for reports with main (or default) parameters.
At the end, my goal is: if people who need to see reports can receive an email every Sunday for example, with a link for new reports... That could be awesome.
Could someone give me an advice please?
Thank you in advance.
You can schedule Reports on SSRS and send them in Excel format with default parameters. Just click on manage on the report and select subscriptions.
You can even select the emails from a query.
Check this for more info.
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?
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.