PaperCut includes a large range of reports, each with varying features and purpose. Some reports, for example the ‘print logs’ report, can produce a lot of output, especially for large organizations with a lot of printing activity. It most cases these reports will be run over a specific (limited) date range - ‘last week’ or ‘yesterday’ for example. Running the report over a larger time period may produce too much data, and have negative effects such as:
Overloading the server, which may cause other requests to be slow or denied.
Causing the server to run out of memory.
Generating a very large file that takes up a lot of disk space to store, and bandwidth to download.
For these reasons, PaperCut has a max rows setting that prevents reports getting too large. By default, this is set to 10,000 (e.g. a user list report will show only the first 10,000 users).
In some cases, you may have reason to generate a report with more that 10,000 rows. For example, exporting a print log CSV report over a large date range. In this case, the max rows setting can be increased (either temporarily or permanently).
To change the max rows setting you will need to change this config key: reports.max-rows
Please see the section called Using the Config Editor to find out how to change config keys.
Increase the value to something higher. In general, this is the number of rows that will appear in your report. So if you want a 15,000 row report, set the value to 15000 or more. Then run your report again and confirm that all the data is now being shown correctly.
This release contains an updated Java version which no longer supports 32-bit workstations. If you have any 32-bit users launching the User Client or Release Station from a network share, see this Knowledge Base article for more information.