Skip to main content
Announcements
Defect acknowledgement with Nprinting Engine May 2022 SR2, please READ HERE
cancel
Showing results for 
Search instead for 
Did you mean: 
exfosteve
Partner - Contributor III
Partner - Contributor III

Qlik Nprinting Setup

First time deploying Nprint.  I have a single server running qlikView Novmber 2017 (12.2 SR6) and nPrint June 2018 (18.19.6.0).

Server Size:  2 CPU (32 total threads), 64GB RAM, Windows Server 2016

I only 4 QVWs, with 3 of them averaging 100MB in size and 1 about 650 MB. (about 20 tabs per QVW)

All qlikview processes run under  QVADMIN

All nprint prcesses run under NPADMIN

I've followed all the setup instructions I've found on the different sites.

QlikView is extremely responsive, but nprinting is incredibly slow.  I have one sheet ppt report with 1 table, and publish task has been running for over 2 hours. CPU on the server is at 1%,  memory utilization less than 15%.

Any help would be great. 

1 Reply
Lech_Miszkiewicz
Partner Ambassador/MVP
Partner Ambassador/MVP

First of ALL - foreget about unofficial documents - always focus on official ones:

https://help.qlik.com/

so if you follow all instructions how did you end up installing it all on 1 server?

https://help.qlik.com/en-US/nprinting/June2018/Content/DeployingQVNprinting/Supported-unsupported-co...


You are running unsupported configuration! QlikView and NPrinitng need to be installed on separate machines.

Unsupported configurations

  • Qlik NPrinting 16 and Qlik NPrinting Designer June 2017 or later cannot be installed on the same computer.
  • Qlik NPrinting Designer June 2017 or later cannot manage Qlik NPrinting 16 projects (.nsq files), but you can import individual Qlik NPrinting 16 reports. See: Migrating report templates from older versions of Qlik NPrinting.
  • Qlik NPrinting Server 16 and Qlik NPrinting June 2017 (or later) Server or Engine cannot be installed on the same computer.
  • Qlik NPrinting Engine and Server and Qlik Sense Server should not be installed on the same computer.There are no known incompatibilities between these two products, but in a production environment, Qlik NPrintingshould be installed on a separate computer (virtual or physical) from Qlik Sense because Qlik NPrinting Engine and Server will consume all the available resources of the computer they are installed on. This may lead to Qlik Sensecrashing because of lack of resources.
  • Qlik NPrinting Engine and Server should not be installed on the same computer where QlikView Server or QlikViewPublisher are installed.There are no known incompatibilities between these two products, but in a production environment, Qlik NPrintingshould be installed on a separate computer (virtual or physical) from QlikView Server or QlikView Publisher because Qlik NPrinting Engine and Server will consume all the available resources of the computer they are installed on. This may lead to QlikView Server or QlikView Publisher crashing because of lack of resources.


Also read about setup and performance of NPrinting when it comes to no of CPU cores - looks like you missed that one too


https://help.qlik.com/en-US/nprinting/June2018/Content/DeployingQVNprinting/Performance.htm

Once you have supported and optimized configuration we can come back to Performance tuning, app performance tuning and design.

If you have never done it before - there is a long learning path ahead as NPrinting development needs to be taken into consideration during Qlik View application development.

For example:

https://help.qlik.com/en-US/nprinting/June2018/Content/GettingStarted/HowCreateConnections/Connect-t...

Unsupported QlikView documents

Before you create a connection to a QlikView document, ensure that the QlikView document does not use any of the following:

  • alternate states
  • sheet and document triggers
  • Always one selected list box property
  • WebView modeWebView mode must be turned off. See: AJAX/WebView.

Qlik NPrinting cannot modify or remove these options. As a result, Qlik NPrinting may not have access to the entire dataset of the connected QlikView document during the cache generation process, and while generating reports.If you want to use QlikView documents with these unsupported features, do the following:

  1. Create a copy of the QlikView document.
  2. Remove all alternate states, sheet and document triggers, and the Always one selected list box property from the new QlikView document. Make sure that WebView mode is turned off.
  3. Use the copied QlikView document for reporting purposes.

cheers


Lech

--------------------------------------------

When applicable please mark the appropriate replies as CORRECT https://community.qlik.com/docs/DOC-14806. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads as HELPFUL if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads as HELPFUL if you feel additional info is useful to others.

cheers Lech, When applicable please mark the correct/appropriate replies as "solution" (you can mark up to 3 "solutions". Please LIKE threads if the provided solution is helpful to the problem.