Hi, if anyone can help it would be appreciated.
I keep getting errors like this when trying to save workflows. Usually this happens after a period of absence from the computer, there is just no way to save the workflow, and neither does it allow you to save as a different name, publish to Server, or export. This is particularly a concern when changes have been made and there simply is no way to know what those changes are and whether they will be saved or not. Please advise?
2020-09-14 23:58:47,668 : FATAL : ModalContext : : InplaceSaveRunnable : : : File not found - this exception will be re-thrown as an InterruptedException.
java.io.FileNotFoundException: C:\Users\AppData\Local\Temp\knime_GL_Bank_Prep_fo83972\knime_container_20200913_7657928779082410725.bin.snappy (The system cannot find the file specified)
at java.io.FileInputStream.open0(Native Method)
2020-09-14 23:58:47,699 : ERROR : main : : WorkflowEditor : : : Could not save + workflow: File access problems: C:\Users\AppData\Local\Temp\knime_GL_Bank_Prep_fo83972\knime_container_20200913_7657928779082410725.bin.snappy (The system cannot find the file specified)
java.lang.InterruptedException: C:\Users\AppData\Local\Temp\knime_GL_Bank_Prep_fo83972\knime_container_20200913_7657928779082410725.bin.snappy (The system cannot find the file specified)
Thanks mlauber71. I ended up copying the workflow to a new workflow and saving that as a new version (phew!). I’ll work on changing the internal compression to gzip and check out the additional link - thanks!
Now, previous workflows built when the compression was the default ‘SNAPPY’ do not seem to run properly, and cause KNIME to freeze (which is very odd for KNIME). Upon changing the .ini file back to SNAPPY my workflow ran fine. Now my issue is I don’t know which files were run with SNAPPY and which were run with GZIP compression, some workflows were partly built with both compression setups. I have been noticing a lot more failures with my workflows and not sure how to get them back to normal, pretty sure this is the cause.
@knime - I’d be happy to provide details of this problem to help it be addressed!
This indeed does sound strange. Typically if you reset a workflow I would expect it to revert to the default compression next time. And at least with zip or parquet KNIME seems to be happy with using both. Cf. also this entry:
Question is if you reset a workflow would it then run Ok.
If a workflow is stored with data in it you could:
export it into a knwf file without data stored
rename the original WF
import the stored one
Now you should have a working WF.
Then could you tell us more about your system and setup and versions. And maybe provide a fresh log file set to debug. Maybe someone from KNIME then can weight in.