We have configured our Report Server Application Pool to run in 64-bit mode, to enable the server to utilize more available memory on the server, which has helped with some particularly large reports that were previously erroring out. However, when scheduling the same reports, it seems the Report Server Service Agent has the same issue, as it runs in 32-bit mode and we are frequently the error "Error details: Exception of type 'System.OutOfMemoryException' was thrown". Is there a way to configure the Service Agent in 64-bit mode?
We have standardized the usage of Central Identity System across applications using OAuth and OpenId connect based https://identityserver.io/.
As a report editor, I want to authenticate to report server frontend using IdentityServer.io Single sign on.
As IdentityServer is .net server core based, we would like ReportServer also .net core based to support non-windows hosting scenario.
Hello, I would like to be able to search within the report datasource on the right hand side of the viewer. I have a lot of fields to search. Thank you.
In order to provide better data-driven subscriptions implementation, the subscribers of a Scheduled Task or Data Alert should be modified dynamically. Currently they are a static list of emails, which is not convenient when a report must be sent to a whole group of users in an organization, because the group members can constantly fluctuate. Report Server should provide the option to declare an external data retrieval service in the ST/DA subscribers list. This service could be a REST API endpoint or a file path that will return the list with the subscriber emails.
I'm using Crystal Enterprise for a longtime, and would like to replace it with that tool. On of the most useful feature is scheduling (for time-hungry reports, that takes more than 20 minutes to be generated). It will be a plus if you add: * The ability to choose the Execution start time, and frequancy; and to enable or disable the schedule job without lossing it. * Add a menu item called "Schedule Jobs", to view all schedule jobs of any accessible report (per profile; Admin can see all categories by profiles). * The ability to execute on-demond (execute disabled or enabled schedules for prepared parameters). * The ability to sign the generated PDF. * The ability to send generated PDF to mail (one or more), and to set the mail subject and body. * nerated PDF to folder (local, remote with auth) or FTP.The ability to save the ge * The ability to view schedule execution history, and view its result; and Add option to clear old results. * No "time out" for longer generation process. * Schedule jobs queued per user profiles; * Admin can set priority to user profiles (to execute queued jobs), and can cancel jobs.
After changing the culture settings on the server machine to EN-GB (which should display the date in dd/MM/yyyy format), the Preview of the report parameters still shows the date format as default, in US format (MM/dd/yyyy).
However, I would not expect to have modified the code to fix this, it should be a configurable option and/or take local server formatting.
As a user utilizing the Report Server product, I need to use a single instance of it to serve two or more completely separated divisions/clients so that they do not have access to each other's assets, so that I do not have to make two different deployments of the server and support them. See https://en.wikipedia.org/wiki/Multitenancy
We get all data from a REST API with an OAuth 2.0 token-based protection. Is there a way to implement the login once and use the token for each data source? Right now, if I have multiple data sources in the same report, each one has the 2-step Authentication Settings and does its own login to the REST API.
Currently, if a report has multiple crosstabs and I would like to use this report for Data alerts. While setting up the rules I am unable to set up rules across cross tab. For instance, crosstab1.textBox59 >= 0 & crosstab2.textbox78 <= 0 is not possible. when i save a rule for crosstab1 and try to add a new rule for crosstab2 it automatically deletes the crosstab1 rule.