The system has been deployed for nearly one month. I checked that the Registry has two key values for the maximum number of prints, 75 and 100, respectively. This error should have occurred as early as possible, but why is it exposed now? After careful analysis, the maximum number of prints is for each virtual directory.ProgramAnd the target server is in running, so the maximum number of times is reached, think of three solutions:
1. Restart the server to reset the number of prints;
2. Modify the maximum number of key values in the registry;
3. Refresh or recreate the virtual directory;
Although the first two solutions are good, It is very troublesome to restart the server, so you can simply modify the registry (the registry takes effect only after the restart is required) and then refresh the virtual directory, in this way, the number of printing times is reset and the days when the server is scheduled to restart can be reached.
Found on the Internet:
HKEY_LOCAL_MACHINE; software; Crystal decisions; 10.0; Report Application
Server; inprocserver; printjoblimit: 1000
There is also an HKEY_LOCAL_MACHINE; software; Crystal decisions; 10.0; Report Application
Server; server; printjoblimit is also modified to 1000