Nprinting Connection Issue

[9717023463]

Hi,

I am using nprinting version 17.6.0 and my application size is 450 mb which has been developed in qlikview.

When I try to make the connection between qlikview and nprinting it takes more than 2.5 hours to be successfully connected.

Though the CPU and Memory utilization is merely 4% and 5% at a given point of time.

There is no section access on the application.

The RAM in the server is 256 GB.

Both nprinting and qlikview are on the same serrver.

Any suggestions on how the connection can be made fast?

[Daniel_Jenkins]

Hi Shashank,

When you say "...more than 2.5 hours to be successfully connected" I assume you mean for metadata generation? If so, 450 mb is not big, however, it's difficult to troubleshoot without the QVW file. Anyway, here are some things to consider:

1. QlikView Server & NPrinting on the same machine is not supported and can lead to issues. You will need to separate them and reproduce the issue if you want support. See point 5 under Unsupported Configurations here: https://help.qlik.com/en-US/nprinting/June2018/Content/DeployingQVNprinting/Supported-unsupported-co...

2. Log in to the NPrinting server machine as the service account used to run the NPrinting Engine service. Make a backup copy of your QlikView document. Open the QlikView Document in QlikView Desktop. Remove all selections. Remove Always One Selected Value option from all listboxes. Go from sheet to sheet and check which objects are taking a long time to render. If you find any, remove them. Test the NPrinting Connection metadata generation again.

If that resolves the issue revisit the design of the expressions used in the charts you removed. If you are still unable to resolve the issue, open a Support case (make sure you can reproduce the issue after separating NPrinting & QlikView or you will be asked to do that first anyway).

HTH - Daniel.

[Ruggero_Piccoli]

I agree with Daniel and I also suggest to update your installation to latest version to take advantages to all the optimization developed between 17.6 and June 2018.

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.

[Anonymous]

Hi,

I had a similar issue and the only workaround I found was to limit the size of the application below 300mb. The connection reload time increased exponentially when the size of the document exceeded somewhere between 300 and 400 mb. It is possible that this was an environmental issue but after substantial troubleshooting no root cause was found.

Br.

Saska Saarioja

[Ruggero_Piccoli]

Hi,

I think it is an environment issue too. Check the page https://help.qlik.com/en-US/nprinting/September2018/Content/NPrinting/DeployingQVNprinting/Performan... to evaluate if you have enought hardware resources for your installation.

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.