There is a new KNIME forum. You can still browse and read content from our old forum but if you want to create new posts or join ongoing discussions, please visit our new KNIME forum:

Error in KNIME 3.4 with reporting

Member for

3 years 2 months Kristof


Using Knime 3.4.0 on MAC OS v10.12.5

When I read in a small 4 X 3 CSV file and attach it to a reporter node I see the correct file at the reporter node. (see screen copy attached)

When I then call the reporter using the Icone or menu I get the message (screen copy attached):

The file has been deleted from the fiel system. Do you want to save your changes or close the editor without saving?

I press save and get the "save as" message (screen copy attached):

When I choose cancel as only possibility I get the following exception error (also attached)

Really gutted I can not get this to work.
Hope one or another KNIME wizard can help me
Kind regards


Thu, 10/26/2017 - 05:53

Member for

7 years 11 months


Hello, dear KNIMErs,

opening the Reporting Tool I get the same error messages as Kristof (see screen_shot_2017-07-12_at_13.05.07.png and screen_shot_2017-07-12_at_12.59.33.png), but with a little variation in the final error message:

"An error has occurred. See error log for more details. java.lang.RuntimeException: No "workflow.knime" file in directory [Workflow Folder]".

The console just states "ERROR KnimeReportHandle               Error while handling editor switch!"

Having created a workflow with report, I get this error when I use the "Save as" option. Deleting the two default report files (see… ) does not help. I also get the error when I export a workflow with report and import it in another workspace folder.

I use KNIME 3.4.1 on Windows 7 64bit



Tue, 12/12/2017 - 02:07

Member for

4 years 11 months


Hey Kristof, hey Alex,

What information does your logfile contain regarding this problem? Can you upload it?

Sometimes the reporting is a little picky regarding file locations. Can you try a fresh workspace and import the workflow, or even better, recreate the workflow and test whether that solves it?