topic Re: NPrinting 17 - Metadata stuck in Generating for QV app with section access in Qlik NPrinting

NPrinting 17 - Metadata stuck in Generating for QV app with section access

kdmarkee — Sat, 24 Jun 2017 16:34:41 GMT

I am wondering if anyone can provide some advice on what might be wrong. I have QlikView 12.1 and NPrinting 17.3 and all of my NP connections generate metadata just fine when I don't have Section Access in the QV app, but for some reason my QV app with Section Access incorporated continues to be stuck in "Generating" mode with regards to reloading metadata in my NP connection. I have the NP service account user part of my Section Access in the QV doc, I am using my account (I have Admin role in NP web console, and am also part of the Section Access in the QV doc) in the Identity field for my NP connection under the server authentication piece, and my domain account info is entered into my User info in NP web console. Thanks in advance for your help.

Re: NPrinting 17 - Metadata stuck in Generating for QV app with section access

Lech_Miszkiewicz — Sun, 25 Jun 2017 23:38:08 GMT

Hi Kris,

If NPrinting user is added to QlikView section access as an admin and datareduction is not leaving the datamodel without records then it should work without the authentication option (sort of like SSO)

Now:

What are the results if you do following:

RDP to NPrinting box as NPrinting account
open QlikView desktop and use open in server to open a document with section access?

Is NPrinting user able to open this document without issues?

I have also noticed that there is a issue with metadata generation if NPrinting account is not able to save/store a qvw file in a location where it is originaly sitting. Can you also open and save this QVW in its original location using NPrinting account user?

cheers

Lech

Re: NPrinting 17 - Metadata stuck in Generating for QV app with section access

alan_richmond — Mon, 26 Jun 2017 00:57:33 GMT

I had the same issue last week with QV12.10.6 and NP17.3.1 when the account that NPring was using was NOT in the section access file used for the QV app build.

The process above allowed me to see that issue

I have moved further now am having cache build issues because the NP server needs SSL and QV doesnt, waiting for the new NP that doesnt need SSL

Re: NPrinting 17 - Metadata stuck in Generating for QV app with section access

Lech_Miszkiewicz — Mon, 26 Jun 2017 01:10:36 GMT

I am testing NPrinting 17.4 (or so called July 2017) and it has following hint in connection generator section.

This should answer Kris's question.

Regarding NPrinting and QV. I do not think you need a SSL certificates to get it working. I does not require a certificate to generate cache metadata.

cheers

Lech

Re: NPrinting 17 - Metadata stuck in Generating for QV app with section access

Ruggero_Piccoli — Mon, 26 Jun 2017 08:31:50 GMT

I confirm that it is not necessary to install a TLS (former SSL) certificate in order to connect to QlikView documents with section access.

I would to suggest you to read this help site page Section access ‒ Qlik NPrinting.

Re: NPrinting 17 - Metadata stuck in Generating for QV app with section access

kdmarkee — Mon, 26 Jun 2017 15:05:23 GMT

Using the NP service account user, I did RDP to the NP server and I was able to successfully open my QV document that has section access. I also confirmed that that user has Admin access and that there is data. I also confirmed that my NP service account user is part of the Admin group on my QV server which if I understand this correctly gives that user all rights on the folder where the source qvw resides so saving in that location shouldn't be an issue, correct? Can you also clarify 3 things for me? (1) In my connection info for this within the NP web console, I am using my personal account for the "Connection requires authentication" portion. If I can do all the same things as the NP service account user, shouldn't the metadata refresh work or not necessarily? (2) When you say "it should work without the authentication option", are you saying that I should not have to set my connection in the NP web console to "Connection requires authentication"? (3) Do I need to include the domain account info for my NP user in the properties of my NP user in the NP web console (Admin > Users menu)? Thank you again for your help.

Re: NPrinting 17 - Metadata stuck in Generating for QV app with section access

Lech_Miszkiewicz — Mon, 26 Jun 2017 23:55:28 GMT

Hi Kris:

answers:

Yes - with your credentials it should work as well - however you need to be an admin in Section Access roles
Now i am not sure neither - as per my screenshot above (in previous post) it means we have to put through credentials when using a document with section access. I was able to create a connection without putting through an authentication details in the past (it could have changed - so we stick to what qlik suggests)
You do not have to. This would be handy however if you would like to use SSO when logging in to NewsStand or Qlik NPrinting Admin console as well as it is necessary to publish to QlikSense Hub

regards

Lech

