It is very weird that we encountered this error in our environment.
As far as we set the printjoblimit to -1 in registry, It suppose to load reports unlimited. As I understood from SAP and Business logic documents, those registry keys have been added to optimize the way that crystal reports was working and 75 concurrent reports is optimize value to prevent server hangs.
But why when we set that value to -1 meaning we want to run unlimited reports (we dispose reports properly, so we dont have resource occupation problem).
Do we need to do another manipulation or configuration to make crystal reports work and doesnt generate this error?
