I am using the Reporting/Report Server 2024 Q4, and my report uses the Amiri font.
Other export formats work as expected, however, the PDF export fails with an "Object reference not set to an instance of an object" error message and produces a corrupted/empty PDF.
Hi Team,
Currently when Report Server has whitelabeling enabled, the browser tab will still show "Page | Telerik Report Server". This request is to allow us to set a value for the 2nd half of the page title.
I see this is applied by using the @ViewBag.Title, my request is to have a field in the Whitelabeling settings page for a brand name in the title. This could be combined with the page name to have a customized title. For example "Page Name | Whitelabeled Name".
Here's a visual example to explain further
Thank you,
Rick
We need to send emails to specific people only when Errors occur in scheduled reports. They shouldn't receive the scheduled reports when there are no errors.
For example, there may be a new user role added for this purpose.
The assemblyReferences, typeReferences, and typeValidation configuration elements are not respected from the TelerikReporting.config files of Report Server Manager and ServiceAgent.
The same settings are respected when set in the corresponding Web.config and Telerik.ReportServer.ServiceAgent.exe.config.
HTML5 Report Viewer cannot connect to report server for .NET.
The old report server still connects us expected.
Hi Team,
This feature request is to ask that a capability be added to Report Server that restricts certain administrative functionality to only be allowed on predefined subnets (e.g. adding new users, data sources, etc.).
Thank you,
Amish
Currently the Report Server appears to keep the execution history of scheduled report tasks indefinitely. The task execution history is a very useful feature but there appears to be no way to limit the history to a certain amount of time. For our use case it is unlikely that we will need to go further back then 1 or two months in the history and as we get months an even years of history (which includes the execution and related documents) the time needed to backup and restore the Report Server increases. We only have about 30 scheduled reports that run each day but over a year that is 10,000+ executions that are stored and anything over a month or so old has little value to us. I am not sure if these also have an impact on the overall performance of the Report Server or at least the Scheduler portion of the UI but that would be another reason to limit the retention.
Currently the only method to delete the executions is to either (a) do it manually via the UI (screenshot below) or (b) to write an application that deletes executions outside our retention window using the API to query and then delete them. Method (a) is too time consuming for a person to do and (b) will require writing the application but then also monitoring it's status and keeping up with any changes in the API over time.
I would propose adding some method of allowing users to set a "retention period" for scheduled task executions.
Implementing this would allow for much quicker upgrades, backups, and restores of the Report Server.
In my MSSQL database, I use SQL Server Authentication with a password that contains '^' and '<'. I connect without problems through the MSSQL Management Studio.
When I try to pass the connection string with this user, I receive an Internal Server Error and cannot set up storage with it.
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
As a Report Server user,
I need to deliver reports to all subscribers in a single email message,
So that no person gets the email more than once if the subscriber emails are groups and a person is part of multiple groups.
This would also allow the persons to reply to all other subscribers.
Milen
In one of our Dev environments we had Telerik Report Server installed, but unfortunately whoever set it up, didn't write down the Admin Username and Password.
The SMTP server wasn't configured when starting with the Report Server, and there is no option for resetting the password.
We do have a username and password that logs in, but it doesn't have sufficient rights to make the necessary administrational.
In such scenarios, it would be helpful if there is an external tool we may use to create an admin user directly in the Storage of the Report Server. Obviously, if somebody has unlimited rights to access the Report Server storage, he/she should be authorized also to be an admin of the Report Server.
Good evening. I have a ticket number 1563975. Attached video where you can see attached information. The TRS core database does not support SSAS OLAP connection. Only local connections work. Can you add that it is centralized?
We are using database storage for the Report Server and we are monitoring the report server service.
If the database is not accessible, for example due to it being updated, the service may stay running but it will not be able to send scheduled tasks.
In this state of the service (running, but not working), no monitoring or automated restart of the service will be triggered.
Please change the state of the service from running to not running when the service is losing contact with the database
When I delete a report from the Reports page, it disappears from the list. However, its details are still visible.
When I refresh the page, the deleted report info disappears.
The Report Server's built-in Web Report Designer does not resolve custom functions assemblies that are referenced in the TelerikReporting.config configuration and thus, on Design time, they are not visible under Functions -> Misc.
The workaround around is to reference the custom functions assembly in the Web.config file in {install_dir}\Telerik.ReportServer.Web