Hi Alvis, thanks for the information. this is very useful.
The error is thrown when there is too much load on the crystal engine running on the web server. Load includes:
- Report objects stored in sessions (ESS uses this for caching and paging)
- Sub-reports count as an addition object (which is part of the 75 default limit)
Also note that if you should set an upper limit based on your available resource for this application. Setting he print job to
No Limit will degrade server performance. Configure IIS to restart once a memory usage point has been reached as this process will use up IIS server memory which can slow down other processes.
In a good setup, applications using crystal reports should be using a separate
application pool which is set to restart once you have exceeded a set memory limit. See
this link for more information on setting automatic IIS application pool restart.