Qlik Community

Ask a Question

Knowledge Base

Search or browse our knowledge base to find answers to your questions ranging from account questions to troubleshooting error messages. The content is curated and updated by our global Support team

Live chat with experts, bring your API Integration questions. June 15th, 10 AM ET. REGISTER TODAY

How to resolve NPrinting - Pending Queued or Generating Cache Status


How to resolve NPrinting - Pending Queued or Generating Cache Status

Description of the Issue:

  • NPrinting Cache Status is stuck on "Pending" or "Queued" or NPrinting Cache Status "Generating" but never completes




Qlik NPrinting , all versions


Possible causes:

  • NP Engine may actually be offline
  • NP services and QV or QS services must all be running. Or of more of these services may not be up and running
  • NP services and QV or QS services may have become locked up and need restarting possibly due to insufficient system resources
  • The NPrinting server service account 'might' be shared with another NPrinting server or possible a QlikView server. This is not supported to do so. 
  • NP service account lost it's CAL while logged on as the NP service account when accessing the QV desktop
  • If engine offline or any of the above services are not running, this may cause the NP cache status to be "Pending" or "Queue" or "Generating"
  • Difference in versions of NPrinting Engine and NPrinting server services. Both MUST be the same version (as well as the NP designer).
  • Unsupported items need to be removed from QVWs in affected NPrinting report connections. On Open Triggers alone can prevent a QVW from being processed during report generation process
  • The NPrinting Server/Engine computer may not have sufficient resources and or the original system requirements have not been met



To resolve the 'pending' 'queued' or stuck 'generating' please check the following:


  • Are all of your NPrinting services running. If no, stop and restart all NP services
  • If the above doesn't help, restart the host operating system
  • If QlikView only, make sure that the NP service account use to run the NPrinting Engine service has a valid CAL assigned to it
  • Log on as the NP service account, open the QV desktop. if the personal edition message appears in the title bar. You need to acquire the manually assigned CAL or install a valid desktop QV license. 
  • To access a manually assigned CAL from a Production QlikView server, do 'file>open in server' while logged on as the NP service account to retrieve the QV CAL from the QV server.
  • If there are unsupported items in the QVW, this too can cause metadata connection reload issues as well and they must be removed. See the following unsupported QV items in the link: NPrinting: Unsupported QlikView Document items, System Configurations and other limitations
  • Ensure the QV desktop on the NP server is the same version as the QV server. ie: QV 12.1 SR4 Desktop on NP server and QV 12.1 SR 4 Server
  • Ensure a dedicated NPrinting service account is used. See the following for details: Dedicated NPrinting Server & Engine Service Account Configuration


Qlik Sense:

  • Check that all of the Qlik Sense services services are running. If no, make sure to start up any QS services that are not running.
  • If the above does not help, restart the host operating system
  • In the NPrinting Connection interface in the NP web console under 'Connections', use the NPrinting service account as the connection identity.
  • The NP service account use to run the NP Engine service should also be a rootadmin on the QS server. This ensures access to the QVF. If this account works then the identity previously used does not have sufficient permission to act as a connection identity.


QlikView and or Qlik Sense:


Once the above points have been managed, applied and the Engine is 'Online' status:

  • Abort ALL publish task and On Demand executions
  • Restart all NPrinting services
  • Start one task at a time.
  • Once the behavior is resolved, enable all tasks as needed
  • If the issue persists, consider upgrading to the most recent version of NPrinting to leverage the most recently performance updates, bug fixes, logging capabilities and product enhancements
Labels (2)
Version history
Revision #:
2 of 2
Last update:
a month ago
Updated by: