topic Re: Connection doesn't close - NPrinting June 2018 in Qlik NPrinting

Connection doesn't close - NPrinting June 2018

renuka_sasikumar — Wed, 25 Sep 2019 18:40:54 GMT

Hi,

Currently I am using NPrinting June 2018 and QlikView November 2017.

I have created some Task in NPrinting, when the reports get distributed & then the second task starts, the first connection doesn't get close automatically due to which the Server Memory is been utilized and remains open until I manually doesn't close it. (Major problem during Weekends, all connections remain opens & server gets hanged due to high utilization)

Like in NPrinting 16 we had an option of Close Connection when task ends, do we have such thing in the latest version.

Regards,

Renuka S

Re: Connection doesn't close - NPrinting June 2018

renuka_sasikumar — Mon, 20 Aug 2018 07:36:12 GMT

Hi lech_miszkiewicz‌,

Can you help me on this.

Regards,

Renuka S

Re: Connection doesn't close - NPrinting June 2018

Lech_Miszkiewicz — Mon, 20 Aug 2018 07:44:48 GMT

do you use QVP connection (server) or Local?

I highly recommend using QVP connection - just to avoid issues like this!

On the other hand inactive connections should close automatically (it is default setting and there is nothing you need to do)!

regards

Lech

Re: Connection doesn't close - NPrinting June 2018

renuka_sasikumar — Mon, 20 Aug 2018 07:52:39 GMT

Thank You for your prompt reply.

I am using Local connection (Mapped drive using below address)

\\xxxxxx\qlikview_apps\NPrint\QlikviewApp\xxx.qvw

Can you help me with the default setting, where I have to look for it.

Regards,

Renuka S

Re: Connection doesn't close - NPrinting June 2018

Lech_Miszkiewicz — Mon, 20 Aug 2018 07:56:31 GMT

That is what i thought. Local connections will always drain hardware resources as there is no control over it. I have mentioned it so many times already and i keep saying that QVP is the way to go.

regarding default setting:

you don't need to look for it. It meant to close connections automatically after job is finished. There is nothing we can configure - as nprinitng handles this automaticly.

Re: Connection doesn't close - NPrinting June 2018

renuka_sasikumar — Mon, 20 Aug 2018 09:00:39 GMT

The connection doesn't close automatically. It remains open when I see it on the next day.

Re: Connection doesn't close - NPrinting June 2018

cwolf — Mon, 20 Aug 2018 10:46:01 GMT

Hi,

For me, the use of qvp connections is not an option as they generate a high load on the QlikView servers that I do not want to have.

Therefore, I also use local connections.

To solve the problem with the hanging processes, I use a little powershell script (see attachment).

The script first stops the "Qlik NPrinting Engine" service (because it holds the connections). Kills all Qv.exe processes for the NPrinting service user (in my case domain\qlikvnpr) and start the engin service again.

The script requires administrative rights to execute and can be scheduled through the windows task scheduler at a time where no NPrinting tasks are scheduled.

But it is also not a problem if the script is executed when nprinting tasks are running. The NPrinting task scheduler automatically restarts the NPrinting tasks when the engine is online again.

Re: Connection doesn't close - NPrinting June 2018

Lech_Miszkiewicz — Tue, 21 Aug 2018 00:15:21 GMT

Hi Christian,

that requires you to have quite a lot of "hardware" on your NPrinting server.

If you did not want ot use QVP you could always setup a Claster to loadbalance resources and still use qlk server benefits (managing hardware via qvs, data caching, warm starts etc...)

regards

Lech

Re: Connection doesn't close - NPrinting June 2018

pradosh_thakur — Tue, 21 Aug 2018 18:32:59 GMT

Hi christian,

As Lech already mentioned qvp is the way to go.

May be you could use taskkill qv.exe in a batch file to kill if any unwanted connection are open instead of stopping the engine. Sometimes when connection gets stuck and qvw can't be used for any other processes in qmc, i use this.

Re: Connection doesn't close - NPrinting June 2018

Lech_Miszkiewicz — Wed, 22 Aug 2018 01:39:02 GMT

