NPrinting requires a Dedicated NPrinting server service account
and a dedicated license/token (Qlik Sense) or Named CAL/Desktop license (QlikView) which is assigned to its account. Some systems may be installed with identical accounts across the NPrinting services and QlikView or Sense services. The latter is not a supported configuration.
This article describes how to configure a dedicated NPrinting Server service account.NOTE:
- This article and information therein apply to ALL versions of NPrinting Server
- Sharing service user accounts between different NPrinting and QlikView servers is is NOT a supported configuration.
- One Service Account can be used for the NP Engine, NP Scheduler and NP Web Engine services on the 'Same' NP server only. See image below.
- Qlik Sense: A dedicated NPrinting service account should also be used with Qlik Sense implementation with NPrinting. This is due to the nature by which NPrinting service share's/borrows a token or license. If a QS token or analyzer license is not explicitly assigned to a dedicated NPrinting service account and the Qlik Sense service account is used to run the NPrinting services, this may cause performance problems and issues for both Qlik Sense and NPrinting. Therefore, a dedicated NPrinting service account should be used if you are experiencing issues connecting to Qlik Sense where the NPrinting services and Qlik Sense services are sharing the same domain user account to run their respective Windows services.
If more than one
For additional support resources, please visit the links below:
- If you are using a service account that is in daily use by another QlikView user or QlikView server, this will cause contention issues due to the attempt to share a user QlikView CAL between two separate server environments. Doing so will inevitably cause failure in normal NPrinting operation.
- Expected behavior of a shared account is that NPrinting Schedules and Tasks get hung up in the background server service due to contention between the QlikView services and the NPrinting services which are sharing the same (domain) service user account.
- QlikView Personal Edition is not supported. A valid User CAL must be assigned to the NPrinting service account or QV desktop license installed while logged on as the NPrinting service account.
- Default user rights assignments have been modified or changed by local or network active directory group policy.
- If a QS token or analyzer license is not explicitly assigned to a dedicated NPrinting service account and the Qlik Sense service account is used to run the NPrinting services, this may cause performance problems and issues for both Qlik Sense and NPrinting. See related article: Qlik Sense April 2018 and later- Service account getting "You cannot access Qlik Sense because you have no access pass"
- Therefore, a dedicated NPrinting service account should be used to mitigate issues connecting to Qlik Sense from NPrinting where the NPrinting services and Qlik Sense services are sharing the same domain user account to run their respective Windows services.
: Upgrading to NPrinting June 2019 or later versions removes the necessity for a dedicated user account and an assigned "Token" or "Analyzer" license.
(NOTE: With QVP NPrintng Connections the QV desktop installed on the NPrinting Server MUST be the same version as the QVS QlikView Server. You will experience NP Verification errors if they are not the same version).
To ensure NPrinting Connections work correctly, please take the following steps:
1. Create a dedicated account, which:
- is a domain account that is a member of the local Administrators group on the NPrinting server and the QlikView Administrators group on the QlikView server
- has a manually assigned CAL from a PRODUCTION ONLY QlikView Management Console (QMC) or a locally installed QlikView desktop license. (a QlikView TEST server does not issue valid user CALs for use with NPrinting Production reporting.)
- has 'log on as a service' user rights assignment applied to it
- is not be shared with any other NPrinting server environment or QlikView server. Each NPrinting Environment MUST have its own NPrinting server service account
- NP (Server/Engine) DEV - NPsvcAccount1
- NP (Server/Engine) TEST - NPsvcAccount2
- NP (Server/Engine) PROD - NPsvcAccount3
Or In a Single NPrinting Environment with Multiple NP Engines (Example PROD Environment with 3 NP Engines)
- NP (Server/Engine) PROD - NPsvcAccountPROD1
- NP (Server/Engine) PROD - NPsvcAccountPROD2
- NP (Server/Engine) PROD - NPsvcAccountPROD3
- is from the same domain that the NPrinting Server is a member of.
- has access to all network resources where NPrinting related files are located if for example output, temp, qvw, report template, recipient folders are stored on the network. But please note that the use of Mapped Drives with NPrinting is not support. You must you UNC network paths if you must access network resources with NPrinting. ie: \\servername\sharename\nprinting\templates is a valid UNC shared path. Mapped drive such as Z:NPrinting\Templates is not supported.
Note: NPrinting does not support the use of multiple domain environments. Specifically, the NPrinting service account used to run the NPrinting server service must be a user account that is in the same domain that the NPrinting server is a member of. The error in Figure 1.3 below may result when an external domain user account is used to install NPrinting with.
Manually assign a QlikView Named User CAL to the NPrinting service account and then:
- Log onto the NPrinting server as the dedicated NPrinting service account
- Open the QlikView desktop and do a 'File>Open in server' to the Production QlikView server to pull down the manually assigned CAL This steps effectively licenses the QV desktop on the NPrinting server
- Navigate to the QVW you wish to connect to
- If you cannot view the QVW, then you need to check that you have added the NP service account to the:
- Local administrators group on the NP server
- QlikView Administrators group on the QlikView serer
- If you have QlikView Publisher, publish the QVW to the NP domain user service account
If using a QlikView desktop CAL rather than a CAL from the QMC
- Log on to the NP server
- Open the QlikView desktop
- Go to settings/user preferences/license tab
- Click 'Change' to apply the license key and control number
Figure 1.1 Configure Desktop License
- If making QVP connections from NPrinting, please ensure the correct permissions have been applied to the NP server service account via report distribution task in the QMC as shown below in order to allow the NP service account to make QVP connections.
Figure 1.2 Configure/Manually Assign a Named CAL for the NP service account (do not allow the NP service account to manually lease a Named or Session CAL)
- NOTE: The NP service account, built in Windows 'Network Service' and 'local' accounts should not have any default user rights assignments removed from it via Active Directory Group Policy. In some large network enterprises, user rights assignments are removed or changed for service account. User rights assignments must remain in their default state to ensure that Qlik NPrinting can be installed correctly and work as designed. Changing/removing any default user assignments via local group policy editor or through global network group policy management will adversely impact the installation and running of the NPrinting server environment. If policy is changed, the following similar to the one below may occur during setup and installation. See figure 1.3:
3. File access
Finally, the NP service account must have network folder and file full permission access to all network file/folder locations for which it must connect to ie: such as output file locations on the network etc. Failure to provide the NP service account with adequate computer and network permissions will result in data reload and task hanging and report generation failures. Also as a reminder if using QlikView Publisher, the QVW must be published to the NPrinting dedicated service domain user account in order to allow NPrinting Connections to that QVW on the publisher server.
- A dedicated NPrinting service account should be used with Qlik Sense implementation with NPrinting if you are running instances of NPrinting prior to June 2019 release of NPrinting. Not required if you are running June 2019 or later releases of NPrinting
- A token (original license model) or analyzer license (new license model)
: do NOT
use a Professional License as this will cause connection, report preview and task failures. Use 'analyzer' license where applicable
- This is due to the nature by which NPrinting service share's/borrows a token or license.
- If a QS token or analyzer license is not explicitly assigned to a dedicated NPrinting service account and the Qlik Sense service account is used to run the NPrinting services, this may cause performance problems and issues for both Qlik Sense and NPrinting. See related article Qlik Sense April 2018 and later- Service account getting "You cannot access Qlik Sense because you have no access pass"
- Therefore, a dedicated NPrinting service account with an allocated 'Token' or 'Analyzer' license should be used to mitigate issues connecting to Qlik Sense from NPrinting where the NPrinting services and Qlik Sense services are sharing the same domain user account to run their respective Windows services.