Problem with BIRT after updating to 4.2.2

Hello,

When I try to generate a BIRT report I get: “+ The report file : default_report.rptdesign does not exist or contains errors.” like was already reported in this thread. In our case the workspace is local. This has been working perfectly on local KAP and KNIME Server before updating.

This is what I see when selecting “Debug report”:

oct 13, 2020 9:51:06 AM org.eclipse.birt.report.debug.internal.core.vm.ReportVMServer start
INFORMACIÓN: [Server] client accepted
oct 13, 2020 9:51:06 AM org.eclipse.birt.report.debug.internal.core.vm.ReportVMServer$1 run
INFORMACIÓN: [Server] enter request dispatching
oct 13, 2020 9:51:06 AM org.eclipse.birt.report.debug.internal.core.launcher.ReportLauncher configEngine
INFORMACIÓN: User class path received:
oct 13, 2020 9:51:08 AM org.eclipse.birt.report.engine.api.impl.EngineTask handleFatalExceptions
GRAVE: An error happened while running the report. Cause:
org.eclipse.birt.report.engine.api.EngineException: Failed to initialize emitter.
at org.eclipse.birt.report.engine.emitter.EmitterUtil.getOuputStream(EmitterUtil.java:82)
at org.eclipse.birt.report.engine.emitter.html.HTMLReportEmitter.initialize(HTMLReportEmitter.java:359)
at org.eclipse.birt.report.engine.api.impl.EngineTask.initializeContentEmitter(EngineTask.java:2336)
at org.eclipse.birt.report.engine.api.impl.RunAndRenderTask.doRun(RunAndRenderTask.java:115)
at org.eclipse.birt.report.engine.api.impl.RunAndRenderTask.run(RunAndRenderTask.java:74)
at org.eclipse.birt.report.debug.internal.core.launcher.ReportLauncher.createReport(ReportLauncher.java:615)
at org.eclipse.birt.report.debug.internal.core.launcher.ReportLauncher.renderReport(ReportLauncher.java:561)
at org.eclipse.birt.report.debug.internal.core.launcher.ReportLauncher.run(ReportLauncher.java:475)
at org.eclipse.birt.report.debug.internal.core.launcher.ReportLauncher.main(ReportLauncher.java:119)
at org.eclipse.birt.report.debug.internal.core.ReportDebugger.start(ReportDebugger.java:39)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:203)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:137)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:107)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:401)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:657)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:594)
at org.eclipse.equinox.launcher.Main.run(Main.java:1447)
at org.eclipse.equinox.launcher.Main.main(Main.java:1420)
Caused by: java.io.FileNotFoundException: \default_report.rptdesign.html (Acceso denegado)
at java.io.FileOutputStream.open0(Native Method)
at java.io.FileOutputStream.open(FileOutputStream.java:270)
at java.io.FileOutputStream.(FileOutputStream.java:213)
at java.io.FileOutputStream.(FileOutputStream.java:162)
at org.eclipse.birt.report.engine.emitter.EmitterUtil.getOuputStream(EmitterUtil.java:77)
… 22 more

oct 13, 2020 9:51:08 AM org.eclipse.birt.report.debug.internal.core.launcher.ReportLauncher renderReport
GRAVE: Engine exception
org.eclipse.birt.report.engine.api.EngineException: Failed to initialize emitter.
at org.eclipse.birt.report.engine.emitter.EmitterUtil.getOuputStream(EmitterUtil.java:82)
at org.eclipse.birt.report.engine.emitter.html.HTMLReportEmitter.initialize(HTMLReportEmitter.java:359)
at org.eclipse.birt.report.engine.api.impl.EngineTask.initializeContentEmitter(EngineTask.java:2336)
at org.eclipse.birt.report.engine.api.impl.RunAndRenderTask.doRun(RunAndRenderTask.java:115)
at org.eclipse.birt.report.engine.api.impl.RunAndRenderTask.run(RunAndRenderTask.java:74)
at org.eclipse.birt.report.debug.internal.core.launcher.ReportLauncher.createReport(ReportLauncher.java:615)
at org.eclipse.birt.report.debug.internal.core.launcher.ReportLauncher.renderReport(ReportLauncher.java:561)
at org.eclipse.birt.report.debug.internal.core.launcher.ReportLauncher.run(ReportLauncher.java:475)
at org.eclipse.birt.report.debug.internal.core.launcher.ReportLauncher.main(ReportLauncher.java:119)
at org.eclipse.birt.report.debug.internal.core.ReportDebugger.start(ReportDebugger.java:39)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:203)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:137)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:107)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:401)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:657)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:594)
at org.eclipse.equinox.launcher.Main.run(Main.java:1447)
at org.eclipse.equinox.launcher.Main.main(Main.java:1420)
Caused by: java.io.FileNotFoundException: \default_report.rptdesign.html (Acceso denegado)
at java.io.FileOutputStream.open0(Native Method)
at java.io.FileOutputStream.open(FileOutputStream.java:270)
at java.io.FileOutputStream.(FileOutputStream.java:213)
at java.io.FileOutputStream.(FileOutputStream.java:162)
at org.eclipse.birt.report.engine.emitter.EmitterUtil.getOuputStream(EmitterUtil.java:77)
… 22 more

oct 13, 2020 9:51:08 AM org.eclipse.birt.report.debug.internal.core.vm.ReportVMServer$1 run
ADVERTENCIA: [Server] client disconnected

Any suggestion??

1 Like

No one? @AlexanderFillbrunn? @tobias.koetter? @Vincenzo?

Our workflow is creating this report (from KAP Report designer):

This workflow is working perfectly, and it is executed without errors. Also, the report is created and saved as PDF and HTML on the server (in /COMMIT/Informe_incidencias/Excel/), and a second workflow is executed after that:

This second workflow (Envio Correo 2) reads the HTML file and copy its HTML code to a string that is used as email body text. Also, the PDF file and two other Excel files (from the previous path) are attached to this email.

Bedore updating KAP to 4.2.2 and Server to 4.11, everything worked perfectly and graphs were included as HTML code inside the email (I have hidden data on table):

Now these emails don’t include the chart image, and also if we try to open the report in any format through the KAP Report Editor ("View report as…), we get the error included in my previous message.

Analyzing the HTML code in the emails, we have discovered that before the update, the images have this HTML code:

<img class=“style_7” id="__bookmark_2" src="data:image/png;base64

and now it seems to be:

<embed class=“style_7” id="__bookmark_2" onresize=“document.getElementById(’__bookmark_2’).reload()” type=“image/svg+xml” src="data:image/svg+xml;base64

Any idea?

Thank you in advance.

Hi @jricgar -

Sorry for the very delayed response on this thread. If it helps, you are not the only person experiencing this problem, and we are investigating - unfortunately, we’re not yet sure what the cause is. Once the team has some additional insight I will update this thread.

1 Like

Hello @ScottF Do you have some hints on how to fix this? I have a similiar issue, the reports runs fine on the server, but my local report complains “default_report.rptdesign does not exist or contains errors.”

Unfortunately, at the moment, I don’t. If you have a sample workflow that reliably reproduces the problem, it would be good if you could upload it for us to test with. Also, if you have excerpts of the server logs, that would be useful too.