Qlik Community

Qlik NPrinting Discussions

Discussion Board for collaboration on Qlik NPrinting.

Not applicable

NPrinting cache not refreshing after reload of apps

Hi,

I have installed NPrinting 17 SR1 and I still have the problem of the connection cache not being generated after a reload of jobs on the Qlikview server. This makes the product completely useless for sending out reports since they only contain old data. Has anyone experienced this and found solution?

Regards

10 Replies
gpr
Contributor III

Re: NPrinting cache not refreshing after reload of apps

Hi,

unfortunately at the moment there is no automatic way to handle document reload. This feature is in development roadmap and will be introduced in future releases. In the meantime there is a "dirty" workaround:

1) Let's say that you have an already "Generated" connection and you want to change the related QV document (add or remove objects or data)

2) Open the related QV document from QlikView Desktop

3) Make desired changes

4) Save and close the document

5) Edit the related NPrinting connection changing the document path to a wrong one (e.g. "NP Demo.qvw" -> "NP Demo1.qvw")

6) Save the connection

7) Wait until the connection status changes into "No engines are working" and the cache status to "Error: The request was purged due to connection errors".

8) Edit the NPrinting connection again fixing the document path (e.g. "NP Demo1.qvw" -> "NP Demo.qvw").

9) Save the connection

Not applicable

Re: NPrinting cache not refreshing after reload of apps

Hi,

I got the same advice from Qlik support,  tried it out and it seems to work sometimes and sometimes not.

Regards

Emmanuelle-Bustos
Valued Contributor

Re: NPrinting cache not refreshing after reload of apps

We have the same issue with NP 17.2 but only with Sense app connections, with QVW local file it works fine, somebody has a fix?

aadil_zyme
Contributor

Re: NPrinting cache not refreshing after reload of apps

I am also experiencing the same issue.

qs-np-connection-error.png

Qlik.NPrinting.Engine17.2.0.0Qlik.NPrinting.Engine.Consumer.EngineConsumer20161004T063610.978-07:00ERRORNPRINTSERVER00000000ERROR Error opening the document 'navigator=qliksense;proxyurl=https://SENSESERVER/;appid=eead9ace-8ad4-468a-8630-363bc6dc19b6;identity=SENSESERVER\SENSEADMIN' \n InnerException: An exception was thrown while invoking the constructor 'Void .ctor(Engine.Navigator.QlikSense.QlikSenseConnectionString, System.Collections.Generic.IEnumerable`1[Engine.Navigator.QlikSense.ISenseNavigatorFactory])' on type 'QlikSenseContentNavigator'. ---> The remote server returned an error: (403) Forbidden. (See inner exception for details.) \n Inner-innerException: The remote server returned an error: (403) Forbidden. \n Inner-inner-innerException: None. \n ...in  connection with id: 339c5eeb-1517-4f71-a9df-cc68f01fa824 connectionString : navigator=qliksense;proxyurl=https://SENSESERVER/;appid=eead9ace-8ad4-468a-8630-363bc6dc19b6;identity=SENSESERVER\SENSEADMIN

I am running Nprinting 17.2 / Qlik Sense 3.0

Anyone have a solution.

evgeniya89
New Contributor II

Re: NPrinting cache not refreshing after reload of apps

I have a same problem.Have you found a solution?

Employee
Employee

Re: NPrinting cache not refreshing after reload of apps

Hi,

Re-install the Qlik Sense certificates & try again. https://help.qlik.com/en-US/nprinting/17.2/Content/DeployingQVNprinting/Installing-sense-certificate...

HTH - Daniel.

evgeniya89
New Contributor II

Re: NPrinting cache not refreshing after reload of apps

Thank you. Now it works.

jonathanruiz
New Contributor III

Re: NPrinting cache not refreshing after reload of apps

Muchas gracias por la respuesta

Translation: "Thank you very much for the reply"

lindbergkarlsta
New Contributor II

Re: NPrinting cache not refreshing after reload of apps

Hi friends

I have a similar problem with NP 17.2 and QV 11.2 SR12 where changes in the QV app does not reflect in NP after reloading metadata. I created a support ticket and got the following answer from Qlik:

"We are aware of this bug and it will be fixed in Nprinting 17.3 which is due to be released soon. We have also seen situations where the workaround provided in the community which doesn't work for some customers. For now, reloading the nprinting engine and schedular service should fix this problem. Not a very nice workaround but it should fix it."

BR/Johan

Community Browser