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.
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 using VS2017 and have added the parts necessary to use SSRS. I've created three reports and have successfully previewed them in VS. I deployed them to a report server and checked that they worked, and they didn't. The server reported an error. To solve that, I had to go into the Data Source Properties -> Credentials dialog and change the Credentials to "Use this user name and password."
That solved the error that the server reported. I deployed them once again, and they worked. However, now when I try to do a preview on any of the reports in VS, I get an error message that says:
an error occurred during local report processing
an error has occurred during report processing
I've already looked on here and Googled this, and most responses were for people using rdlc reports in applications, which I am not doing. Any ideas?
Using SSRS 2014 enterprise.
I have a data driven subscription that should be generating about 500 reports as PDF files.
These reports are made up of a master report and two sub reports. If I view the report through the web portal, it works perfectly. The master report takes one parameter that is also passed to the sub reports, this parameter is data driven from a database query.
When I run the report through the subscription, all the expected PDF reports are generaeted on the file share, however they all only contain the below error, once for every sub report.
Error: Subreport could not be shown
The SSRS execution log doesnt contain anything helpful, only the below:
ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: , Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Exception of type 'Microsoft.ReportingServices.ReportProcessing.ReportProcessingException' was thrown.;
This was caused by an error in the subreport. It appears that these errors are not passed up through to the logs, they are caught and then rethrown as an error that happened in the subreport, destroying any chance of identifying the error!
Running just the content of the subreport through a data driven subscription, I discovered the following:
When ran from a subscription, the job would hang, but log the following to the SSRS ReportServerService log (in the SSRS program files folder)
ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.HasUserProfileDependenciesException: , Microsoft.ReportingServices.Diagnostics.Utilities.HasUserProfileDependenciesException: The '/REPORTNAME' report or shared dataset has user profile dependencies and cannot be run unattended.;
This error means that there was something in the report that had a dependency on the user.
The subreport was using the following parameter to log to a trace table:
[&UserID]
Replacing this with a value that is not user dependant value allowed the subscription to run.
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 !
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