The 'report name/Shelve' path seems to be broken.

For example, when I try to preview the report in Server > Web Preview in the Standalone Designer connected to the Report Server, the browser tries to open the URL 'reportServerHost/Report/View/CategoryName/ReportName/Shelve'. However, it hangs and doesn't display anything.

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.  

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()

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.

Getting this error in the browser when trying to preview a report:

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.

A possible reason is the cache for the Report Server used for previewing reports has become corrupted. A workaround is explained in the Telerik.Reporting.Cache.CacheStorage.AddInSet NullReferenceException KB article.

It will be very convenient for the user to be able to clear the cache directly from the Report Server Manager UI.

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

I am trying to edit an existing user, and before changing anything I receive the error message 'The email is already taken!'. This happens occasionally.

Here is a link to a video that demonstrates the problem.

It seems that when you try to open two tabs in the same browser looking at different websites, the browser gets confused about the URL that is sending the request. Issue is related to CORS protocol and HTTP caches.

It sounds like something needs to be changed on the report server so that even if it gets cached it would still allow access when I switch sub domains.  Or something on the viewer side to clear the cache.

Following the ReportServerManual.pdf I meet the system requirements, using Visual Studio 2013 and have followed the installation guide but I am getting the following error when running the report server web application;

"A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 50 - Local Database Runtime error occurred. Cannot create an automatic instance. See the Windows Application event log for error details.
)"

I have checked the application pool identity has permission to the files.
Please advise.  Kind regards, Scott.

The current version of reporting service seems to have issues with the newer servicestack libraries. The only way I could get the ServiceStack Service implementation to work is to use the following dependencies (attached). What is the official supported version of ServiceStack and when will newer version be supported?

Though I have overridden the mail template for an individual alert, It is picking up the Configuration | Mail Templates | Data Alert External User for an external email address. However, internal email address gets the right one. 

Please help me resolve this. 

Thank you for adding this feature.

I tested this feature and found that emails were not being delivered to email addresses in the 'CC' email address field.

Furthermore, would it be possible to look in to these options?
1. Add 'BCC' email address field option
2. Add multiple email addresses under 'MAIL SERVER' in Configuration - This will allow us to add SMTP email services for multiple companies / clients, which can then be utilised in the 'FROM' email field in the Preview Report Email feature.

It is great that Telerik takes on feedback and is continuously updating the software to provide an excellent service to its users.

Thank you.