Skip to main content
Announcements
Defect acknowledgement with Nprinting Engine May 2022 SR2, please READ HERE
cancel
Showing results for 
Search instead for 
Did you mean: 
sifatnabil
Specialist
Specialist

NPrinting 17: scheduler doesn't pick up qvw update

Hi all,

I have a report scheduled to trigger at 10am and 2:30pm. I have a batch file reloading the qvw 5 minutes before both triggers. However, the report does not pick up the new data from the last refresh of the qvw. So the report just sends out stale data. Anyone know how to fix this? Thanks.

1 Solution

Accepted Solutions
sifatnabil
Specialist
Specialist
Author

Guys, I have spoken with the Qlik development team and this has been raised as a major bug in NPrinting 17. They will have a fix for this in their next release.

View solution in original post

9 Replies
sifatnabil
Specialist
Specialist
Author

bump

jonopitchford
Contributor III
Contributor III

I think i have a similar issue. What happens if you restart the NPrinting engine service after you reload the qvw? do you see the new data in your report then? (obviously not a solution)

cwolf
Creator III
Creator III

How do you open the qvw in Nprinting? Directly from filesystem or from QlikView server (qvp:\\...)?

On the server there are some settings,wich prevents an immediate refresh.

sifatnabil
Specialist
Specialist
Author

Directly from file system. What setting can I change to immediate pick up changes after a qvw is refreshed?

cwolf
Creator III
Creator III

Sorry, I mean settings on QlikView server, if you open the qvw on it. But by opening from filesystem I don't know what the problem is. Your batch job has realy finished before the Nprinting task starts?

sifatnabil
Specialist
Specialist
Author

Yes I tested and my batch job refreshes well before the Nprinting schedule. In fact, when I check the connections page, I can see that the meta data/cache only loads once (after creating a connection) and never again. Shouldn't the cache refresh each time there is new data on the qvw?

Capture.PNG

Daniel_Jenkins
Specialist III
Specialist III

Hi Sifat,

Are there any other tasks scheduled that are using the same connection?

NPrinting 17 keeps a connection open with a QVW so long as there are tasks in the queue for Engine to execute which contain reports which use those connections. As soon as the queue is cleared, or if the subsequent tasks use different QVWs, the connections will be closed.

The next time a task is executed using that QVW, the connection will be re-opened and any data loaded in the interim will be populated into reports.

For example:

Task1 uses Connection1 and Connection2 and runs from 01:00 - 03:00.

Task2 uses Connection2 and runs from 02:30 - 04:00

Task3 uses Connection1 and runs from 03:30 to 04:00

[Connection1 = QVW1, Connection2 = QVW2 & Connection3 = QVW3]

If QVW1 is reloaded between 03:01 and 03:29, Task3 will use the reloaded version of QVW1.

If QVW2 is reloaded between 01:01 and 02:31, Task2 will use the old version of QVW2.

HTH - Daniel.

sifatnabil
Specialist
Specialist
Author

Guys, I have spoken with the Qlik development team and this has been raised as a major bug in NPrinting 17. They will have a fix for this in their next release.

jonopitchford
Contributor III
Contributor III

I think that's useful Daniel. I've been looking at NPrinting 17 and struggling with this. I was testing using just one report/connection and found that if i updated the .qvw it would not update in the report. but when i add two connections and run them one after the other is does update the report. I assume this is because it keeps the connection open until a new connection is made and then closes it and opens a new connection?