I have a huge report which works fine when I browse through report viewer. I have created a subscription so I can run this in the background. The subscription works if it's the only subscription running. If I run 2 subscriptions starting at the same time and pointing to the same report, the thread is aborted for one subscription and the other one works.
I have tried all suggestions with the configuration keys in rsreportserver.config, but no luck.
Yes, it was the resources issue. it's to do with the RAM. If it takes up to 90% then SSRS restarts, hence losing the thread.
The issue for me was a timeout setting. In the report portal in the Report Properties management page the default settings is "Use the system default setting". I changed this to "Allow report to run for 3600 seconds before timing out", and then the report completed successfully. I believe the default setting is 1800 seconds(30 minutes) so changing to 3600 seconds (60 minutes) give the report enough time to complete.
Related
I'm working with MS Reporting Services 2016. I noticed that the application domain is set by default to recycle every 12 hours. Now the impact on users after a recycle is either slow response from reporting services or a failed report. Both disappear after a refresh of the report, but this is not ideal.
I have come across a SO answer where people suggest that you can turn off the scheduled recycle by setting the configuration attribute RecycleTime to zero.
I have also read that writing a script to manually restart reporting services, which also recycles the app domain. Then a script that simply loads a report at a controlled time to remove the first time load issues. However this all seems like a work around to me and I would rather not have to do this.
My concern is that there must be a logical reason for having the scheduled recycle time, but I cannot find any information explaining this. Does anyone know if there is a negative impact from turning off the scheduled application domain recycle?
The RecycleTime is a function aimed at making sure SSRS isn't consuming RAM it doesn't need and potentially starving the rest of the machine. Disabling the refresh essentially removes the ability to claw back any memory used for a brief period of intensive processing.
If you are confident your machine is suitably resourced you can turn the refresh off or, if not, alternatively schedule the refresh for an out of hours time and define a Cache Refresh Plan to cache any super important reports immediately afterwards to minimise any user impact.
Further reading here: https://www.mssqltips.com/sqlservertip/2735/prevent-sql-server-reporting-services-slow-startup/
I guess I'm possibly over simplifying this, but SSRS was designed to recycle every 12 hours (default) for a reason. If it ain't broke, don't fix it. In my case, I wanted to control when the recycle occurred. I execute a 1 line powershell script from a SQL Agent job at 6:50 am, then generate a subscription report at 7 am, which kick starts SSRS and the users do not see any performance degradation.
restart-service 'ReportServer'
Leaving the SSRS config file setting at 720 minutes lets the recycle occur again at 6:50 pm. Subscription reports generate throughout the night, so if a human gets on SSRS after hours there should be no performance issue because the system is already running.
Are we possibly overthinking it?
We have couple of long running reports in SSRS. It is rendering fine in ReportViewer. When we try to export to PDF, it times out after some time. We increased httprequesttimeout in ReportServer Web.config and it works fine in Offshore. Our onshore environment is a shared one and the client is not inclined to change setting in shared environment. We have tried changing invidual reports time out properties(Do not time out and also Manually given the time out to some big number). Unfortunately it seems to be overridden by reportserver web.config entry httprequesttimeout which is 2 minutes by default.
Is there a way to override individual report's timeout settings instead of changing Reportserver web.config
Regards
K.P.Kannan
Maybe it's about execution time-out value. I've found something on Microsoft, hope it helps.
How report execution time-out values are evaluated
The report server evaluates running jobs at 60 second intervals. At
each 60 second interval, the report server compares actual process
time against the report execution time-out value. If the processing
time for a report exceeds the report execution time-out value, report
processing will stop.
Note that if you specify a time-out value that is smaller than 60
seconds, the report may execute in full if processing starts and
completes during the quiet part of the cycle when the report server is
not evaluating running jobs. For example, if you set a time-out value
of 10 seconds for a report that takes 20 seconds to run, the report
will process in full if report execution starts early in the 60 second
cycle.
Here is the link for details:
https://learn.microsoft.com/en-us/sql/reporting-services/report-server/setting-time-out-values-for-report-and-shared-dataset-processing-ssrs?view=sql-server-2017
I have SSRS line graph which is to be auto refreshed every minute. I takes a long time to refresh and shows loading icon until it is refreshed and the graph becomes blurred.
How to reduce the refreshing time and how to refresh the report in background and not to show the loading icon?
Reducing the report refresh time
In most examples, the bulk of the time taken to refresh a report will be due to the dataset queries running. Therefore you should start by looking at those queries and investigating how they can be optimised to execute as fast as possible. As noted in the comments there are options to cache reports for performance, but given your requirement to refresh the report every minute I am assuming you will want the latest data, not a cached version.
Refreshing the report "in the background"
As far as I am aware, this is not possible.
It would seem a snapshot would be the way to go. You can set up Snapshots under the Processing Options tab when managing the report. With a snapshot, SSRS runs all the queries behind the scenes at a set interval or schedule. Then, when the user accesses a report, the only loading time is for the presentation layer.
That said, if a user tries to access a report while SSRS is running a snapshot, then the user will wait until the snapshot is finished, and thus the loading screen will appear. I would recommend you follow Nathan's advice and work on query optimization.
I'm developing a report in ssrs for display in a public location within the company. The report shows up-to-the-minute data on department activity, so is set to refresh every 30 seconds or so.
The problem I'm running into is that once every few hours, the report throws an error (rsErrorReadingNextDataRow) & (rsProcessingAborted). All I have to do is hit refresh in the browser (rendered in a an internet browser) and it reruns and charts along happily for a while.
After looking at the reportserver execution log, it appears that these errors coincide with a phenominal spike in processing time. On average, each time the report refreshes, processing times is 400ms~800ms, but when it spikes it goes to ~90000ms (yes, five zeroes) and then throws this error.
Being new to SSRS I am not sure where to begin looking for the root cause.
Can anyone give me pointers as to where I can start to find out what is causing the processing time to rocket like that? Data retrieval is stable at ~5000ms, and Time rendering is stable at around 200ms. It's only the processing that goes haywire.
Some background on the report and data:
Data is pretty straight forward. It's based on a view that pulls transactions from last 7 weeks. Number or records, therefore ebbs and flows each week ~ 8000 records. When select * from View is run in SSMS, query takes about 5 seconds to run. I'll work on speeding that up after I resolve this processing issue.
No parameters are used, though the view does use getdate() to figure out which records to show from base tables.
No stored procedures are used.
Report itself is comprised of 6 panes within a single tablix, none of which have to draw more than a few dozen marks ('cept one is a map of US states).
The report does have one feature that may be related, though I am not sure how. Report definition filters the dataset based on a mod 3 of the built in execution time variable, rotating the report to show "This Month", "This Week", or "Today" activity. There is an additional mod 3 on execution time which rotates visibility for the panes. The result is that each 30 seconds, a report with different combinations of charts shows up on a rotating time-frame.
Don't know if this could be a cause, but it's the only element of the report that makes it remotely fancy. Everything else about the report is actually rather straightforward/plain.
While I would love to identify and eliminate the spikes, even a mechanism to automatically refresh on error, or refresh on timeout (or something to that effect) would do the trick. I need to be able to launch the report in the morning and have it run unmanned all day without any human interaction, refreshing every 30 seconds for the duration of business hours.
Just a recap of the comments:
it might be possible to push the web page into a frame, then add javascript to the main page to periodically refresh the frame. It wouldn't fix the underlying problem, but it might help.
it might be worth looking at the performance monitoring tools in Sql Server - it might be a database issue (temp table filling up, etc)
You noted that adding a with (nolock) seemed to help locate the problem.
Had an interesting error today and couldn't find anything online about it so wondered if any of you guys had seen this behavior before.
We had an out of memory error and the CPU usage was spiking this morning on our reports server, a clean reboot seemed to rectify the issue, however since then all the email subscriptions have been sending multiple times. What do i mean by this, the subscription as far as SSRS is concerned ran once at its normal time (10am), this has been proven by scrutinizing the logs to see if another execution occurred (it didn't) and by renaming the SPROC that the report references to ensure that it would fail, yet it didn't and the mail resent. I then checked the Exchange queues and turned on logging for the connection and i could see a new mail being resubmitted every 30mins to the exchange mail queue.
The question is, what process is causing that mail to be resubmitted to the exchange server and how, other than another reboot do we stop the emails resending.
Thanks in advance
-- Further --
Having done more digging we have noticed that the [ReportServer].[dbo].Notifications table is populated with all of the reports that are sending out multiple times with the Attempts column incrementing every time the duplicate email is sent out.
We still dont know why these are resending
It seems to be down to the logging level... If you switch the Report Server Service logging level down to level 2 (Exceptions, restarts and warnings) this error seems to manifest itself however when the logging level is switched back up to 3 or above the error seems to disappear. Some similar behavior is noticed here: http://social.msdn.microsoft.com/Forums/en-NZ/sqlreportingservices/thread/b78bb6e2-0810-4afd-ba6b-8b09a243f349
Check the SQL Agent jobs (named with GUIDs) for the subscriptions. Maybe the schedule on those go messed up somehow.