NPrinting publish task fails with Access denied  error
Article Number: 000062586 | Last Modified: 2019/05/16
ublish Task fails
with "...Access denied ..."
error. In the NPrinting logs the following is registered:
Qlik.NPrinting.Engine 188.8.131.52 Qlik.NPrinting.Engine.Consumer.ConnectionResolvers 20190111T171417.456+01:00 WARN QLIKSERVERNAME 0 0 0 0 0 0 0 0 Unexpected exception while trying to initialize a resolver for connection navigator=qliksense;proxyurl=https://fqdn.domain.local/;appid=f072cb5d-6cdc-4052-a572-a0917494ae51;identity=domain\username0 after getting the connecting and working tokens. The connecting and the working tokens will be now released. ERROR: Access denied :Access denied(). Stack trace: ↵↓Server stack trace: ↵↓ at Qlik.Engine.Communication.QlikConnection.AwaitResponseTask[T](T task, String methodName, CancellationToken cancellationToken)↵↓ at Qlik.Engine.Hub.OpenApp(String docName, String userName, String password, String serial, Boolean noData)↵↓ at Engine.Navigator.QlikSense.SDK.Extensions.LocationExtensionsEx.AppEx(ILocation location, IAppIdentifier appIdentifier, ISession session, Boolean noData)↵↓ at Engine.Navigator.QlikSense.SDK.SenseNavigator.ReconnectApp
Due to app's Section Access
Use the same account listed in the logs under identity= to access the same app (see "appid="/" " in logs) via Qlik Sense Hub, and confirm that the same "Access Denied" error is prompted to the user. This confirms that the users selected as destination for the NPrinting Publish Tasks do not have access to the app / data due to Section Access.
In addition, if the NPrinting service account does not have Section Access ADMIN access level to the app, the connection metadata may fail to reload.