Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
While executing connection in Nprinting, getting error as
Cache generation failed: NPrinting Engine(s) failed to open document:
Failed to open a resolver for connection navigator=qliksense;applytheme=True;proxyurl=https://*********/;appid=******;identity=********. ERROR: Qlik.Engine.MethodInvocationException: Access denied [5]:Access denied()
Then We tried to change identity of user who having admin level access and then the connection is executed successfully. But, while execution of task for same connection , getting below error even though the user is enabled in security Role and user has the NPrinting user profile setup with domain account.
WARN: error during report generation: NPrinting Engine(s) failed to open document: navigator=qliksense;applytheme=True;proxyurl=https://*********/;appid=******;identity=********.Check connection page for connection status.
Please help in resolving issue
@Sri_Bhuvana does the source app (QVW or QVF) have section access enabled on it? If so, check the section Access table in the source document and ensure that the Nprinting service account has been added properly to the Section Access table. Or you can try create a copy of the source QVF or QVW without Section Access and you use that App for the Nprinting Connection as well.
Hi @Sri_Bhuvana - seems that you are duplicating posts for no reason: https://community.qlik.com/t5/Qlik-NPrinting/Report-Generation-Failing-in-Qlik-Nprinting/td-p/209817...
I have already commented on that issue. and the questions I asked are:
The issue is that you are probably trying to use section access (there is a setting in NPrinting connection for that) and you are not configuring all required pieces which are:
All above applies to scenarios where you try to use section access, or when there is section access in your Qlik Sense app.
more on that obviously in documentation: https://help.qlik.com/en-US/nprinting/May2023/Content/NPrinting/DeployingQVNprinting/Section-access....
so bottom line is - are you using section access?