When printing a crystal report i.e. printing an Incident using the View Report button on Incident window, an error is displayed: Inner Exception: - The maximum report processing jobs limit configured by your system administrator has been reached.
The error message appears because the web application has exceeded the Crystal Reports reporting engine default print job limit of 75. Or, in other words, a high reporting load has been placed on the reporting engine.
There is a problem raised for this - Problem 5754 - Loading reports in Web Access causes a report limit to be hit because connections are not being closed.
The immediate workaround is to recycle the application pool in IIS that WebAccess uses ( or restart IIS).
The limit can also be increased in the registry in the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Report Application Server\Server: PrintJobLimit
Using the Registry Editor incorrectly can cause serious problems that may require you to reinstall the Microsoft Windows operating system. Use the Registry Editor at your own risk. It is strongly recommended that you make a backup copy of the registry files before you edit the registry.
Setting the PrintJobLimit value to a higher limit allows more prints to be processed although this could affect system performance. Therefore would recommend setting the application pool to recycle regularly i.e. each night to close any open connections.
Please note from testing using the value -1 does not work and defaults to the value of 75.
Also see the SAP community article link on this issue for Crystal Reports.
If you encounter this problem please report this to Landesk support as an instance of Problem 5754.
ServiceDesk all versions using Crystal Reports 10 through to 2008.