I’ve seen this odd message several times now saving my workflow:
Could not save workflow: Exception while accessing file: “/Volumes/SAMSUNG/knime-workspace5/Smartney/Smartney2/Bar Chart (#54)/internalTables/object_2/data.zip”: /Volumes/SAMSUNG/knime-workspace5/Smartney/Smartney2/Bar Chart (#54)/internalTables/object_2/data.zip (No such file or directory)
Deleting the offending node allows the save to proceed. Recreating the bar chart works fine, and sometimes allows saving - but not always.
Resetting the node also allows the save to complete.
I have not seen this problem so far. Seems like the data object it tries to access is not available anymore. Can you give me a bit of context about your Workflow and operating system? Can you maybe even share the workflow or a minimal version of this workflow?
I’m on a Mac Pro, latest MacOS, running KNIME V5.1.1
Perhaps relevant is that the workflow is stored on an external SSD? Spurious error? I have many bar charts and only one (but not the same every time) of them gives the error. Like I said, resetting (which deletes the data) allows me to save it. Never any problems in executing it, so the data is definitely there.
I checked the log, and the relevant portion seems to be this:
2023-09-16 20:37:48,638 : ERROR : ModalContext : : InplaceSaveRunnable : : : Could not save workflow - this exception will be re-thrown as an InterruptedException.
java.lang.RuntimeException: Exception while accessing file: "/Volumes/SAMSUNG/knime-workspace5/Smartney/Smartney3/Bar Chart (#38)/internalTables/object_2/data.zip": /Volumes/SAMSUNG/knime-workspace5/Smartney/Smartney3/Bar Chart (#38)/internalTables/object_2/data.zip (No such file or directory)
at org.knime.core.data.container.BufferedContainerTable.ensureBufferOpen(BufferedContainerTable.java:346)
at org.knime.core.data.container.BufferedContainerTable.getTableStoreFormat(BufferedContainerTable.java:243)
at org.knime.core.node.BufferedDataTable.save(BufferedDataTable.java:612)
at org.knime.core.node.FileNodePersistor.saveBufferedDataTable(FileNodePersistor.java:1439)
at org.knime.core.node.FileNodePersistor.saveInternalHeldTables(FileNodePersistor.java:1286)
at org.knime.core.node.FileNodePersistor.save(FileNodePersistor.java:1205)
at org.knime.core.node.workflow.FileNativeNodeContainerPersistor.save(FileNativeNodeContainerPersistor.java:519)
at org.knime.core.node.workflow.FileSingleNodeContainerPersistor.save(FileSingleNodeContainerPersistor.java:640)
at org.knime.core.node.workflow.FileWorkflowPersistor.saveNodeContainer(FileWorkflowPersistor.java:2302)
at org.knime.core.node.workflow.FileWorkflowPersistor.saveContent(FileWorkflowPersistor.java:2050)
at org.knime.core.node.workflow.FileWorkflowPersistor.save(FileWorkflowPersistor.java:1941)
at org.knime.core.node.workflow.WorkflowManager.save(WorkflowManager.java:9363)
at org.knime.workbench.editor2.InplaceSaveRunnable.save(InplaceSaveRunnable.java:92)
at org.knime.workbench.editor2.AbstractSaveRunnable.run(AbstractSaveRunnable.java:103)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)
Caused by: java.io.FileNotFoundException: /Volumes/SAMSUNG/knime-workspace5/Smartney/Smartney3/Bar Chart (#38)/internalTables/object_2/data.zip (No such file or directory)
at java.base/java.io.FileInputStream.open0(Native Method)
at java.base/java.io.FileInputStream.open(Unknown Source)
at java.base/java.io.FileInputStream.<init>(Unknown Source)
at org.knime.core.data.container.CopyOnAccessTask.createBuffer(CopyOnAccessTask.java:153)
at org.knime.core.data.container.BufferedContainerTable.ensureBufferOpen(BufferedContainerTable.java:344)
.. 14 more
2023-09-16 20:37:48,802 : ERROR : main : : WorkflowEditor : : : Could not save workflow: Could not save workflow: Exception while accessing file: "/Volumes/SAMSUNG/knime-workspace5/Smartney/Smartney3/Bar Chart (#38)/internalTables/object_2/data.zip": /Volumes/SAMSUNG/knime-workspace5/Smartney/Smartney3/Bar Chart (#38)/internalTables/object_2/data.zip (No such file or directory)
java.lang.InterruptedException: Exception while accessing file: "/Volumes/SAMSUNG/knime-workspace5/Smartney/Smartney3/Bar Chart (#38)/internalTables/object_2/data.zip": /Volumes/SAMSUNG/knime-workspace5/Smartney/Smartney3/Bar Chart (#38)/internalTables/object_2/data.zip (No such file or directory)
at org.knime.workbench.editor2.AbstractSaveRunnable.handleRunExceptionCleanUp(AbstractSaveRunnable.java:153)
at org.knime.workbench.editor2.AbstractSaveRunnable.run(AbstractSaveRunnable.java:127)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)
The whole log is rather big, is this extract enough?
I can explain what is happening, or at least what is supposed to happen:
There is a workflow that you created with an older version of KNIME AP, say 4.7. The node in that workflow is executed. When you then open the workflow in 5.1, make some modification and save it it’s going to fully load&save the workflow since the workflow format has slightly changed. (This doesn’t happen for every KNIME release but it did happen between 4.7 → 5.1.)
Note that while you are saving it’s first loading the entire workflow (no incremental save) due to the format change … and this is where the problem is reported. During load it’s loading that bar chart node and that causes problems (/Volumes/SAMSUNG/knime-workspace5/Smartney/Smartney3/Bar Chart (#38)/internalTables/object_2/data.zip no longer present).
Two questions:
Do you have the original workflow still somewhere in the backup? Does the above file exist?
Many thanks for the explanation… but it cannot be quite the whole story. I created this particular workflow in v5.1.0, not in 4.7.7. I now create all new wfs in v5, but more often than not use the classic interface.
When deleting and recreating the node (bar chart - it has never happened with another node) it mostly works (for instance, yesterday - today the error has not occurred, I tried…). So it’s intermittent, not systematic.
I have not changed the backed from the standard, so it’s row, not tabular.
If it occurs again, I’ll post the fresh log entry.
I’m learning something new here. If you have any particular workflow that you think will cause the problem it’d be great if you could create a backup of that workflow before running into the problem. Maybe we can diagnose the original workflow.
