Article Number: 000007756 | Last Modified: 2018/06/12
Description
Keep in mind that a best practice would be to schedule your NPrinting Jobs to run in 'off hours' because you will typically have QlikView and QlikView NPrinting Developers accessing the server during office hours.
If preferred, the QlikView NPrinting client can be installed separately on a separate computer. But you must ensure that you install a copy of the QlikView Desktop and a copy of Microsoft Office as well. If this is done, you should have enough physical resources (ram and cpu) to run Qlikview Desktop client and Microsoft Office on that machine. The QlikView Desktop client must also receive a QlikView license as well to prevent the QlikView Personal Edition message from appearing on the screen. QlikView NPrinting itself uses very little resources.
Please use a dedicated QlikView Desktop license with your QlikView NPrinting service account which is used to run the QlikView NPrinting service. This can be assigned from the QlikView Management Console. This will mitigate any downtime cause by the loss of a leased QlikView license. Note: This will only work if QVP connection is used for the Meta Data in Ver. 17
QlikView NPrinting user/service account requires:
Leased License: leased licenses may expire so if a leased license is lost, then QlikView NPrinting connections to the QVWs on the QlikView Server will no longer be possible until the QlikView NPrinting service/user account can re-lease a license.
A Named CAL License: Manually assigning a QlikView license to the NPrinting service/user account will dramatically mitigate or issues connection to QVWs on the QlikView Server.(This will only work if QVP connection is used for the Meta Data in Ver. 17)
A Local QlikView License: Assigning a local license would effectively remove any issues with connecting to the QVWs on the QlikView Server
Environment: Qlik Nprinting 16 and 17
Get Answers
Find Answers
Qlik Community
Collaborate with over 60,000 Qlik technologists and members around the world to get answers to your questions, and maximize success.
Experiencing a serious issue, please contact us by phone. For Data Integration related issues please refer to your onboarding documentation for current phone number.