I’ve encountered an issue with KNIME Analytics Platform after the latest update on my Mac. When I open KNIME, it automatically tries to open a specific workspace repository that I did not create or set as default. It creates this workspace on my computer without my consent and ignores my actual workspace, which is located in a different directory.
Even when I delete this unwanted workspace, it reappears the next time I open KNIME, forcing me to manually change the workspace location every time.
This issue started happening only after the recent update, and it seems like a bug.
Any help or suggestions would be greatly appreciated.
Confirmed. But cannot reset workspace from classic interface. Must swap to modern UI, change workspace, then swap back to classic UI.
No data loss, even restores previously open workflows.
Have also tried importing saved preferences in case preferences corrupt, but that didn’t make any difference to above behaviour.
@VAGR_ISK@JPollet do you have the Palladian extensions installed and can you try un-installing them and see if the problem goes away? It tried this on my Windows machine and it seems to work.
I re-installed Palladian. After the first re-start everything was fine but with the next one the problem started to appear (again).
Palladian for KNIME 3.1.1.202409151310 ws.palladian.nodes.feature.feature.group palladian.ws
(I took the two by the way), Knime first re-opened on the “correct” workspace but then, after an other close and start, Knime opens on the default workspace in the default location.
So, here’s my Road to Canossa: This one is on me - I am sorry!
Turns out that the recent updates for the Palladian and Spellchecker nodes had a bug which caused this issue on KNIME 5.3.
There’s updates for Palladian (v3.1.2) and Spellchecker (v1.3.3) available now which address this. Please install the updates, restart KNIME, select the proper workspace location once again and all should be back to normal.
FAQ:
Did the bug lead to any data loss? - No.
Which KNIME versions were affected? - KNIME 5.3 and newer.
When did it happen? - If a non-standard workspace location was selected.
What did happen? - The mentioned nodes contain a mechanism which automatically keeps your update site URLs at the proper version and which is intended to make future updates less of a hassle. It is to address the common issue, that people use e.g. a Palladian Nodes update site in their KNIME 5.3 which was originally intended for KNIME 5.2 and thus provides no compatible updates. Turns out that this functionality broke in KNIME 5.3 due to an incompatible change - this is addressed now and the feature should work as expected.
Anything left unanswered? - Let me know.
A big THANK YOU goes to @danielesser who spent his early morning debugging and fixing this and helping to roll out this fix rapidly - I owe you! Also thank you to @mlauber71 for the pointer in the right direction.
Hi @qqilihq
Thanks for the update of Palladian extensions and the clear explanations. Restart twice Knime after update Palladian and all works well again.
Best,
Joel
