We are using Crystal Reports 2008 in a Microsoft ASP.Net environment. Every since we started developing the report module using Crystal Report engine, we have realized the Print Job limitation for Crystal reports on a web server is a huge issue that needs to be handled by writing explicit garbage collection code. Since the code has evolved over more than half a decade, we have had some success in getting rid of this issue to a huge extent. However, there have been and still are users that use our product line that complain of their reporting modules suddenly stopping working pointing a crossing of the Print Job limit imposed by Crystal.
Our way of handling the report document disposal issue has been a mix of the straight forward code and some ingenuity.
On browsers that give access to the close event of the browser (IE), we generate a server post back on browser close and dispose the report document associated to that window.
Also, we keep a track of every report document that is loaded in a Session array and clean the array if the count goes over ten report documents.
This seem to work 90% of the times but fails esp. when they are multiple people logged to our Web application, each having a Session of his own in the memory, thus making the report document session array disposal undependable.
Keeping this in mind, I have some questions that I would love hear some answers from the SAP experts on this forum.
1. What's the best way to overcome this issue?
2. Does the 75 print job limit refer to each session on the Web Server or concurrent sessions on the web server.
Regards,
Faisal