Hi Pradosh,

TRUE, QVP or CALSTER connections are my suggestion, and they solve a lot of performance issues around memory leaks and hardware management. The drawback however is report execution speed.

In NPrinitng 16 this was "flying", however in NPrinitng 17 it can be slow - which frustrates me a lot and i have been very vocal about it. Still - in my deployments i am using QVP;s

Christians solution is not bad - the reason i don't use it is that is not Qlik supported and as a partner providing solution to clients i cannot support it!

cheers

Lech

Re: Connection doesn't close - NPrinting June 2018

renuka_sasikumar — Wed, 22 Aug 2018 05:12:32 GMT

ok, but about creating a QVP connection.
In my scenario there are two server (load balancing) & applications are on Server A in a different folder say like NPrinting app, so here I would like to how do I create a QVP connection.

I used vp://server.domain/xyz.qvw for creating QVP connection.

I tried doing it see the below error.

Re: Connection doesn't close - NPrinting June 2018

renuka_sasikumar — Wed, 22 Aug 2018 05:41:05 GMT

Re: Connection doesn't close - NPrinting June 2018

Lech_Miszkiewicz — Wed, 22 Aug 2018 05:54:10 GMT

did you read help document? If not - please start from there!

https://help.qlik.com/

If you have Qlik Claster you can follow instructions for Claster connection:

https://help.qlik.com/en-US/nprinting/June2018/Content/GettingStarted/HowCreateConnections/Connect-to-QlikView-docs.htm

help documents provides possible resolutions to errors you are experiencing

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.

Re: Connection doesn't close - NPrinting June 2018

pradosh_thakur — Wed, 22 Aug 2018 06:00:42 GMT

True Lech. But once clients gets a taste of ON-demand feature they want it in most of the cases.and On-demand is not possible in local connection.

Re: Connection doesn't close - NPrinting June 2018

Lech_Miszkiewicz — Wed, 22 Aug 2018 06:15:09 GMT

I agree and understand - however....

On-demand is not related topic to this thread and original question.

We are trying to answer hardware capacity question here - not the functionality of each connection types

Re: Connection doesn't close - NPrinting June 2018

cwolf — Wed, 22 Aug 2018 09:45:38 GMT

Hi Lech,

sorry, but I have no any problems with NPrinting. My NPrinting environment works stable and with a good performance.

Killing the processes is not a problem for me. It's only a workaround until the functionality is implemented in the NPrinting engine itself. And I'm sure it will come.

It is basically the same as with monthly triggers. Until the june update, a workaround was needed to have monthly triggers. And now they exists in Nprinting.

- Christian -

Re: Connection doesn't close - NPrinting June 2018

Lech_Miszkiewicz — Wed, 22 Aug 2018 23:08:56 GMT

Hi Christian. Like i said in one comments above i believe your solution is as good as any other working solution.

I am not trying to convince you to change your setup, but i tried to share my knowledge around Qlik supported configurations which will solve problem described in this topic

Regards

Lech

Re: Connection doesn't close - NPrinting June 2018

renuka_sasikumar — Thu, 23 Aug 2018 05:58:11 GMT

The connection doesn't close automatically, & I tried using the batch file to kill the task that is also not working.

I have to end the process manually by the Task Manger.

Any other option to end the connection after report generation.

Re: Connection doesn't close - NPrinting June 2018

Lech_Miszkiewicz — Thu, 23 Aug 2018 07:45:02 GMT

There must be something buggy there

I don't know what else i can suggest, you might want to talk to Qlik support or have Qlik consultant looking at it in house or via conf.call

I am running out of options and advices.

Again - having QVP connection would not hurt, even if connection would be left alive, since the workload would be sitting on Qlik server....

Re: Connection doesn't close - NPrinting June 2018

renuka_sasikumar — Thu, 23 Aug 2018 09:08:43 GMT

Thank You very much lech_miszkiewicz‌

But here I can't go with QVP, so I don't have option about it.

As said I will log a ticket with Qlik Support, will reply if I get the solution.

Regards,

Renuka Sasikumar.