"Crystal Reports Maximum Report Processing Jobs Limit"

[Former Member]

"Crystal Reports Maximum Report Processing Jobs Limit"

How to overcome the error and From where we can get Paid Techincal Support since we were trying last one year to over come this error , i have seen lot of suggtions but nothing is giving desired result , hence requested to give Paid Support details.

[former_member11696 · Accepted solution]

Need to know what product and version you are using?

CR for VS and other single use processes have a built in limit of 3 reports being able to be processed at one time.

The efficiency of crpe32.dll, the main report engine, is such that most applications will not run into the 3 JOB limit. There is a registry key that defaulted to 75 jobs in RAS, that can be set to 0 or -1 for unlimited but not recommended, you should set it to the limit the hardware/software can handle.

If you are using CR for VS then you need to build in a job handler and limit the number of jobs being processed by the Engine.

Bottom line is you CAN NOT overcome this limit if you are not using CR Server/ CR Server Embedded (OEM)  or full BOE.

If you are using one of the above then to handle more jobs you simply add more RAS servers until your expected loads are processed without failed jobs or the job limit is maxed out.

To contact CIC click the Contact Us at the bottom of this page.

A paid case will not change this built in limit. You need to scale the CR/BOE Servers according to your load.

Talk to Sales, I can't find it right now but there is a Sizing Guide that discusses all of this.

Don

[DellSC]

There are not a lot of ways to get around this - this is due to the limitations of using the .NET SDK, which are:

5 concurrent sessions

100 concurrent print jobs

I "print job" is an instance of a report or subreport.  For example, if you have a report that has a subreport in the report header, that's 2 print jobs when it runs.  If the report has a subreport in the details and there are 99 records, that's 100 print jobs.  If there are more than 99 records, the report won't run.

The one thing you can do programmatically is to make sure that you explicitly call dispose() on the report when the user is done with it.  The SDK is based on some COM objects and this is the only way to make sure that you've cleared the session when you're done with the report.

-Dell