I also discovered that the runtime engine has a limit of 75 jobs by default and you can edit the registry (PrintJobLimit) to increase it. If not, I would look at your IIS applications that are starting the run time, as there might be an issue there where improperly formed requests are occasionally issued to the Crystal Run Time. You might want to attempt a regression to the version we are using, and see if that solves your problems. We use both the 32 bit and the 64 bit run time (13.) every day for hundreds of reports with no issues that are traceable to the run time, except when some strange parameters get passed to the report, then the run time might error, but otherwise no issues. It only is doing anything when requested, there is no service, or anything else, it only becomes active when called from something else.
0 Comments
Leave a Reply. |