Qlik Community

Qlik NPrinting Discussions

Discussion Board for collaboration on Qlik NPrinting.

stevelord
Valued Contributor

How to reduce frequency of need to pull named cal down from server to qv desktop?

Hi All, our nprinting jobs fail every 30 days or so (give or take weeks, I haven't measured yet) because the named license on its instance of qlikview desktop edition expires or needs to be pulled back down via the 'open in server' trick.

Is there a way to make it so that license stays on that instance of qlikview desktop edition indefinitely?  If not, how often exactly will the license need to be pulled back down.  If it's not a timed thing, what causes that instance of qlikview to forget its license info?

Thanks!

PS> Nprinting runs jobs 7 days a week so inactivity is not among the reasons its instance of qlikview would forget the license.

1 Solution

Accepted Solutions
Employee
Employee

Re: How to reduce frequency of need to pull named cal down from server to qv desktop?

Hi Steve,

Have you considered using a QlikView Server Document for at least one of your daily/weekly reports? This works the same as Open in Server

HTH - Daniel.

3 Replies
Employee
Employee

Re: How to reduce frequency of need to pull named cal down from server to qv desktop?

Hi Steve,

Have you considered using a QlikView Server Document for at least one of your daily/weekly reports? This works the same as Open in Server

HTH - Daniel.

stevelord
Valued Contributor

Re: How to reduce frequency of need to pull named cal down from server to qv desktop?

Yes, I will do that in the near future and come back with either correct answer credit or questions.   Thanks!

stevelord
Valued Contributor

Re: How to reduce frequency of need to pull named cal down from server to qv desktop?

I've successfully implemented this now using a random fake html report that will run itself at 11pm each night.  (I thought about weekly, but didn't want to risk missing a beat if an infrastructure issue happened on the same day one or two weeks in a row.  And the job takes less than 30 seconds to run itself. )

I was unable to just do a straight reload of the dashboard opened in server (security settings we have I think), nor an excel or qv entity report.  But this makes a kind of sense in retrospect, that html report is the one that works for a document opened in this manner.

Community Browser