Qlik Npriting Error: Only a single Instance of QlikNpriting Designer Can Run

[Purushothaman]

Hi Experts,

I have this error keep populating, though I have checked Only One designer is running in Windows. Don't know how to resolve it. Any one can help.

Thank you!

[andries_bos · Accepted solution]

Having excel already open and  in edit mode, will also cause the Nprinting designer to crash prior to opening. In my opinion the designer  is not stable at all as I quite frequently had to kill the process manually within task manager. 

The process to kill  could not be found as a process but only within the taskmanager details tab : NPrintingdesigner.exe 

Compared to the old v16 Nprinting that Qlik bought and turned into their own web version made NPrinting al least 10x slower withinin all designing actions !

[Ruggero_Piccoli]

Hi @andries_bos ,

Please avoid commenting so old conversations, start a new one instead with the details of your issue and the correct version of Qlik NPrinting you are using. Be sure you are using a supported version, the latest is better because you will benefit from all solved issues. 

You can open a single instance of Qlik NPrinting Designer at a time and it is visible in the Task Manager:

The process name is NPrinting Designer.exe and it is visible in the Details tab of the Task Manager. If it crashes during the editing of a Microsoft Office template you have to kill also the related process: Word, Excel, or PowerPoint.  In supported versions, the Designer is very stable and can be used with other Microsoft Office processes opened. What version of Qlik NPrinting are you using?

Qlik NPrinting Designer of 17+ series is the same as QlikView NPrinting 16 a part of the needed updates to make it compatible with the web version. User Interface and template editing methods are the same.

Best Regards,

Ruggero

[andries_bos]

Still using Version: 21.14.4.0 

An installed version/update once installed is not (easiliy) downgradable and following the Qlik support team's suggestion 'upgade first' pushed me into a lot of serious problemsfor a logn time  that only was solved only after 3 months  : not a situation  I was very happy with...

From then 'if it aint broken don't fix it.. helped me from then

I came from v16 and are still not happy at all for the performance of the web version of nprinting,

Where adding  a new report would have taken me 5 minutes  in total within the old Nprinting windows program, this web version would take me at least 30 minutes:  I have to reload metadata that takes me 15 minutes (yes, my reports are still huge) whereas in the old Npritning this would have taken me 30 seconds loading all new chars... Previewing a report took me 1 munte in tghe old nprinting ; the new takes somtimes 5 minutes...

Also ALL connections have to be reloaded and valid editing one report : all items that worked fluently within the old (windows program) nprinting (when qlik was not the owner)

[Ruggero_Piccoli · Accepted solution]

Hi,

Metadata reload was mandatory also on QlikView NPrinting 16 and it was single-tread, single-engine, and file based whereas the 17+ is multi-tread, multi-engine, and stores data in a database. If your installation of Qlik NPrinting 17+ is slower than 16 I suggest you investigate the usage of hardware resources. Maybe you have to increase them.

If you are connecting to a QlikView server check also its usage of hardware resources. If you are using local connections move to a server one.

There are also optimizations suggested to speed up the creation of huge reports already shared multiple times here in the community. Those optimizations could be useful in your scenario.

QlikView NPrinting 16 is out of support since March 2020. 

Best Regards,

Ruggero

[David_Friend]

@Purushothaman if that solution from Frank helped out be sure to click on the 'accept as solution' thanks!