I recently upgraded my SSRS site from 2014 to 2019. No issues upgrading, but one annoying thing is happening; every report is taking an extra 10-20 seconds to start the display process, and it happens every time. When I click on a report, the "loading" box appears for 10-20 seconds. Then the "loading" box changes fonts and then the report renders. In the case where the report has parameters for the user to fill in before rendering the same thing happens before the user can fill in the parameters. I haven't found any errors in the logs, but once thing I noticed is that the messages in the logs are recording this extra time, like this example (note the 14 second time lapse in the messages):
library!ReportServer_0-31!df0!07/07/2020-09:30:22:: i INFO: Call to GetItemTypeAction(/CWDS Developer Prod Database Tools/CWDS Mirror Database Last Refresh Dates). User: CWOPA\c-sthenry.
library!ReportServer_0-31!19a8!07/07/2020-09:30:22:: i INFO: Entering StreamRequestHandler.ExecuteCommand - Command = StyleSheet
library!ReportServer_0-31!19a8!07/07/2020-09:30:22:: i INFO: Exiting StreamRequestHandler.ExecuteCommand - Command = StyleSheet (success)
library!ReportServer_0-31!1d8c!07/07/2020-09:30:36:: i INFO: Call to GetItemTypeAction(/CWDS Developer Prod Database Tools/CWDS Mirror Database Last Refresh Dates). User: CWOPA\c-sthenry.
library!ReportServer_0-31!1d8c!07/07/2020-09:30:36:: i INFO: RenderForNewSession('/CWDS Developer Prod Database Tools/CWDS Mirror Database Last Refresh Dates')
dataextension!ReportServer_0-31!1efc!07/07/2020-09:30:36:: i INFO: Opening SqlConnection with ClientConnectionId 621b8f6862a748f2b3304e97e827e4c8
I suspect an issue with the SSRS 2019 install, but I can't find anything wrong; any ideas?
So...after much research, we found that the reports are sending out a request to this site: az416426.vo.msecnd.net.
This is an MS "insights" website. Anyway, I followed the instructions in the link below (on our SSRS server) to disable those customer insights calls in the registry, and now our reports are rendering at a normal speed.
https://learn.microsoft.com/en-us/answers/questions/87904/ssrs-2017-reports-loading-slow-on-first-time.html
Related
i have created SSRS reports and Query which i am using in particular SSRS report is fetching data immediately.when i try to run any report first time it is taking more time when i run the same report 2nd or 3 rd time it is loading immediately and when i run same report for the first time in report builder it is loading immediately and when i open same report with system which is having internet connection it is loading immediately and when i try to open same report with LAN/Intranet connection it is routing to az416426.vo.msecnd.net. once az416426.vo.msecnd.net link is time out then it routing to my SSRS report and loading the data.How to stop routing to az416426.vo.msecnd.net and how to fix it.is there any thing i need to add in settings or anything wrong with my SSRS reports.with inetrnet connection report is loading in 5-10 seconds and same report with Intranet it is taking 40-50 seconds.I read in some of the articles we need to change Recycletime in rsreportserver.config file. i tried this option as well but it didn't worked for me. please suggest me how to fix this issue.
Thanks & Regards,
Venkateswara rao
I'm seeing a bizarre issue that is occurring daily when trying to run a report via the SSRS portal. Upon clicking the report, the entire screen grays out and pops up a Loading notification, which never advances. This is not the Loading message you get when running the report. The process never gets to the report screen (no report menu items, etc.). There are no errors in the log files, and the report execution is not attempted (nothing in the execution log in the ReportServer database for these reports). I've tried setting the recycle time to several days out then restarted the service, but the issue recurred the next day, even within less than the 12 hours of the default setting. The only thing that clears the issue is a restart of the Reporting Services service. This seems to work the rest of the day, but the following morning, ad hoc reports won't run. All scheduled reports are running successfully so this appears to be an issue with the portal. When this occurs, the same loading screen appears when trying to view subscriptions. All other functions on the portal seem to work.
Environment is as follows:
2 servers (1 RDBMS, 1 SSRS)
SQL Server 2016 (13.0.4260 for SSRS)
SQL Server 2016 (13.0.4466.4 for RDBMS)
Windows Server 2012 R2
We recently upgraded our SQL server to 2016 and I turned on QueryStore to do the analysis that it provides. I'm encountering a problem where, even if the time period of the report is Last hour, it will generate a message that says "Couldn't connect to database" even when running it on the database server itself. Sometimes if I keep refreshing the report it will eventually display some data, but it's intermittent at best. I'm running SSMS 17.5 on a sql server 2016 server.
We are having a somewhat similar issue with another program that connects to the database where it will sometimes not be able to connect, but every time I run my queries in SSMS, run reports in SSRS, or even use activity monitor, I never see any connection drops, so I'm not sure if it is related.
Thank you in advance for any help!
I find it works fine with the statistic set to Avg, StdDev, or Total. Max and Min give the error.
I found this happens when the query store runs out of space and gets into cleanup mode.
In database properties in SSMS try playing around with Query Store settings: for how many days it stores the query stats and does it get into "size cleanup" mode. More info on how to keep it adjusted: https://learn.microsoft.com/en-us/sql/relational-databases/performance/best-practice-with-the-query-store?view=sql-server-ver15#Configure
I know similar questions have been asked before...
I am using SQL server 2005, with SSRS 2005 installed on the same box. (aka. production DB, Report DB/TempDB, Database engine, and SSRS all in the same box).
We have about 200 reports deployed in the box.
SSRS/DB is running on a W2k3 64-bit VM.
Now the problem...
Occasionally almost on a daily basis our users get the 'operation timeout' error (error in XML document....). At first I thought it was a report size problem, but then when I try the Report Manager URL (http://<>/reports), nothing appears on the browser. The only thing I can do is to recycle the Report server IIS pool and it will work again. Everytime when the 'operation timeout' happens, the Report Manager URL will not work, and I can't find any logs in IIS to indicate there's a problem.
I researched on the net and found that some people have put a dummy report as part of the SQL server agent job which runs every 10 minutes from 9-5 to 'warm up' the SSRS. The dummy report made a small connection to the DB on one row from a very small table. The operation timeout problem seems to have disappeared for 95% of time, but it still happens. Strange enough, when the operation timeout problem happens, I notice the dummy report job has also stopped working. In this case, I had to recycle the IIS pool, and start the SQL server job again, and then SSRS will work again (until the same problem happens next time)
The error I got from the SQL server job is:
System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host
However I am totally confused by how the IIS issue on the report server somehow affects the SSRS job. Maybe I am on the wrong track but that's bizzare.
My observation so far is if it takes forever for the Report Manager URL (http://<>/reports) to appear it is a bad sign that something has gone terribly wrong on SSRS.
I have also added a new task which call the SSRS Report Manager http://<>/reports URL using PowerShell in order to 'warm-up' the IIS but it does not seem to make much difference.
Can someone point me to the right direction? Thanks. WM
In the past, after much research, I've found memory allocation for SSRS to be the root of many issues. You can try this.
Add the following into the <Service> node in the rsreportserver.config file
<WorkingSetMaximum>4000000</WorkingSetMaximum>
The file is typically in c:\program files\Microsoft SQL Server\MSRS11.iMIS\Reporting Services\ReportServer
This sets the maximum memory available for the report which also set the minimum memory to 60% of the maximum.
https://msdn.microsoft.com/en-us/library/ms159206(v=sql.110).aspx
I've installed a SQL Reporting server (2008 R2), with some reports. But I've some performances issues.
The first call of the day to the server(going on the report interface by example), is VERY slow(something like 30-45seconds at best).
The report generation is then "fast"(1-2 seconds).
The next calls to the server are always fasts until the next day. I've the impression that it loads a lot of thing in the memory. But what can takes 30-45 seconds to be loaded in memory??? And how to load it only once?
The server is good enough(quad core, 8GB of ram, never near its capacity for now).
What is the problem? How can I resolve this ?
Thoses reports will be launched only 4-5 times in a week, so they will always be slow if I can't change this. And since it's available for customer, I just can't make them understand this(and the report is called through a website, so I risk to have timeout).
Thank you very much
It seems to be an SSRS issue. There is nothing wrong with your report.
It's "normal" that SSRS takes more time to load the first time you access it after a long time of inactivity. The issue is caused by the way how SSRS works and SSRS regularly restarts application domain after a specific time period. After the application domain is restarted, then upon first request to the SSRS it needs to load all the settings and it takes quite a long time.
This blog show's a workaround for the situation
Here is the powershell script that I wrote to fix the problem. It is setup as a task to run every 1:00am:
Stop-Service "SQL Server Reporting Services (MSSQLSERVER)"
Start-Service "SQL Server Reporting Services (MSSQLSERVER)"
$wc = New-Object system.net.webClient
$cred = [System.Net.CredentialCache]::DefaultNetworkCredentials
$wc.Credentials = $cred
$src = $wc.DownloadString("http://localhost/Reports/Pages/Report.aspx?ItemPath=***NAME OF HOME PAGE***")
The best solution I could come up with was to issue a 'curl' command to the http page of the report using via windows batch command in a windows service. This ran up the page(s) every morning before the users came in.
Don't have access to the code anymore (job was a while ago) but this question shows how to use curl:
http://blogs.plexibus.com/2009/01/15/rest-esting-with-curl/
As Diego said, SSRS has some issues. The first call it is slow, regarding your server configuration. I recommend you the following config to add in rsreportserver.config (located if you don't know in C:\Program Files\Microsoft SQL Server\MSRS10.MSSQLSERVER\Reporting Services\ReportServer\ )
If you want to increase the max memory used by SSRS: (which means 7 GB)
<WorkingSetMaximum>7000000</WorkingSetMaximum>
If you want to improve the first call, you can set (in minutes)
<RecycleTime>4320</RecycleTime>
Actually SSRS has a reset (recycle) time in which cleans its buffer. By default its setted at 720 min (12h) so thats why if you open a report every morning it actually load very slow.
As you need you can set the recycle time higher (2-3 days). I don't recommend a higher time because the buffer will fill up and you will get only blank pages, so you will have to manually restart Reporting Services.
It may be completely unrelated to SQL Server. Try to see if is not the code sign revocation list check issue, see Fix slow application startup due to code sign validation
I converted the main query and the dropdown controls on the page to load from stored procedures, it made a difference of say 5 sec in the loading process.Avoid using any inline queries.