Hello to the team,
I had a very strange behavior of KNIME today. During editing of a workflow, KNIME closed apruptly, without error message. After this, the knime.exe was gone from the KNIME installation directory. Also, the workflows that were open at the time were deleted from the workspace directory. And on top, the backup (export .knwf) files of the workflows were deleted from my synchronized Sharepoint folder, where I had synchronized the workflows to some 10 minutes earlier.
This has happened twice today, with different workflows.
After the first time, I replaced the knime.exe with the file from a colleague’s installation, so I was able to try again and experience the error again.
We searched for some log files that might contain any indication to the cause of this error, but found no log that had anything related to the correct time of the incident.
Is this something you want to research? If you tell me which log files in which folder you need, I would be happy to supply that.
Best regards,
Jan
That sounds very crazy.
The first idea coming to my mind is a virus. But I assume that a destructive virus would destroy more that just the program and some associated data (workflows).
The second ideas focusses on problems with the hardware you are using (e.g. corrupted file system)
Maybe you can share more details about then IT environment you are working in and with (e.g. OS) and the KNIME software (KAP, Hub, …) and version you are running. How was KNIME installed: centrally by IT, just unzipped?
2 Likes
I am working on Windows 11 2025H2.
Incidentally, the 2025H2 update was installed 2 days ago; maybe this is an issue with that release? IT will now deinstall that update and we will test whether that was it.
The KNIME version I am working with is 5.3.2. I know there is a newer one, but the last update we tested created problems on our Linux machines, so we wanted to wait until the next one.
KNIME was installed via the installation .exe file.
It is still happening after deinstalling the 2025H2 Windows 11 update. I can narrow it down a bit: it always happens when saving a workflow. We will try to test the new 5.8 version as soon as possible to see if switching resolves this.