Report Server is not refreshing my report while Report manager is. Now I did have to alter the aspx files for both as the date parameters for my reports were showing in an American Date Format as per this website , http://geekswithblogs.net/naijacoder/archive/2008/06/26/123422.aspx
Any idea why this is happening ? Deleting the data sources, data sets and reports and redeploting does not work for Report Server either. Ahhhhh !
Related
Report 1 (Works): I have an SSRS package deployed to Server_A which pulls data in a database also from Server_A. The following URL works so I can download the report. http://Server_A/ReportServer?/SSRS_Package_Name_A/SSRS_RDL_Name_A&rs:Command=Render&rs:Format=EXCEL
Report 2 (Report Viewer Works, Direct URL Doesn't Work): I have a second SSRS package also deployed to Server_A, but it pulls data from a database that's on Server_B. If I use a similar URL, then SSRS displays the following error message in my browser:
Error during processing of ‘Reporting_Period’ report parameter. (rsReportParameterProcessingError)
The Reporting_Period parameter in SSRS references a column within a dataset that runs a query against a view in Server_B that pulls the min and max dates. Adding the Reporting_Year parameter to the URL didn't work, and it seems like I'm getting this error because the SSRS Server_A can't connect to Server_B.
Going to the report viewer in my browser and manually downloading the report works for both reports above. I just can't download the report automatically in the background by going to the URL for the 2nd report (Need to automatically download multiple reports using SSIS automatically).
Report 3 (Report Viewer & Direct URL Do Not Work): I then tested what was happening by first creating a new SSRS package with a simple textbox and deploying it to Server_A. Downloading the report in Report Viewer worked and using the direct URL worked. I then created a data connection to Server_B, and now the following error is displayed when attempting to view the report in Report Viewer:
An error has occurred during report processing. (rsProcessingAborted) Cannot create a connection to data source 'DataSource1'. (rsErrorOpeningConnection) For more information about this error navigate to the report server on the local server machine, or enable remote errors
I deleted the data connection and the Report Viewer and direct URL worked again. I'm now even more stumped because "Report 2" can at least download the report manually using Report Viewer.
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 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 a report running on SQL Server Reporting Services which is rendered in browser. It has several report parameters. Is there any way to save values of the parameters for next run? For example, I set parameter "Results from date" to some day in the past, view report, then close browser and then open it again - the value of this parameter will be date which was set in my previous session. Is it possible?
Check out this little gem.
From the article:
...a method of enhancing Reporting Services reports to make
them ... remember the parameter selections so that next time they run
the report they haven’t got to re-select the same parameters.
We are using reporting services for our reports and are currently using the Report Manager application to allow users to run reports. The report manager application can be accessed from outside our firewall, so we have configured reporting services so that the report manager web application is on a separate server than the report server web service.
This configuration is working great, except when a user runs a report it does not show the 'Generating Report' message while the report is being generated. The screen does not change and shows no indication that it is working on generating the report. It does generate the report correctly, and everything works correctly, it just does not give the user any indication that the report is being generated.
I have only had this problem when we have the report manager and reportserver webservice on separate servers. I have done a lot of searching but have not found any information about what could be causing this or how I could possibly fix this issue. I would really appreciate any suggestions on how this can be fixed so that the user does get an indication that the report is being generated.
The 'generating report' message does display for a split second before the report is rendered. For example if a long report takes five minutes to run, I will get nothing for five minutes, then for a split second I will get the 'generating report' message and then it will show the report.
Thank You,
Eric
Run it on the Report Server and do a view source when the "Generating Report" message is displayed.
Do the same on the other server when the "Generating Report" message should be displayed.
I suspect that some files/images might be missing.
Have you run SQL Profiler on both machines to see what is going on when you run the report? I have seen three server configurations where the ReportManager, the RS catalog db, and the SQL database were on separate machines and there was an enormous load on the RS catalog machine which brought everything to a standstill.
Hope this helps,
Bill