Reporting Services Report Manager Generating Report Message - sql-server

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

Related

Data retrieval failed with subreport CRM SSRS report error

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.

SSRS 2017 reports loading slow with Intranet connection and loading immediately with Internet connection from web link

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

SSRS Ad-Hoc report stuck on loading screen

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

SSRS report only works with a specific user and for the other users, it stucks in loading forever

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.

SSRS report subscription ended with an error

I hate to cross post, but I wasn't getting any progress with this on serverfault and there appears to be a lot more activity with regard to reporting services here.
I've created a simple report in SSRS, and then tried my hand out with a data driven subscription.
I can verify that the subscription runs on the 'My Subscriptions' page. Under Status it says Done: 1 processed of 1 total; 1 errors.
How do I find out what this error is?
I've looked in the Windows Event Logs and haven't found anything. I also checked the SQL Server Logs and nothing is there either.
You need to look in the "Report Server Execution Log" which is a particular SQL Reporting Services log file.
See Reporting Services Log Files for details.
A bit late to the party, however:
Here is where I find my logs when DD subscription fails:
C:\Program Files\Microsoft SQL Server\MSSQL.2\Reporting Services\LogFiles
look for filename: ReportServerService*.log with relevant Date Modified
You also can check the Report History, to get this option, put the mouse on top of your report and select manage option from drop-down list of your report, look for the "Report History" on the left options, create a "New Snapshot"
It will show you, the last error know:
Parameter validation failed. It is not possible to provide valid values for all parameters (rsParameterError)
for this case you need to check the definition of the report, I had an issue with the drop-down list I used to send parameters to the report.
The path under which you can find Report Server Service logs could be different, such as:
C:\Program Files\Microsoft SQL Server\MSRS12.MSSQLSERVER\Reporting Services\LogFiles
In this logs you can find errors that happened after generating the report itself. For instance, if the Reporting Services user needs to write the report as a CSV file after a subscription and it lacks the necessary authorization, the only place where you can find the description of the error is in these logs, while the history of the Job connected with the subscription and the Execution Log will tell you that the Report was correctly generated (nothing about saving the report).

Resources