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
Related
We have a report in Microsoft CRM 8.2 on premise that goes into a timeout after 60s - report cannot be displayed error and "Data retrieval failed for the SubReport1" in the SSRS logs.
This report was running on CRM 2015 without any issues - the problem occured after the upgrade.
The report is running in report server as well as in report builder without any issues, it is also running in CRM but with records that the processing is done under 60s.
I changed all the necessary settings refered to other posts regarding timeouts but the issue persists.
Any ideas would be greatly appreciated.
PS. report is using SPs and it is a subreport with no shared datasets - I also tried running the parent report separately without issues, so I guess the issue is with the subreport.
modified web.config of CRM, modified the rsreportserver.config, modified reporting services site settings, even modified the registry (OLEDBTimeout, ExtendedTimeout) values.
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
I'm using SSRS (SQL Server reporting services) to display reports, my datasource is Snowflake
I have installed the ODBC snowflake driver and configured it properly
Click here to view the ODBC configuration
I have created a shared datasource on the SSRS server (via Report manager) and put in my own credentials and the connection works fine
Click here to view the connection on the SSRS Server
I'm able to build the SSRS report without any issues, when I run the report, everything works fine, I can publish the report on the server and the report renders perfectly fine on the browser
The issue is when i go back to the report the next day, i'm presented with an error:
An error has occurred during report processing. (rsProcessingAborted)
Query execution failed for dataset
'insert_name_of_my_dataset_here'. (rsErrorExecutingCommand)
ERROR [57P03] No active warehouse selected in the current session.
Select an active warehouse with the 'use warehouse' command.
So, this also means that the following doesn't work neither:
Subscriptions
Cache refresh
Snapshots
The only thing that works is if I open my report in SSRS Report builder, I right-click EACH of my datasets ("each" is very important, it doesn't work if i don't do all of them), I run the queries manually for each of them, and then the "connection" or "session" is "re-activated" and the report runs fine, both locally AND on the server...note i do not have to re-publish the report on the server for it to run
Click here to view screenshots of my process
Steps I have taken to addresss the issue (that didn't yield any resolution):
I have tried putting the "use warehouse WAREHOUSE_NAME;" command before each dataset's SQL script, but Snowflake's API doesn't allow multiple SQL commands to be sent, so I already saw that this functionality was in the development pipeline for Snowflake and found this link: https://github.com/snowflakedb/snowflake-connector-net/issues/33 - this work was started in 2018 and the last update dates from Apr 2019 that says they are starting to address the JDBC driver...no mention for the ODBC driver yet
I have set the snowflake parameter client-session-keep-alive to true (https://docs.snowflake.com/en/sql-reference/parameters.html#client-session-keep-alive), but according to the community portal: A similar "keep alive" parameter is not currently available for the ODBC driver. Instead, you could issue a dummy query every few hours to keep the connection alive. (https://community.snowflake.com/s/article/faq-how-long-can-my-jdbcodbc-connection-remain-idle)
List item
I have tried to create a cache refresh plan or a snapshot schedule that creates a snapshot or caches the report every 3 hours, and it works for the first schedule, but fails with the error for the other ones
The only thing I didn't try is to have snowflake never close the connection and keep the warehouse in the "started" state indefinitely...but this would increase my cost, and i'm pretty sure it won't work since the session would end anyways after 4 hours...
Any assistance is welcome!
Thanks
Specs:
SSRS 2014
Snowflake X-small
ODBC-64 bit driver, installed from the
snowflake driver repository (tested with 32-bit also, but 64-bit is
the one that is visible to SSRS)
I faced the same kind of issue and fixed adding the corresponding role with the data warehouse.
In the data warehouse add role with USAGE.
Could it be related with the data warehouse name (in the ODBC settings)? Is there a typo? COSNUMER_WH or CONSUMER_WH?
I strongly recommend setting default "context" configurations for situations like this, setting default role, warehouse, database, and schema with commands such as this:
ALTER USER xyz SET DEFAULT_WAREHOUSE = 'WH_NAME_HERE' ;
https://docs.snowflake.com/en/sql-reference/sql/alter-user.html
I have some reports deployed by SSRS 2016. They were working perfectly until yesterday. Now There is only one user can use them and the other can just see the reports name. If the other users try to run the reports it is going to stuck in loading stage and nothing more happens. I took a look at SQL Server profiler, the only time that report sends the query to the database is when that specific user runs the reports.
All the users are in the same domain.
Let me know if you need more info. Thanks.
It's fixed by changing Service Account setting (from Network Service to domain user) in Reporting Services Configuration Manager.
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