Qlikview does not close after Nprinting report runs

[braham]

Afternoon,

We have just installed NPrinting on the same server as Qlikview. When running a report, the report is mailed to the user, but the instance of Qlikview that ran the report remains open. It shows up in the message from Interactive Services Detection window. You have to manually close the Qlikview instance after viewing the message in Interactive Services Detection window. Qlikview and NPrinting were installed and run using the same local services account.

What could be preventing Qlikview from closing and how do you resolve the issye.

Thanks

Braham 

[marcus_malinow]

In NPrinting 16, in your Report task you can set the option 'Close connection when task ends'

[braham]

Thanks for the response Marcus, we are using NPrinting  v18.29. Through the web interface I cannot find any setting that allows me to specify what you are suggesting 

[marcus_malinow]

Ok I'm guessing you have set up your connection as a local connection (by file name) rather than a server connection. Changing it to a server connection should work

or

If this is not an option, it looks like others have had the issue before you, and here's the solution:

https://qliksupport.force.com/QS_CaseWizardKnowledgeArticle?Id=ka5D0000000TO7vIAG

[braham]

Thanks Marcus for the input on this issue. I have tried changing the config file as suggested in the attached article and that makes no difference. I have also tried to run the report via a local connection as well s via the server. In both cases The message shows the Qlikview model that it is reporting on and I have to close the model in the message box. 

[Lech_Miszkiewicz]

first of all go to https://help.qlik.com and read documentation. Make sure you read requirements (system and architecture) and make sure you meet all of them.

There is a lot of requirements and one of them is to not install NPrinting on the same machine. I have setup many NPrinitng instances and had many problems initialy when they were setup on the same machine. 

Basicly now you are running unsupported configuration and there can be many reasons why NPrinting is not behaving as intended.

The other thing is that NPrinting handles Qv.exe proceses internally. I noticed that some sessions remain open for some time but eventually they close. Indeed using qvp server connection is in my opinion best solution as it will not consume resources on dedicated NPrinitng box (once you have it) and it will perform a lot more stable -also you will not have to rebuild metadata after every qvw refresh, since qvp connection does not require it.

to start with i suggest to get a better understanding how Nprinting infrastructure needs to be configured and then once this is done properly i would worry about "zombie" qv.exe sessions.

cheers

Lech

[Ruggero_Piccoli]

Hi,

Installing Qlik NPrinting Server or Engine in the same machine (phisical or virtual) of QlikView Server or Qlik Sense Server is not supported. You can install Qlik NPrinting Server and Engine in the same machine. For more details refer to the thelp site linked by Lech.

You must install QlikView Desktop in the same machines where you installed Qlik NPrinting Engine. More details on the help site.

You did not specify but I desume you are speaking about Qv.exe process that are the processes of the QlikView Desktop. It is normal that you find one or more Qv.exe processes open after, for example, report generation. I suggest you to keep them alive and not to manually close. This will increase report generation performances.

When report generation starts and ioof you have at least one connection to a QlikView document (local or server) Qlik NPrinting opens the document in a numbers of Qv.exe process that depends on the hardware resources of the computer. The same document is opened more times to speed up the report generation. When the generation is finished Qlik NPrinting decide if it is better to keep or to kill the Qv.exe processes. In general at least one Qv.exe with the document used in report production is keep alive. Qlik NPrinting supposes that you would generate other reports based on the same connection in the future, so when a new report generation starts again you have not to wait the document opening time because it is already opened and report generation starts immediately. If you manually kill the Qv.exe process you will need to wait the document opening again. If Qlik NPrinting needs to generate reports based on a different connectio and there are not enough hardware resources the previous opened Qv.exe proccess now unuseful will be automatically killed.

Best Regards,
Ruggero
---------------------------------------------
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.

[MItch_01]

Ruggero,

I understand your answer but it does not help in our situation. We have a dashboard that reloads every 10 minutes and Nprinting occurs once a day from the server connection to this dashboard. As you describe the system believes it would be better to leave the NPrinting connection open. However, this causes conflicts with the next reload. This requires manual intervention. We can live the inefficiency of the connection needing to be opened daily as long as it does not stay open and interfere with the next reload. So how do we ensure that the connection is closed after NPrinting?

Thanks for you assistance on this.

[Ruggero_Piccoli]

Hi,

You can:

- create a connection to a QlikView Server

or

- create a connection cache reload task every 10 minutes. This force the connection to be closed and reopen (all Qv.exe processes are killed).

Connections are keep opened (and Qv.exe processes running) to improve performances. 

I also suggest to create a QlikView document only for reporting reasons. In it you keep only data and charts that are needed to generate the reports. So you speed up the report generation.

Best Regards,

Ruggero