A large number of qv.exe (QlikView) and or QS reporting_web_renderer.exe (Qlik Sense) processes (i.e. Publish or Reload tasks) are running on server freezing it due to usage of all available memory (thus insufficient memory) on the NPrinting Server (Engine) computer.
NPrinting Scheduler uses an algorithm to manage the number of processes (QV.exe or QS reporting_web_renderer.exe) enabled when connecting to QVW documents or QVF apps.
Since NPrinting is designed to use all the available resources (one .exe per core/logical processes) on the server, in some scenarios it may be necessary to set a temporary limit until additional RAM can be added. Please note that if RAM use issues are observed with QlikView connections to local .qvw files (stored on the NPrinting server or a share), RAM use can significantly be decreased by using QlikView Server connections (via qvp protocol) which would offload most of the RAM use to the QlikView Server.
Environments:
Resolution:
Managing QlikView and Qlik Sense processes
- Stop the Qlik Nprinting Engine Service ( "on all nodes you have installed it ")
- Backup of %ProgramFiles%\NPrintingServer\NPrinting\Engine\engine.config ( check the right path if you have a custom install )
- Open with text editor %ProgramFiles%\NPrintingServer\NPrinting\Engine\engine.config
- Next, inside the the app setting section of the engine.config file "<appSettings> .... </appSettings>"
- Add a row with the number of resolvers above the </appSettings> closing tag as shown below:
<add key="resolvers-count" value="2" />
</appSettings>
- These sample settings allow two .exe processes to run concurrently.
- Note that it is not recommended to allow more than a value of 16 due to ensure maximum performance and there should be sufficient system RAM to support the use of 16 resolver/processes with NPrinting. More related information found under Performance Guidelines.
<add key="resolvers-count" value="16" />
- Save the config file
- Start Nprinting Engine
Related Information
