Connection Cache Error

[anderseriksson]

Qlik NPrinting November 2017

Qlik Sense April 2018

Have several connections to the Sense server for Apps in stream Everyone. All but one working?

They use the same Proxy-adress and user, copied Sense app ID from Hub.

Verification is okay and Connection status successful on all NPrinting engines (only one, single server installation).

But for this single application I get Cache status = Error after some seconds running (not immediately when showing Generating).

Have even made a copy of the App and published to stream Everyone under a different name and that works!?

User has access to application in the Hub, no Section Access.

nprinting_webengine.log says "Reload metadata task d2011d9c-9aed-4243-a61d-5d791d15c209 sent to queue" but nothing more.

Nothing in any other log-file and nothing in Windows logs.

What could be the issue?

Don't want to delete and republish the Sense applikation since there are user objects I don't want to loose.

[balabhaskarqlik]

May be this can:

What is the result of running a verification on the Connection details screen?

What do you see under Admin > Task executions & you select the relevant  task?

Check the Task name, relevant logs.

Check these:

https://help.qlik.com/en-US/nprinting/April2018/Content/Troubleshooting/Troubleshooting.htm

https://help.qlik.com/en-US/sense/April2018/Subsystems/ManagementConsole/Content/engines-overview.ht...

[anderseriksson]

As I said above verification is okay.
No task, this is the cache build directly when creating the connection.

I have already checked the NPrinting documentation without finding anything relevant.
And as I stated, connections to other Sense applications in the same stream works.
Even a copy of this application published in the same stream under a different name!

[Lech_Miszkiewicz]

Hi Anders,

I wonder on which version of Qlik Sense was this app created? Since the duplicate of the app works i assume it can be something (some legacy) in the qvf file causing an issue.

Wha tyou can do is :

• create a duplicate
• publish and replace (overwrite) existing app. This will keep your user created sheets and all Id's will be the same. It should not break anything and is definitely worth trying.
• try re-generate metadata

cheers

Lech

[anderseriksson]

Sorry, already tried to re-publish over the old published version with no success.
The application is published but NPrinting cache generation generates error.

[Lech_Miszkiewicz]

Is it possible that for this particular AppId you have some security rule applied which could prevent it from full required access?

[anderseriksson]

No special security rule for this app and no section access.
The user used in the NPrinting Connection has no problem accessing the app in Sense Hub.

[Lech_Miszkiewicz]

In such case i would open support ticket with Qlik and let them investigate.

Also keep us posted if you resolve this as it is quite interesting issue...

cheers

Lech

[anderseriksson]

Yes I will, first I wanted to ask if someone else had the same experience.
Appreciate your effort.

[william_fu]

Hi Anders, did you ever figure this out?

I'm running into the same problem, error when reloading the connection cache on a older app (I'm publishing and replacing the updated app over the new one).

If I publish the exact same app,  same stream on its own (without replacing), the cache generation works fine.