Crystal Reports Exception: The maximum report processing jobs limit configured by your system administrator has been reached

Question

I\'m facing a very buggy issue, in ASP.NET application after viewing the same report many times simultaneously I got this exception:

The maximum repor

Answer 1

Crystal Report document implements IDisposable interface. So all you have to do is to enclose the report's instance with using statement. It will be automatically closed and disposed once the using statement is completed. You can write something like that:

using(var report = GetInvoiceReport())
{
     // your logic here
}

or (depends on your context):

using(var report = new ReportDocument())
{
     // your logic here
}

Answer 2

In my case, the report had 4 subreports...

What solved for me was changing the value of "PrintJobLimit", from 75 to 500, in the following Regedit paths:

• \HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Report Application Server\InprocServer

• \HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Report Application Server\Server

Answer 3

You have to Dispose your report instance after all. If you Dispose the report after showing it, you will never see the error:

The maximum report processing jobs limit configured by your system administrator has been reached

Code:

Dim report1 As rptBill = clsBill.GetReport(billNumber)

rpt.Print()

'Cleanup the report after that!
rpt.Close()
rpt.Dispose()

Answer 4

I was working on local report server. I have hosted my web application in other pc. When I got such error I just did IISRESET and working fine now.

Try this, this could help you.

Answer 5

Make sure IIS user have sufficient permission to delete files present in "c:/windows/temp" folder.

I face the same issue once I provide write permission to that folder then it solved my issue.Also make sure dispose that object after generating the file

Answer 6

I know this thread is older, but if you configure the app pool setting "Recycling..." to recycle at, say, 180 minutes instead of 1740 minutes (the default), this might free up the needed resources.