I’ve just installed KNIME 5.1.1 using the zip archive. (Windows 10)
I already did some re-installation of a few extensions and on restarting, I’ve clicked the advertised update for 1 extension. It tells me there is a dependency conflict.
Looking at the message it appears that the KNIME AP Core Features update is conflicting with its former self…
Cannot complete the install because of a conflicting dependency.
Software being installed: KNIME AP Core feature 5.1.1.v202309110912 (org.knime.features.core.feature.group 5.1.1.v202309110912)
Software currently installed: KNIME Analytics Platform 5.1.1.v202309110912 (org.knime.desktop.product 5.1.1.v202309110912)
Only one of the following can be installed at once:
KNIME AP Core feature 5.1.1.v202309061330 (org.knime.features.core.feature.jar 5.1.1.v202309061330)
KNIME AP Core feature 5.1.1.v202309110912 (org.knime.features.core.feature.jar 5.1.1.v202309110912)
Cannot satisfy dependency:
From: KNIME Analytics Platform 5.1.1.v202309110912 (org.knime.desktop.product 5.1.1.v202309110912)
To: org.eclipse.equinox.p2.iu; org.knime.features.core.feature.group [5.1.1.v202309061330,5.1.1.v202309061330]
Cannot satisfy dependency:
From: KNIME AP Core feature 5.1.1.v202309061330 (org.knime.features.core.feature.group 5.1.1.v202309061330)
To: org.eclipse.equinox.p2.iu; org.knime.features.core.feature.jar [5.1.1.v202309061330,5.1.1.v202309061330]
Cannot satisfy dependency:
From: KNIME AP Core feature 5.1.1.v202309110912 (org.knime.features.core.feature.group 5.1.1.v202309110912)
To: org.eclipse.equinox.p2.iu; org.knime.features.core.feature.jar [5.1.1.v202309110912,5.1.1.v202309110912]
The fix to the problem is uninstalling the KNIME AP Core feature – it’s a “technical feature” that is not meant to be installed (it’s uncategorized/hidden from the end user). However, there currently is a bug that in some scenario(*) it gets automatically installed and that causes the symptoms above. You can safely uninstall it - it’s not going to break your installation (but instead enable the update).
(*) That scenario is the automated install of missing extensions when you open workflows containing 3rd party port type definitions (e.g. the Continently Excel nodes have their own type) – when one of these types are used in components then this technical feature is suggested to be installed, causing the problems above. We’ll fix this in a future patch release.
I have successfully (I think) uninstalled. As it took me a few moments to work out how to uninstall it, I thought I’d post a couple of screenshots in case anybody else hits this problem and needs to do the same.
First off is to go to “Install Knime Extensions” in Classic UI, or “Install Extensions” in Modern UI on the “resources page” found by click the (i) top right of modern UI screen.
From here, click what is already installed, then choose the item to uninstall
At this point it gave me a message that it cannot be fully uninstalled because other installed software is dependent on it, but that it would uninstall what it could.
Our DevOps team is currently looking at a temporary solution to fix the problem for other users running into it. We might be able to fix the problem by changing the version of that problematic feature on the online update site (without any code change).
We changed the KNIME update site so that this problem no longer occurs. For everyone who has successfully updated already: KNIME Analytics Platform will offer another update on the next restart - that’s expected (but doesn’t change any code - only some minor configuration.)
