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

[kdmarkee]

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.

[kdmarkee]

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.

[Lech_Miszkiewicz]

Hi Kris,

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

1. let us know how did you go with 1. service account user and 2. smaller qvw
2. 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

[alan_richmond]

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

[Lech_Miszkiewicz]

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

[alan_richmond]

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

thanks for your support Lech

[kdmarkee]

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.