Error CEF rendering exception. Remote code could not be executed

[Gestion-PSD]

Hi all!

Recently we've faced an issue in NP reports, both in report preview and publish task.

When we tried to preview o publish a brand-new report we got this error:

CEF Rendering error

Reading some threads here in Community and this QSupport article, it seems to be a connection port issue, but id actually doesn't.

I can assert that out issue doesn't a communication problem because other reports based on the same QS app don't fail when they're launched.

After some tests, we realize the issue is related to some visualizations (graphs) that were copied and edited from other app.

We solved the issue redoing affected graphs directly on the QS app, mirroring the graphs we want.

Even thoug the issue is solved, I open this thread hoping it helps someone that will face the same error.

Greetings from Valencia, Spain.

[Frank_S]

Hi @Gestion-PSD 

It would be interesting to know if the visualizations you copied over (then recreated using supported object only perhaps) have known limitations described the in the following limitations matrix.

https://help.qlik.com/en-US/nprinting/November2019/Content/NPrinting/ReportsDevelopment/Qlik-objects...

Thanks for sharing your findings.

[Gestion-PSD]

Hi Frank!

Thanks for your quik reply.

The visualizations we copied have not limitations to be processed by NPrinting. All of then were used in former reports that were discontinued. They are simply horizontal bar charts.

Moreover, the "new" visualizations are exactly the same as before (same graph type, dimensions, measure, colouring, size, ...)

Cheers!

[Frank_S]

Hi @Gestion-PSD 

So did you copy/paste from another app from the same Qlik Sense version/environment? Or from a QS server that is a different version/patch than the destination server/patch version?

Doing so could definitely cause the behavior that you reported. 

The copy / paste needs to be version to version accurate.

Another approach and a better practice is to export the entire sense app and to import the sense app to the target sense server. Otherwise recreating the object entirely is likely the best solution in your scenario.

Since I'm not sure of exactly how the copy paste worked, doing what you did was a good idea.

It comes down to determine how you are migrating QS apps, charts etc from place to place and determining which best practices work for you in your environment.

So it's possibly a compatibility problem with the objects that you are copying and possibly data sources are different between the source app and the target app of your chart.

For migrating reports from NP to NP environments you can follow these steps. However, the versions of NPrinting MUST be the same as well.

https://help.qlik.com/en-US/nprinting/November2019/Content/NPrinting/AdministeringQVNprinting/Import...

[Gestion-PSD · Accepted solution]

Hi Frank

Both old and new app are in the same QS server. NP old and new reports reside in the same NP server too. Both QS and NP servers conform the same environment since we created it. So version/patch is not the problem.

I think there must be some dark-side code behavior in copy/paste action.

Another possibility is a spontaneous code corruption or something similar in copy/paste action. Bad luck for us.

Thanks for your help!