NPrinting connections stuck on generating

[bethany_]

Hello all,

We have just started using NPrinting (we've got version 17.6) and are having difficulty with reloading the caches. We have two files that trigger overnight (2am and 4am), but in the last two weeks they just stay on 'generating', until the next morning when the previous attempt aborts and the new attempt starts. Trying to manually reload metadata doesn't work either on the two files, or on other connections.

I've verified the connection and that seems to work fine - we previously had a licencing issue when that was run, but that has been resolved. I've checked the licence activation and it all seems happy - I'm at a bit of a loss as to where the issue is. Any suggestions on where I can look next?

Thanks!

[Daniel_Jenkins]

Hi Bethany,

What type of Connection (QlikView local/server/cluster, Qlik Sense)? If QlikView and not Local, does the version of QV Desktop used match the version of QV Server used?

What do the NPrinting logs say?

- Daniel.

[Ruggero_Piccoli · Accepted solution]

Hi,

I would to suggest you to upgrade to February 2018. There is this solved bug:

Cache and metadata reload from QlikView Server remained in Generating status

The cache and metadata reload process of some QlikView Server connections remained in Generating status forever.

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.

[bethany_]

Hi Daniel,

It's a server connection, and desktop and server versions match.

On checking the task executions, it does show the progress as 0% and the elapsed time of 00:00 even though the event triggered nearly 6 hours ago - it looks like it's saying triggered but not actually doing anything

Thanks

Bethany

[bethany_]

Hi Ruggero,

We've installed the Feb 18 upgrade and it seems to be working now! Thank you

[Lech_Miszkiewicz]

yeeeeep

I battled this for soooo long time until it was called a BUG

It was a quite rare behaviour though.

glad that Feb 2018 solves it. cheers Lech

[pnowicki]

After upgrading to June 2018 from November 2017, all of our metadata needed to be re-generated across all our Nprinting reports.  Trying to do so now and generating the cache is stalled, taking forever without any progress.  Followed all of the tips on the community website, but to no avail.  I think we are going to roll back to our backup of November 2017. 

[Lech_Miszkiewicz]

Hi Paul, What does connection verification say when you are running it?

[Ruggero_Piccoli]

Hi,

Check the logs if there are some specific error messages. Refreshing the caches after an upgrade is normal because from a version to a newer the cache could be different to manage new feature. Of course the metadata reload process must work fine.

If the problem persist please open a support ticket so one of us can remotely connect with you to deeper investigate.

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.

[bethany_]

Yes, we've got this issue back again. After we upgraded to Feb 18 it was working fine, now we've upgraded to June 18 it's stopped working again. I'm wondering if Nprinting is the correct platform for us to produce reporting on seeing how it's so temperamental.