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"
- Stop NPrinting Engine service.
- Make sure that the NPrinting Engine process is not running from the Windows task manager
- Make sure that all the qvw.exe are not running from the Windows task manager
- Stop NPrinting Scheduler service
- Make sure that the NPrinting Scheduler process Is no more running from the Windows task manager
- Stop NPrinting Messaging service (or RabbitMQ service depending on the NPrinting version that you're using)
- Start NPrinting Scheduler service
- Start NPrinting Messaging service (or RabbitMQ)
- Start NPrinting Engine service
- Wait for the Engine to came back online
- Reload the cache
Let me know if this works.
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?
When stopping the services, the NPrinting Scheduler service has to be the first one to be started, however, if you don't start the other two services right away, Messaging service and Engine service, the Scheduler will stop, and will not fix the issue.
The process definitely works, just keep in mind that when restarting the services, start one after the other quickly, as soon as it says Running.