Some NPrinting Tasks failing after Qlik Sense May 2024 Patch 11

[SamTaubman]

I'm attempting to manually run some monthly NPrinting publish tasks that have been working until today. The publish tasks are getting stuck at Status: Running, Progress: 0% for around 15 minutes before Failing. On Failure it says:
"Failed generation of report 025af9f0-6c56-492a-90a1-2089b664c3ec for user 45979d92-dcc8-459c-aaa0-9da39a44194a. ERROR: All documents failed to generate: Object 'UsWXvLe' from Sense app '6e444ba3-efe9-4824-857e-39d52ee42d0f' had problems when rendering. ERROR: CEF rendering exception. Error during GRPC request. For further details, check 'f1ed8bea-e5a6-4be2-bc8f-1de7e8869fe6' in nprinting_engine_cef.log."

When I check the nprinting_engine_cef.log it says: 
"Engine.Navigator.QlikSense.SDK.Rendering.MashupLoadException: request with id 31b7fd2f83394573a5214fb5e437159b failed with remote error ErrorLoadurlTimeoutResult, mashup load failure<---"

I upgraded my Qlik Sense Windows Enterprise Version to Qlik Sense May 2024 from February 2023 last month. Last week I upgraded Qlik Sense to May 2024 Patch 11 due to the security issue. Now these NPrinting jobs are not working. However there is another job that is automated and runs 3 times a day which uses a different Qlik Sense App that has been running without issue. I tried restarting the server which runs Qlik NPrinting but that didn't resolve the manual NPrinting jobs failing.

[Lech_Miszkiewicz]

Classic! 

Very well said @David_Friend - I am still amazed how many times people fall for the version compatibility trap. I think it is hight time for me to write a blog post about it so we can reference it each time something like this happens.

cheers

[Lech_Miszkiewicz]

To answer your question @SamTaubman 

various different APIs can change also Qlik Sense charts have changed and underlying structure of them has changed too (you noticed for sure how over last few years many new controls appear in Qlik Sense chart properties).

You may be able to run some reports on unsupported configuration because maybe you are using just an old straight table in one report but then other report may be using differnet objects which are no longer supported. 

Compatibility check is a cardinal sin of every customer so there is nothing to be ahamed of, you are not the first and not the last one who fell for this trap.

For the future - ALWAYS check compatibility chart by going to help.qlik.com -->NPrinting for currently supported version:

If your version is not in dropdown it is already out of support and you need to find it in archive (as shown above). Below is a standard place where in help--tree structure you will find this info. It is always specific to the version of NPrinting used!

cheers