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.

[Lech_Miszkiewicz · Accepted solution]

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

[alan_richmond]

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

[Lech_Miszkiewicz]

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

[Ruggero_Piccoli]

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.

[kdmarkee]

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.

[Lech_Miszkiewicz]

Hi Kris:

answers:

1. Yes - with your credentials it should work as well - however you need to be an admin in Section Access roles
2. 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)
3. 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

[kdmarkee]

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...

[#9]

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 .

[Lech_Miszkiewicz]

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