Qlik NPrinting may show a Cache status of Generating instead of Generated.
Cache was introduced from Nprinting 17. It stores data NPrinting captured from the QlikView or Qlik Sense app, helping performance.
The cache status has to be generated if a report should be created or distributed. In some cases, this cache status will stay "Generating" instead of "Generated".
This article provides direction how to approach the symptom.
Review the Connection Status
If Connection Status is "-"
This indicates the connection has not established between Nprinting and app.
- Verify that all Nprinting Service are up running including RabbitMQ Service
- It is possibly communication issue and/or Nprinting cannot access app by some reason.
- Review the NPrinting Engine log and NPrinting Scheduler log for more details.
- If the App is hosted on a remote drive, or being connected to remotely, place it into a local drive or open it locally to verify if the connection succeeds.
If Connection Status is "Ok"
This indicates the connection has been established between Nprinting and app
If Connection Status is none of above
- Check Nprinting Engine log and Nprinting Scheduler log
Verify the Cache Status
If connection Status is "OK" but cache status is "Generating":
- Verify the machine CPU/Memory of the machine. Does it match or exceed the system requirements, and are enough resources available during the process?
- When generating cache, the first thing NNrinting do is to apply a "Clear selection" to all the objects contained in the app.
- If there is resource exhaustion, Cache may not be generated.
- Review the NOrinting Engine log and NPrinting Scheduler log for more details.
Thirdly Upgrade to 17.2.3 or later if you are using 17.1.2 or prior.
Ensure that NPrinting Server and NPrinting Engine(s) versions match versions