Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
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
The issue occurs intermittently, and re-running the process resolves it.
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.
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
for last 4-5 years did you load more data to this app or are you actually reducing "tail" and only keeping say: current and last year or current and only last 2 years.
If process was working before and it isnt currently that means something has changed, Like:
all above can have a performance impact on how Qlik Sense behaves. I have similar story with my other customer who suddenly said his Qlik Sense is stopping from time to time. It turned out more and more data was loaded, more apps were created and more resources (or apps omptimization) is required, but as you say - it worked until it didnt 😄
cheers
Thanks, Lech, for highlighting some key indicators!
I agree—there have been significant changes over the past 4–5 years. We only load the last two years of data to keep the app size manageable. As I mentioned, the issue is still quite infrequent, and a re-run resolves it. It only affects the initial few generated reports occasionally, with cycle values ranging from approximately 300 to 1000 across different reports. The limited scope of the issue is helpful since I don’t have to check all 1000 reports to identify the impacted slides.
The fact that only a few initial reports are affected suggests that the issue is not related to overall performance but might be a synchronization problem when NPrinting starts fetching chart images (just a hypothesis). I still need to run tests without the custom theme to rule out that possibility.
Thanks,
Digvijay
Hi @Frank_S
Do you know if I can apply custom theme while doing debugging as suggested in this article?
I should have verified this earlier, but I just discovered that the PowerPoint report output for the initial few reports matches the default classic theme. This clearly indicates that the custom theme application is delayed while NPrinting is fetching images from the Sense app. As a result, only the initial few generated reports are affected. In fact, the last error report contains some charts with the default theme and others with the custom theme. Would it be fair to call this an NPrinting bug now? 😊
Thanks,
Digvijay
Ok I have done some further digging as per your comments today and since I'm not clear if your using 'carded' theme or 'extended sheets' this may or may not apply to you.
Please have a look to verify if this is also you.
If yes then it is a Qlik Sense bug resolved in Nov. 2024 Initial Release and later patches and versions. (Defect QB-24997 is quoted therein)
Cheers!
ps: otherwise, please try the renderer.config settings since as you said it happens on the first few reports. It still could be a timeout issue.
Thanks @Frank_S for sharing more details.
We do not use carded or extended sheets. Everything functions smoothly most of the time, so I believe once in a while Nprinting starts fetching images before custom theme JS load finishes.
I will follow up after implementing the renderer.config changes and conducting further tests.
Thanks,
Digvijay
I think you missed my question on debugging related.
Is it possible to apply theme while running this below command in Chrome Dev tool? Currently It applies default theme even though the App I have used in the command has custom theme applied in Sense.
qlikPrintingService.render("f5dda2a3-f592-49a0-b387-5b8493568c97","","object","pcPZ")
Thanks,
Actually I want you to run the render.config tests. I did not miss your question.
If the issue persists, then please continue via support case outside. I will work internally with the case owner going forward.
Regarding your question, (and if the issue persists after renderer.config tests), please ask directly in the case but include exactly the steps you are referring to when you say:
"Is it possible to apply theme while running this below command in Chrome Dev tool? Currently It applies default theme even though the App I have used in the command has custom theme applied in Sense.qlikPrintingService.render("f5dda2a3-f592-49a0-b387-5b8493568c97","","object","pcPZ")
A video of your steps provided via the support case would be superior.
Thanks!
@Digvijay_Singh did increasing the timeout have any affect?
Thanks @David_Friend for your response!
Not yet, we are working with IT to make that happen, but it doesn't make sense to me how that change will help.
How that setting will fix the issue of 'Nprinting capturing few images with default theme and after some time start capturing images with custom theme? and that too once in a while!
Thanks,
DJ
The renderer.config changes will allow for images that take longer to load, more time to load ie: 180 sec.
The recommendation is based on the logging you shared initially that indicates that the images are timing out.
"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,"