Currently, the POST api/reportserver/v2/documents endpoint is available only for the standard version of the Report Server.

Consider adding it to Report Server for .NET as well.

Hi,
   You guys give the tool,but not release it's value enough;Will there are a method to localize the desinger or compile the designer from source by myself?

We are disappointed with the lack of SSRS improvements over the last 8 years.  We use data driven reports extensively.  For example, every day at 10am we run some report that emails everyone a list of items in their inbox from a custom application that routes them a task they need to act on.  

The problem we experience is that there is no way to flag an item as "emailed" successfully. So we end up either writing our queries to only select the previous 24 hours worth of data, or we write the select of the data inside an SP that also updates the data to mark them as "emailed" even though if there is a problem rendering the report or a problem contacting the email server, the emails won't actually go out.

Basically if we could have a data driven subscription, and while the server is looping through the data, sending off emailed reports, we could get a hook to update status for the item that was just emailed, or just errored during report rendering.

 Please consider to provide access to the Report Server API via client (most probably Javascript). We want to get a report rendered in a given format in a Java based application by creating a custom client of the service.

Our team is working with TelerikReporting with reports we write in Visual Studio rather than designing them directly in the tool.  This lets us do version control which is important to us.  

It's working well for us.  However, it would be much smoother a simple change:
- when you upload a report, you should have the option to overwrite the definition of an existing report.  Otherwise you have to:-
- delete the report you are updating
  - because there are schedules atached, you have to delete those as well
- recreate the report
- recreate the schedule

You can understand why this is time consuming. 

I would like to suggest support be added for external assemblies in Report Server via the ObjectDataSource similar to what is available in Reporting Services.

As a developer integrating the ReportServer into our solution,
I want to be able to pull data for reports from my custom business objects model, instead from database,
So that I can reuse the data layer I already have along with its business rules.

Could the 'From' email address in Preview Email functionality be self populated from the 'Mail Server' SMTP settings in configuration?

This way the users do not need to a) remember the email address; and b) type it each time they are emailing a report.

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.  

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.

We've recently deployed a new infrastructure with multiple instances running Telerik Report Servers behind a load balancer.

In this new structure, we noticed a new intermittent bug when rendering some reports using the HTML5 report viewer, which is breaking some of our images included in PictureBox controls due to 400 Bad Request errors.

Upon further inspection, it seems the error happens because one of the instances is returning the following error instead of loading the image, hence the intermittency.

Provided document Id has expired. Please refresh your browser to generate a new one.