Telerik Reporting Cache Mechanism in Dotnet6

[mubarak]

Hi Team ,

I started using Telerik reporting , not sure how to use Cache mechanism , so telerik report should not connect production database every time instead cache data should be render ?

Tried few things like DatabaseCacheConfigurator.exe , but below error occurs .

Also any file cache mechanism available in Telerik Reporting ? , i can see all Cache mechanism are related to database like SQL Server , Postgre SQL , SQLLite etc....please help on this.

[Dess | Tech Support Engineer, Principal]

Hi, Mubarak,

I am sorry to hear that you are facing any difficulties with the Telerik Reporting Cache Mechanism in .NET 6. More information about this functionality can be found in the Configuring the Cache Management System help article. As to the error message, it wouldn't be easy to determine what is the root cause according to the provided brief information. Could you please elaborate?

- Is the error randomly occurring or it is reproducible with strictly identical steps each time?

- Could you please provide more details about the exact scenario you need to cover and in what context the cache mechanism is used?

- Are you using it in a desktop or a web application?

One possible reason which may lead to this behavior is described in the following KB article: Operation Could Destabilize the Runtime Exception Occurs when Running on Windows Azure.

As to the File Cache Provider, I would recommend you the following resource along with other useful cases how to use the cache mechanism even with a custom provider:

Configuring the File Cache Provider

Configuring an MSSQL Database Storage for the Reporting REST Service

Configuring the Database Cache Provider

Configuring Custom Cache Providers

I hope this information helps. If you need any further assistance please don't hesitate to contact me. 

Regards,
Dess | Tech Support Engineer, Principal
Progress Telerik

[James Glinsek]

Hey Dess,

So, I am trying to use the `Telerik Database Cache Configurator` as well, and experiencing the same results as Mubarak (but I'm using the latest release of 2025 Q1). I'm just trying to run the tool locally on my Windows 11 development machine and set up a Sql Server cache DB for testing.

If I choose "Configure engine / viewers cache database" and click the "Create schema" button, I get the "Operation could destabilize the runtime." error every time (no matter what I choose in the target backend - I tried Microsoft SQL Server and Microsoft SQL Azure. 

Now, if I choose the "Configure REST service storage database", then it does work and it creates what appears to be the "cache database" and I do see those tables getting used when I set my `Storage` up to use the `MsSqlServerStorage` option with my connection string. 

So, I guess there are a few questions:

1. What is the different between the 2 "database usage" options?
2. I used the "Configure REST service storage database" and that seems to actually be a "cache" database. Is that accurate? 
3. Why does the option to "Configure engine / viewers cache database" fail every time with that exception?

[Dess | Tech Support Engineer, Principal]

Hi, James,

Following the provided information, I have tested the behavior on my end with the latest release of 2025 Q1. Indeed, the error occurs every time:

It seems that we have a similar issue internally logged in our backlog. That is why I have created a public item for it for better visibility to our customers. You can cast your vote for the item, track its progress, subscribe for status changes, and add your comments on the following link: 

DatabaseCacheConfigurator.exe throws exception when creating viewers cache

As to the question about the main difference between the database usage options: The Reporting REST Service that serves report documents to the HTML5-based Report Viewers hosts a Reporting Engine that also utilizes the cache management system while rendering the report documents. After finishing with the rendering, the REST Service moves the prepared document or document pages and all the needed resources, for example, the images for the HTML renderings to the REST Service Storage and releases the cache.

The utilization of the cache management system constitutes an important difference between the viewers working with embedded Reporting Engine and with Reporting REST Service. The former reuse the processing report, hence fetching and processing the data only once for a report, storing the necessary processing objects in the cache. The REST Service processes the report again with each new rendering.

I hope you find this information helpful. Please, let me know if there is anything else I can assist you with.

Regards,
Dess | Tech Support Engineer, Principal
Progress Telerik