Skip to main content Skip to complementary content

Licensing Qlik NPrinting

Qlik NPrinting can be installed and configured to connect to QlikView documents or Qlik Sense apps. The licensing requirements and procedures are different depending on if you connect Qlik NPrinting to QlikView or Qlik Sense.

Information noteQlik NPrinting is an on-premise reporting add-on product for Qlik Sense on Windows or QlikView on Windows.

You do not need to activate licenses for Qlik NPrinting Designer or Qlik NPrinting Engine. They are activated automatically based on license information from the Qlik NPrinting Server. See: Licensing Qlik NPrinting Server .

Contact Customer Support for more information about customer license codes.

Qlik NPrinting with QlikView

To start the Qlik NPrinting service and connect to QlikView, you must have one of the following:

  • A named user Client Access License (CAL) that is manually assigned to the Qlik NPrinting Engine service user active directory account, on the QlikView Server.
    Information noteA valid named user CAL from a production QlikView Server must be used for the Qlik NPrinting Engine service user account. If the CAL from a test QlikView Server is used, it will cause personal edition to appear in the QlikView Desktop title bar, and it will not work with Qlik NPrinting.
  • A local QlikView Desktop license.

To connect Qlik NPrinting Server to QlikView a fully licensed version of QlikView Desktop is required. You can activate QlikView Desktop by inserting a license code and control number, or by manually assigning a named user CAL from a QlikView Server.

Dynamically leased licenses and Personal Edition are not supported. We do not recommend using dynamically assigned leased licenses, because when a dynamic leased license expires the Qlik NPrinting service stops working.

A user account with a leased license needs administrative privileges and permission to run as a service. The user account must be specific to the Qlik NPrinting service. Do not use the same account for other purposes such as remote desktop connections or server login. See: Activating a QlikView Desktop license.

If you are configuring multiple Qlik NPrinting Servers you must create a Windows account for each one.

QlikView Desktop licenses for Qlik NPrinting Engine

You can use a license code and control number (local license) or assign a Named CAL from your QlikView server. You must use a different Windows user for each instance of the Qlik NPrinting Engine service.

A Named CAL license, taken from a QlikView Server, is valid only for a single QlikView Desktop user. In the case of a multiple Qlik NPrinting Engine installation, you must set a different Windows user and a different QlikView Desktop Named CAL license for each Qlik NPrinting Engine. If you use the same QlikView Desktop Named CAL license two or more times, the QlikView Server will disconnect all QlikView Desktops but one, and report generation will fail.

We do not recommend using shared licenses (also called dynamically-assigned CALs) because when Qlik NPrinting opens the local QlikView Desktop, the license must be active or the report generation process stops. If you use assigned CALs, you need to connect the QlikView Desktop to the QlikView Server at least one time, at the beginning, using the same Windows user and computer as the Qlik NPrinting Engine service.

Qlik NPrinting with Qlik Sense

To start the Qlik NPrinting service and connect to Qlik Sense, you must have the following:

  • Qlik Sense certificates exported without password information
  • User account with RootAdmin privileges in Qlik Sense

To connect Qlik NPrinting to Qlik Sense you must have Qlik NPrinting Server and at least one Qlik NPrinting Engine installed and activated.

Qlik Sense certificates must be installed on each computer where a Qlik NPrinting Engine is installed. See: Connecting Qlik NPrinting with Qlik Sense.

The Qlik NPrinting user that creates the connection to Qlik Sense must have RootAdmin authorization in Qlik Sense.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!