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

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.

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

Hello, 

 

I recently upgraded our Report Server that was hosted in IIS with an HTTPS binding but after the upgrade we were unable to communicate with the server using HTTPS. We received an invalid client id error.

We updated the bindings and everything worked. However, it would be nice if we could upgrade Report Server without changing the IIS bindings.

 

Thank you.

Hello, 

I was on a remote web session with an engineer and we discovered that the Scheduler UI isn't saving the changed password to the database. 

The environment that I use is below. 

• Report Server is installed in an Azure Virtual Machine
  • IIS is bound to ports 443 and 83
• The SMTP Service is on RackSpace
• The storage is located in SQL Server

The steps to reproduce are as follows.

1. Change the Password
2. Save the Changes
3. Send Test
4. Receive Error output

During the Remote Web Assistance Session, we tried a Gmail SMTP server and received the same results. 

We also enabled tracing and noticed an error in the event logs which I will attach here. 

Please let me know if you need any additional information.

We would like to be able to prevent our users from continuing to attempt to log in to RS after a certain amount of failed tries.

If you previewed a report from the Report Server after more than 30 minutes of inactivity, there is an error message "Forbidden. Insufficient credentials."

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

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.

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

The Guest User can not use the search functionality in the report. It gets the error "Authorisation has been denied for this request".

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.

 

The reports are scheduled for the first of each month at 6 PM but are sent out on the last day of the month at 6 PM. The Next Occurrence is also set for the last day of the month at 6 PM.

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

Hello, almost every time I select a scheduled task that I have to scroll down to select in the Scheduling tab, the grid view jumps back up to the top of the task list, making it very annoying to look through tasks.

 

1. Open Scheduling tab.

2. Scroll down in scheduled task grid view below the first N rows displayed.

3. Select row corresponding to a scheduled task.

4. Task grid view returns to the top N rows of the scheduled tasks.

 

Thank you

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.