Re: NPrinting 17 - Metadata stuck in Generating for QV app with section access

kdmarkee — Tue, 27 Jun 2017 17:23:23 GMT

Thanks for the responses. I'm still stuck in Generating and am assuming it will eventually error out, and as far as I can tell I have followed your tips and the online help for NP 17.3. Not sure what I'll do next...

Re: NPrinting 17 - Metadata stuck in Generating for QV app with section access

Tue, 27 Jun 2017 17:29:11 GMT

The June 2017 release (available as of this morning) has a kill task button. I know this doesn't help your immediate problem, but hopefully next time .

Re: NPrinting 17 - Metadata stuck in Generating for QV app with section access

Lech_Miszkiewicz — Wed, 28 Jun 2017 02:50:15 GMT

What is your section access looking like? is it based on NTNAME? or is it using custom user name USERID and custom password?

can you share Qlik script for section access? Maybe you have other things in it like DOMAIN ID or SID?

cheers

Lech

Re: NPrinting 17 - Metadata stuck in Generating for QV app with section access

kdmarkee — Wed, 28 Jun 2017 20:25:14 GMT

I'm trying 2 other metadata reload tests today too: (1) using the nprinting service accountuser in my NP connection as the "Identity" instead of my personal one, and (2) trying a smaller qvw, although I doubt that is the issue since what I've read seems to suggest my size is ok (636kb).

2 other passing thoughts I had...is section access picky about using a mounted folder name in the NP connection, or even picky about case sensitive characters for the domain user info listed in the NP connection Identity or even in the NP web console User screen, as section access uses uppercase.

Our full ETL process is made up of 2 qvws that each have some logic that begin to build the security tables, a 3rd qvw (our final data model) that has the Section Access and Section Application syntax, and then our 4th and final qvw is our actual QV UI app that does the binary load of our data model from that 3rd qvw. But what we basically end up with in our 3rd qvw file (the data model, which eventually feeds our final QV UI app as well of course) is what is going to be of most importance for this discussion I believe, and below are the following tables and linkages of that, and some sample data. (There's a lot of extra fields that we use for conditional purposes in our app associated to our users.) The Users table is hidden when Section Access is applied in our script, but wanted to show the full picture below. I will also mention we use STAR is *; as our first line of code in our Section Access section.

Hope that helps. Thanks again.

Re: NPrinting 17 - Metadata stuck in Generating for QV app with section access

Lech_Miszkiewicz — Wed, 28 Jun 2017 21:45:31 GMT

Hi Kris,

I do not see anything unusual in your section access model. regarding your questions & suggestions:

let us know how did you go with 1. service account user and 2. smaller qvw
Section Access is picky when it comes to lower/upper case letters in your user table. As you said it is all in UPPER case - and that is how it should be. On the other hand in NPrinting it shouldn't matter where you write user name in capital letters or small. It should convert it all to capitals in the background anyway.

regarding "Star is *" in you r script - i prefer to build a logic 1 to many for the same purpuse (build a full tableof all combinations - but it is only my personal preference it it should not have any impact on NPrinting.

regards

Lech

Re: NPrinting 17 - Metadata stuck in Generating for QV app with section access

alan_richmond — Wed, 28 Jun 2017 21:57:26 GMT

I was having the same issues with caching and after upgrade to 17.4 or June 2017 I no longer have the issue

Re: NPrinting 17 - Metadata stuck in Generating for QV app with section access

Lech_Miszkiewicz — Wed, 28 Jun 2017 22:00:56 GMT

Seems like everyone was waiting for June 2017 release ... I like it!

Re: NPrinting 17 - Metadata stuck in Generating for QV app with section access

alan_richmond — Wed, 28 Jun 2017 22:10:12 GMT

yes i love the abort button against a task to kill a task i want to stop

thanks for your support Lech

Re: NPrinting 17 - Metadata stuck in Generating for QV app with section access

kdmarkee — Fri, 30 Jun 2017 21:30:07 GMT

Just providing the latest... my tests to use a smaller qvw as well as the np service account both failed; they either end up with "Error timeout" as the cache status or stay in Generating status for over 24hrs and I decide to kill it and restart my NP machine because what seems to happen is that it ends up blocking all my other metadata reloads that I know work. The long Generating status shouldn't happen I would think because the same qvw without section access took just minutes to reload the metadata. At this point I need to connect with our chief tech officer to see if we reach out to support or not, or if we'll ditch using section access and go with NP web console filters instead.