Nprinting powerpoint template - Intermittently missing chart colors/text blurred in initial few reports

[Digvijay_Singh]

Hello Everyone,

Has anyone came across with this issue as per the image attached?

Here is our current configuration - 

Nprinting - Feb 2024 SR3

Qlik Sense - May 2024 Patch 6

1. The issue occurs intermittently, and re-running the process resolves it.

2. When the Cycle field contains 100 values, only the initial few reports are affected. The number of impacted reports varies across incidents but is typically fewer than 25. I suspect this might be a synchronization issue between Sense and NPrinting, where the theme is not applied immediately when report generation starts, but everything functions correctly after the first few reports.

3. Meta data reload is executed before the task runs. Both the meta data reload and tasks are triggered from the Qlik Sense trigger app using APIs.

Please let me know if you need further details. Any assistance on this would be greatly appreciated.

@Frank_S  @Lech_Miszkiewicz @Ruggero_Piccoli 

[Digvijay_Singh]

nprinting_engine_cef.log logged this error for each object when the task was running - 

20250110T135635.983-06:00 [377] ERROR Engine.Navigator.QlikSense.SDK.Rendering.MashupGrpcServerUpdated - Engine.Navigator.QlikSense.SDK 24.4.5.0 Engine.Navigator.QlikSense.SDK.Rendering.MashupGrpcServerUpdated 20250110T135635.983-06:00 ERROR myserver 0 0 0 0 0 0 0 0 Details error 9da32087-0a0d-4bae-ab2c-89f1fa635a4f. ERROR: System.AggregateException: One or more errors occurred. ---> System.Exception: request with id 2ccf3dd67384483695c57da6d05e1d41 failed with remote error ErrorGenericResult, task CEF_ON_JS_ERROR_MESSAGE_RECEIVED, result: ERROR_JS_FAILURE_RESULT, a JavaScript call failed, app.visualization.get promise rejected for obj: pcPZ, error: vis.rendered.promise rejected for obj: pcPZ, error: visualization rendered an internal error for obj: pcPZ, message: The visualization was not found on the server. This extension is not available: piechart (), type: Type loading error, original: Loading chunk 9559 failed.↓(error: https://myserver/resources/qmfe/sense-client/8.189.14/@nebula.js/sn-pie-chart.3344fb9291e4d55ff463.j...), type: error, last js call: qlikPrintingService.renderOnline("f5dda2a3-f592-49a0-b387-5b8493568c97","np17-2feee201-4e50-4f4f-8044-d15503fa8b6a","object","pcPZ","render",{"jsTimeoutMsec":"60000","theme":"theme_nprint"})↓↓ --- End of inner exception stack trace ---↓↓ at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)↓↓ at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)↓↓ at Engine.Navigator.QlikSense.SDK.Rendering.MashupGrpcServerUpdated.Render(RenderParams renderParams) in C:\Jws\release-february2024-YKotfc3yq\server\NPrinting\src\Engine.Navigator.QlikSense.SDK\Rendering\MashupGrpcServerUpdated.cs:line 131↓↓---> (Inner Exception #0) System.Exception: request with id 2ccf3dd67384483695c57da6d05e1d41 failed with remote error ErrorGenericResult, task CEF_ON_JS_ERROR_MESSAGE_RECEIVED, result: ERROR_JS_FAILURE_RESULT, a JavaScript call failed, app.visualization.get promise rejected for obj: pcPZ, error: vis.rendered.promise rejected for obj: pcPZ, error: visualization rendered an internal error for obj: pcPZ, message: The visualization was not found on the server. This extension is not available: piechart (), type: Type loading error, original: Loading chunk 9559 failed.↓(error: https://myserver/resources/qmfe/sense-client/8.189.14/@nebula.js/sn-pie-chart.3344fb9291e4d55ff463.j...), type: error, last js call: qlikPrintingService.renderOnline("f5dda2a3-f592-49a0-b387-5b8493568c97","np17-2feee201-4e50-4f4f-8044-d15503fa8b6a","object","pcPZ","render",{"jsTimeoutMsec":"60000","theme":"theme_nprint"})<---
20250110T135636.066-06:00 [151] ERROR Engine.Navigator.QlikSense.SDK.Rendering.MashupGrpcServerUpdated - Engine.Navigator.QlikSense.SDK 24.4.5.0 Engine.Navigator.QlikSense.SDK.Rendering.MashupGrpcServerUpdated 20250110T135636.066-06:00 ERROR myserver

[Lech_Miszkiewicz]

Hi @Digvijay_Singh 

I have not experienced this issue personally with NPrinting as I just dont use images in my reports (instead I use native charts and tables to template). I did however noticed this behaviour directly in Qlik Sense few times and refreshing sheet was fixing it. That makes me wonder if the issue is actually NPrinting or Qlik Sense specific? On top of that this happened to me when the app had sheet triggers and some extensions which were causing issues on the sheet.

I dont know anything about your app, its performance and how it operates on the server and how resposive it is so I cannot comment on that. 

thats all from me for now.

thanks

Lech

[Digvijay_Singh]

@Lech_Miszkiewicz 

Thanks for sharing your experience! I haven't encountered this issue in Qlik Sense yet. As I mentioned, it typically appears in the initial few reports. Some of my tasks generate 800-1000 reports, but this issue only affects the first 20-30 cycle value reports, and even then, only occasionally. However, I've noticed that the frequency of this error has increased recently.

Thanks,

Digvijay

[Lech_Miszkiewicz]

are you using custom theme? Maybe thats what is causing the issue? I would try running it without custom theme and check for the same error. See how you go. Btw-I will have no idea about QS custom themes so someone else would need to comment on that.

cheers

[Digvijay_Singh]

Yes, we have a custom theme applied. Apologies, I forgot to mention it earlier. The issue appears about 1-2 times in 10-12 runs, so it might be related to a delay in applying the theme, but I'm not certain. I'll run a few tests without the theme, and if the issue doesn't occur in 20 runs, I'll focus more on that aspect.

Thanks for your help!!

Thanks,

Digvijay

[Lech_Miszkiewicz]

otherwise i think you may want to open support case and provide those details to Qlik Support

[Digvijay_Singh]

Yes, I opened support case as well today!

Thanks!

[Frank_S]

@Digvijay_Singh 

(late to the party but none the less 🙂 )

Yes, I think that is a good call. Opening a case that is.
It will be worked on internally and a team member will get back to you via the support case.

Meanwhile, I think you hit the nail on the head with the latency suggestion.

Just ensure that your meta data reload is actually finishing 'before' the publish task starts. 

Also ensure that your Qlik App itself isn't be reloaded by a Qlik Sense task while your NP metadata is reloading.

I would also suggest increasing the image rendering time in the NPrinting renderer.config file (up to 300 secs).

Configuration examples:

renderer.config (June 2020 & newer versions of NPrinting)

<add key="webrenderer-timeout-sec" value="90" />  

The above is from this article below. Unfortunately the table layout is not preserved in the copy paste.  

https://community.qlik.com/t5/Official-Support-Articles/Upgrade-to-Qlik-NPrinting-June-2020-or-newer...

I'd suggest using a value of 180 (not 90) to start with. Then increase it as needed (up to 300 secs) until it works.

Hope you are doing well!

Kind regards...

[Digvijay_Singh]

Thanks, @Frank_S, for consistently sharing great tips!

We have a series of events that must occur in a specific sequence, starting from the app reload to the final NPrinting task trigger. This process, managed by the Sense app through sequential NPrinting API calls, has been running smoothly for the past 4-5 years. However, we've recently encountered this issue intermittently—about once or twice in every 15-20 runs.

As suggested, we'll review the renderer.config settings and share our findings soon.

Thanks,
Digvijay