We're sorry for the issues you're having with our products. It is important to us to understand the exact cause, so we would like to ask you to investigate further in order to help us pinpoint the problem. Here are a few suggestions to check:
- Make sure the Report Server's application pool has Enable 32-bit
flag set to false
. Otherwise the worker process could use only 2GB of your memory. See this thread
- Add a trace listener to the Report Server's web.config file and inspect the produced log. If the reason for the exception is still unknown, please send the log to us to investigate it on our side. This article
explains how to add a trace listener in the Standalone Designer's configuration file, but the same approach applies to the web applications as well.
- Check the event viewer for any IIS-related errors.
You can also check the <processModel> element
in the machine.config file, which is used to configure the IIS applications and increase the number of maxWorkerThreads
if needed. A table with the recommended values can be found here
Please note that the time needed to execute the query against the database is not relevant to the time (and resources) needed to produce a report. A simple "select * from production.sales" query can be executed in a few seconds, but the received data must be processed (enumerated and aggregated), and the produced multidimensional dataset will be kept in memory until the final rendering (PDF, EXCEL, etc) is performed.
Please apply the suggestions above and if you have further questions, let us know.
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Telerik Feedback Portal
and vote to affect the priority of the items