I am having a problem with the On Demand printing feature in NPrinting 17.2.
I upgraded to Qlikview 11.20 SR 15 and NPrint 17.2. I also installed the On Demand feature. Everything seems to have installed correctly (no errors on installation). I ensured that the Nprint service account is assigned to the appropriate groups on the server (Qlikview Administrators and Qlikview Management API). I also set the On Demand trusted server setting.
For setting up the connection, I am following the on demand configuration instructions by setting the connection as a server connection (as opposed to a local connection). After creating the connection, it is stuck in the "Generating" status and never finishes. I am able to generate cache using local connections on the same documents (although somewhat slower to generate than in 17.1).
I did try to create an on demand report using an existing local connection, but the on demand button doesn't surface on AccessPoint.
Questions: To use the On Demand feature, must I use a server connection to the qvw? And if that is the case, what could be causing the cache to never finish generating?
Hi Ann Weiner,
Please make sure your engine is showing online status in Main Menu > Admin > Engine Manager window. Also, try to restarting NPrinting Services of server/engine. For On-Demand Printing feature, please go thru following links:
Hope this helps.
I managed to create a data connection 3 days ago using 17.2 to local files and files that are published into the Server.
Today when I need to reload the meta data, it gets stuck at "generating" for all these connections.
Restarting services does not help, the log file says:
"Reload metadata task 3b19040f-b086-4cfc-9345-2b5b66335e01 sent to queue"
Yes, the engine is online. And I did use the configuration steps that are in the YouTube and in the documentation. I restarted all of the services, and still have the same problem.
Let me know if this works.
For me that works. We did reboot to our server but that didn't work. I found that Nprint Scheduler prosess was stucked. After killing that process and after restarting Nprinting Scheluder service Nprint works again.
Thanks a lot!
Yes, I go through the steps of stopping all of the services when ever we have cache generating issues. The problem is that this issue seems intermittent, and is a rather disruptive way to recover. Wish there were more transparency in the administration of NPrint, so that we can see exactly where the failure is and correct it, rather than having to restart everything. My guess is that will be in a future release of Nprinting.
I am having the same issue and I followed your steps to stopping the services. The NPrinting Scheduler service was stuck and I had to stop it from the Windows Task Manager. It stopped. However, the Cache Status is still stuck on Generating.
We tried to reboot the server and still does not work. Do you think I will have to recreate another connection?