The Migration tool updates the source storage instance to its own version prior to migration process. This might cause issues in scenarios where an older version of Report Server storage is used in production and the migration is performed using a newer version of Migration tool. The tool must show a confirmation dialog and wait for input from user before modifying the source storage.

Hi,

 

I have a report that is scheduled to happen first day of every month. The thing is that when I look at the next occurrence of the report, it is happening on the second day of the month. I am attaching the report settings herewith. Please let me know if you have a solution/ explanation to get this corrected. Thanks a lot in advance.

 

 

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.

To localize the reports I now set the Localizable parameter to true and Culture an Language options to nl-NL (for the Netherlands).

So for Dutch customers that will be alright, but when I want to send a report to an English customer I must now make a second report with en-EN.
It will be nicer when I can change that in the schedule.

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?

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,

I'm trying to customize the interface language (english to german) of our report server web application without success. I set some language entries in the sr.user.js file in the script folder of the web application but the labels of the report server remain english. When I do this in the original file (sr.js) it works well.

Provide an official and supported migration path from the Telerik Report Server built on .NET Framework to the newer .NET-based Report Server, allowing reuse of existing storage and configuration.

Organizations running long-lived Telerik Report Server installations want to adopt the newer .NET version for performance, longevity, and platform alignment, without rebuilding their entire environment.
Lack of migration support is currently a blocker for adoption and increases operational costs.

Suggested Solutions

• A migration tool or script that converts credential storage to the new hashing algorithm

• A supported upgrade path that forces password resets but preserves users and roles