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.

Reports with resources for different languages should be rendered with the language resources and client culture.

• Preview - render the reports according to the browser settings/language;
• Scheduled Reports and Data Alerts - language/culture option is needed for every recipient;
• Server API - have to accept device info or language/culture option;

Functionality for capturing user activity like executing reports from viewers or through the Report Server Web API.

We cannot delete reports using the Report Server UI. After you select the report and choose to delete it, the report appears as removed from the list, even though the details are still visible. If you refresh the page, the report is still there.

Further investigation revealed that the ServiceAgent is not running. There is no proper error message indicating this though.

The issue is reproducible only with the Report Server running under HTTPS. When under HTTP there is a proper message stating that the ServiceAgent is stopped.

Currently, the Report Server is installed with binding only to HTTP-type sites. This may break a Report Server site bound to an HTTPS site after upgrading to a new version. It is necessary to add the binding to HTTPS manually after each upgrade.

It would be great if there is an option for binding to HTTPS with the installation and if all the bindings can be preserved after upgrading.

If you unselect all the days from the Day of the Week in the recurrence rule of a scheduled task of data alert, the task can be saved but will throw an Internal Server Error and you won't be able to list the available tasks on the server.

The linked muted video demonstrates the problem.

Here is the error stack trace produced by the ServiceAgent:

Telerik.ReportServer.ServiceAgent.exe Information: 0 : Loaded 37 tasks in total.
Telerik.ReportServer.ServiceAgent.exe Error: 0 : System.IndexOutOfRangeException: Index was outside the bounds of the array.
   at Telerik.WinControls.UI.Scheduler.ICalendar.CalHelper.TryParseRecurrenceRuleProperties(RecurrenceRule result, IEnumerable`1 keywordPairs)
   at Telerik.WinControls.UI.Scheduler.ICalendar.CalHelper.TryParseRRuleCore(String valueToParse, RecurrenceRule& result)
   at Telerik.ReportServer.Web.Utils.Appointment..ctor(DateTime startUtc, String recurrenceRule)
   at Telerik.ReportServer.ServiceAgent.Tasks.TaskInfo.UpdateNextOccurrenceTime(DateTime utcFrom, DateTime utcTo)
   at Telerik.ReportServer.ServiceAgent.Services.SchedulingService.CalculatePendingTasks(List`1 pendingTasks)
   at Telerik.ReportServer.ServiceAgent.Services.SchedulingService.MainLoop()
   at Telerik.ReportServer.ServiceAgent.Services.SchedulingService.StartMain()

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.

• The retention period would ideally be able to be set globally and overridden for a particular task
• The retention period would be specified in days
• To actually remove the old executions you could create a task that runs once a day and is executed by the windows service that exists -OR- each time the task executes to run the report it can also look to see which historical executions are older then the retention period and delete them.
• The removal of the historical tasks should also delete any associated documents

Implementing this would allow for much quicker upgrades, backups, and restores of the Report Server.

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.  

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 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.

One of the biggest draw backs I am having while pitching the Telerik reporting products is the amount of work that would be involved in converting our existing report libraries to the Telerik reporting format. You all have some conversion capability built into the Telerik Reporting Designer, but it is so limited that we rarely find a report that we can use it with. I know you all have a disclaimer stating that as the case. However when I am trying to persuade my peers to take a look at your reporting products that single scenario is the one that I can never win and rightfully so.

I would really love to either see operability within your reporting server to be able to schedule and distribute a multitude of report formats such as SRSS, Active Reports, and Crystal or a much more reliable and feature rich converter. 

A great feature would be to add security over the connection strings that a user can choose from in the server. We have a development and production environment and we want to allow people to write reports but we don't want them hitting production data because they don't always build efficient queries which can take the production database down.

This would help allow access to development and production separately and help keep the DBA from yelling at me :)

Built-in option to select all available values of a multivalue report parameter.

A Multi-value parameter can use a user function to have a value accumulating all available values. Add built-in support through the expression engine.

Background: 
Our report server database undergoes maintenance every weekend. As part of this, the report server DB is taken down without stopping the Telerik service. When the DB comes back online the reporting service doesn't recognize the re-instated DB and doesn't send out reports. 

Reply from Telerik Support:
My assumption is that the Report Server has hanged due to an error when the Storage was not available. The service has probably remained in this undefined state even after re-starting the database. Note that the Storage is a required resource, hence the service cannot work without it.
We have logged the current behavior of Report Server with respect to its Storage database for improvement in our system.

Feature request:
It would be nice to get an alert/email to the Report server admins that the Report Server DB/Storage is unavailable. 

User functions should be visible in Edit Expression editor when editing Report Server's report in Standalone designer.

Considering that the server's configuration was modified to load the custom assembly with user functions as per How to configure Telerik Report Server to use reports with custom functions, there should be no other configurations required.