Let’s face it, there is only one issue here, the crystal print engine is being used too extensively but it is not designed for this much amount of load. Now imagine the same report being accessed by two users at the same time? So running a single report with one subreport could itself generate 76 print jobs and causing the issue. In this case the subreport being in details section will run for 75 times, once for each record generating 75 print jobs plus one print job for main report. Sometimes the error is self-explanatory but sometimes one has to identify the scenario that too many print jobs are getting generated.Ĭonsider a simple scenario where a Crystal report has 75 records and 1 subreport in details section.
Once this limit exceeds, above issues start to appear. Application hangs / crashes after processing multiple Crystal reports, starts working fine after windows service or IIS restart.Ĭrystal print engine is designed with 75 as a default print job limit.COMException (0x80041016): The maximum report processing jobs limit configured by your system administrator has been reached.” Followed by Error “ Load report failed.”.drill down, paging, searching, and more.). Note that a print job includes main reports, subreports, and in-session report objects (e.g. This includes paging, drilling, zooming and so on. So, what exactly is a Crystal Reports ‘Print Job’?Ī Print Job is essentially any action the print engine has to perform while generating a report. This blog summarizes all the information and suggestions we offer to the customers. This issue has been discussed many times on all fronts of Crystal support. Be it support incidents or community forums, one issue never gets old is the Crystal print engine reaching its print job limit. It’s been a long time since I am working with Crystal.
0 kommentar(er)
