NPrinting error 'CEF rendering exception' while generating report in preview
I've upgraded Qlik Sense en NPrinting from sept 2019 to feb 2020 (Patch 1 and later Patch 2). Since then I've got an error while generating a Powerpoint report (request failed) and in Designer I've got a more detailed error popping-up,
a CEF rendering exception 'CEF_ON_JS_ERROR_MESSAGE_RECEIVED'.
Attached the screenshot of the error and the corresponding part of the log.
The report is containing images. The image the error is pointing at its the firs image in the report ('bWBjaa'). If I remove this image from the report, the error points to the next first image in the report.
I also restored a backup of the NPrinting server, so I could test this with NPrinting sep 2019, but then also this error appears.
All communication between the servers is setup with the correct certificates, everything is done in https.
Does anybody has a clue where this error is coming from? It would be very helpfull, because now I can't generate my report to Powerpoint. Another report to Excel is still working luckely.
Thanks for your response. And finally this was also the solution for me. In the QS app I've rebuild all the objects which were causing this error. Even copy-paste of the object was not sufficient. Completely rebuild and replace the objects, even with exact the same settings and measures, was the solution. Very strange.
If anyone has a different solution, I'd like to hear it. I'm having the same issue. I have 778 pages throughout 18 reports that would have to be rebuilt. Like you, the first sheet in each report causes the error, remove that one and it's the next first sheet, so it's not really an object issue.
I have determined that this problem is not related to my App/Report. I just tried to run a report that had been able to run successfully every day (on schedule) without a single error. That report now does not run and generates the same error message. So I'm getting IT Support to restart the NPrinting engine and if that doesn't work to update to the latest release. Assuming I am then able to run the old report, I'll try again with the new ones that I just built.