Collaborate with over 60,000 Qlik technologists and members around the world to get answers to your questions, and maximize success.Join Us
The first thing to check is that the connection in NPrinting is pointing to the Qlik sense Default proxy.
Go to Qlik Sense QMC > Virtual Proxies. Is there a prefix for the default proxy?
If so, be sure that this has been added in the NPrinting connection. The "Proxy address" in the connection should look like
If the NPrinting connection is correct, the problem may be related to a known issue. Instead of restarting the NPrinting services in the event of a error being reported when adding an image perform the workaround below.
If that works, then we have a setting recommended to be entered in the scheduler.config file (ProgramFiles\NPrintingServer\NPrinting\Scheduler):
1. Stop NPrinting Scheduler and NPrinting Engine(s) services
2. Open scheduler.config (in scheduler installation folder) file
3. Add the following line within the appSettings section (the line just before the closing </appSettings> is ok):
<add key="force-unused-resolvers-closure-policy" value="1" />
4. Save the changes (pay attention that the file should be named scheduler.config, not scheduler.config.txt)
5. Restart the scheduler service and the engine service(s)
What this key is for?
Per R&D, it essentially tells the scheduler to request a "close all Qv/Sense connectors (that we call resolvers)" to all NPrinting Engines when there are no more requests to resolve.
This forces the engine to shutdown all connections to QlikView/Qlik Sense servers, usually freeing up some RAM on the NP engine machines but most importantly avoiding some session timeout related issues.
Items to be aware of:
Sessions are closed immediately when there are no more requests to resolve. If a user will ask for a preview immediately after this will force to start a newly created connector/resolver and this could take several seconds (usually more on Qvs connections than on Sense ones).
The option is lost when an upgrade is performed
Please NOTE : R&D recommends avoid using it on NPrinting + QlikView installations because it is very rarely needed and the impact on performance could be noticeable. On the contrary usually not a noticeable degrade with Sense (and if it happens it is due to a very high number of Sense apps in the Sense server and/or slow internet connection).
Search Qlik's Support Knowledge database or request assisted support for highly complex issues.Submit a case
Experiencing a serious issue, please contact us by phone. View phone numbers and hours by region.