NPrinting cannot create a Connection due to Section Access usage of NTName

[#1]

Hi,

We're using NPrinting 17.3 and observed that QVWs which implement Section Access would prevent us from creating a working NPrinting connection. It would show the Cache Status: "Error Request has been purged due to connection errors"

Upon further reading, someone mentioned that using NTName in Section Access causes this.

A workaround/solution provided was to use USERID/PASSWORD, but this is definitely not scalable for a large organization.

Can someone confirm if this is a known issue / bug with NPrinting?

Any other workarounds?

Thanks.

[pauljohansson]

Hi,

You are able to create connections to documents with section access, details:

http://help.qlik.com/en-US/nprinting/17.3/Content/GettingStarted/HowCreateConnections/Create-Connect...

br

Paul

[Anonymous · Accepted solution]

Hi,

I think you might want to check the account which you're running the NPrinting engine with. It could be due to some security access issue that is blocking the NPrinting service.

Try adding the role and permissions for the NPrinting service into the datasource used by the section access. NPrinting behaves like a robot user so you have to give it the permissions to access your QVW.

[Lech_Miszkiewicz]

Add NPrinting user (like above mentioned - service account running your engine) to section access table, reload it and then test by:

• log in to server as NPrinting account
• open application using NPrinting account credentials
  • If you are able to open document then NPrinting process generating data will be able to do it as well.
• also make sure NPrinting account has userCal license allocated.

(I assume you are using QlikView as NTName is not part of QlikSense section access setup) 

cheers

Lech

[#5]

Thanks!!!

I did as advised and added in the Nprinting user service account, reloaded the cache and the connection now works! I've managed to create the task now!

Thanks!

[Lech_Miszkiewicz]

Hi Glenn,

When applicable please mark the appropriate replies as CORRECT. 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.

regards

Lech

[kdmarkee]

Can I ask, what did you use as the Identity in the web console when you set up your connection?  The NPrinting user or a different user, maybe one with the admin role?  Thanks.