When I try to use the Report Server for .NET 2025 Q1 in a Docker container, I get the following error in the logs:
"An error occurred while checking the licenseResult: The value cannot be an empty string. (Parameter 'path')."
The error does not seem to prevent the Report Server Manager from remaining functional.
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.
When you revert to another Report revision and don't refresh the browser page, the date of the active report in the Revisions History is different from the Report Date Modified. The user needs to refresh manually to match the dates.
The issue is demonstrated in the linked muted video.
We recently upgraded our report server after years of operation due
to various technical challenges. Our system currently manages over 250
reports and more than 100 scheduled tasks, all of which have been
running for the past seven years. The backup process has become
significantly delayed, as we are handling over 70GB of data, primarily
composed of daily generated reports related to executed scheduled tasks.
While we regularly review execution history (execution date & time) for debugging purposes, but we never use the
reports of executed scheduled task for all historical records. This leads to unnecessary storage usage, which will continue to grow over time.
Manually deleting seven years' worth of historical reports across over 100 tasks is not feasible, and scripting this deletion would impact the performance of our already heavily utilized report server.
I believe the execution history is valuable for everyone for debugging purpose. However, the associated reports which takes significant amount of storage space should be kept optional. Therefore, I propose the following features:
During the configuration of scheduled tasks, include an option (similar to an "Enabled" checkbox) that allows users to choose whether to retain or delete the associated report for each scheduled task execution. This would only apply to reports generated for future task executions.
Introduce a REST API endpoint within the Scheduled Tasks framework that would facilitate the deletion of historical tasks and their associated reports.
These enhancements would greatly improve our report management and storage efficiency as we have over 10+ intensely used report servers for different businesses.
These are some feature requests which align with our goals -
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
On some system configurations, the setup wizard throws the following error when upgrading the Telerik Report Server from version R2 2023 SP1 to version R3 2023 SP1.
To work around the issue, one can uninstall the previous version first and install the new one afterward.
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.
In the production environment, there is no option to clear the Redis database after each redeploying/restarting of the applications (ex. k8s with many pods).
The are many reasons:
- this database can be used for other purposes, but you deprecate RedisStorage with a separate database selection
- more complex deploy/restart operations with additional steps to clear Redis
- users can use Reporting at this moment
Please add TTL option for RedisStorage in ReportServiceConfiguration
Yesterday I installed the report server. Everything seemed to be working correctly. Today when I try to view a report I get this error message "Error registering the viewer with the service. An error has occurred. Incorrect value (null) deserialized. Make sure you are using CacheStorage inside single-instance application deployment only."
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.