Several nodes unavailable and uninstallable

Hi,

since recently I face an issue where Knime complains about a missing extension.

ERROR LoadWorkflowRunnable                      Status: Error: Node "Java Edit Variable" not available from extension "KNIME Javasnippet" (provided by "KNIME AG, Zurich, Switzerland"; plugin "org.knime.jsnippets" is installed)
ERROR LoadWorkflowRunnable                    Status: Error: Node "Rule-based Row Filter" not available from extension "KNIME Javasnippet" (provided by "KNIME AG, Zurich, Switzerland"; plugin "org.knime.jsnippets" is installed)
ERROR LoadWorkflowRunnable                      Status: Error: Node "String Manipulation (Multi Column)" not available from extension "KNIME Javasnippet" (provided by "KNIME AG, Zurich, Switzerland"; plugin "org.knime.jsnippets" is installed)
ERROR LoadWorkflowRunnable                      Status: Error: Node "String Manipulation" not available from extension "KNIME Javasnippet" (provided by "KNIME AG, Zurich, Switzerland"; plugin "org.knime.jsnippets" is installed)

KNIME Javasnippet 5.2.0.v202310301555

The search finds it but I cannot pass the install screen:

Searching for the nodes in question in the workflow I happen to find disconnected sections where there should be nodes.

Edit: The above issue might be caused by this:

ERROR LoadWorkflowRunnable                    Status: Error: Unable to load node with ID suffix 1007 into workflow, skipping it: Could not initialize class org.knime.base.node.io.filehandling.table.reader.KnimeTableMultiTableReadConfigSerializer
ERROR LoadWorkflowRunnable                    Status: Error: Unable to load node with ID suffix 984 into workflow, skipping it: Could not initialize class org.knime.base.node.io.filehandling.table.reader.KnimeTableMultiTableReadConfigSerializer
ERROR LoadWorkflowRunnable                  Status: Error: Unable to load node with ID suffix 1017 into workflow, skipping it: Could not initialize class org.knime.base.node.io.filehandling.table.reader.KnimeTableMultiTableReadConfigSerializer
ERROR LoadWorkflowRunnable                  Status: Error: Unable to load node with ID suffix 1034 into workflow, skipping it: Could not initialize class org.knime.base.node.io.filehandling.csv.reader.CSVMultiTableReadConfigSerializer

I’d usually expect this:

image

Should I split this apart from this topic?

Best
Mike

@mwiegand I have seen this a lot with the native Apple Silicon variant of KNIME which brought me to currently mostly using the Intel version. On Windows I have not seen this behaviour.

My impression is that somewhere deep inside there is a problem preventing KNIME from detecting and installing nodes.

Good morning @mlauber71,

that is interesting and quite concerning to hear. The fact that this issue seems to be present for others, impacting basic / core nodes of Knime and wracking havoc in workflows by removing nodes, I’d guess would get addressed with utmost priority.

@armingrudd do you happen to know if there is already a ticket? I also wonder if such information isn’t automatically reported if sharing of data in Knime got enabled.

Best
Mike

We are looking into it. Thank you @mwiegand for reporting!

2 Likes

У меня такая же проблема с такой же нодой.
Иногда она исчезала после переустановки knime или пакетов.
Но всё-равно повторяется через какое-то время.
Сообщения об ошибке такие:
2024-03-03 15:16:12,525 : ERROR : ModalContext : : LoadWorkflowRunnable : : : Errors during load: Status: Error: BSL 3 loaded with errors
2024-03-03 15:16:12,525 : ERROR : ModalContext : : LoadWorkflowRunnable : : : Status: Error: BSL 3
2024-03-03 15:16:12,525 : ERROR : ModalContext : : LoadWorkflowRunnable : : : Status: Error: Unable to load node with ID suffix 23 into workflow, skipping it: Could not initialize class org.knime.core.data.convert.datacell.OriginAwareJavaToDataCellConverterRegistry
2024-03-03 15:16:12,525 : ERROR : ModalContext : : LoadWorkflowRunnable : : : Status: Error: Node “String Manipulation” not available from extension “KNIME Javasnippet” (provided by “KNIME AG, Zurich, Switzerland”; plugin “org.knime.jsnippets” is installed)
2024-03-03 15:16:12,526 : ERROR : ModalContext : : LoadWorkflowRunnable : : : Status: Error: Node “String Manipulation” not available from extension “KNIME Javasnippet” (provided by “KNIME AG, Zurich, Switzerland”; plugin “org.knime.jsnippets” is installed)
2024-03-03 15:16:12,526 : ERROR : ModalContext : : LoadWorkflowRunnable : : : Status: Error: Node “String Manipulation” not available from extension “KNIME Javasnippet” (provided by “KNIME AG, Zurich, Switzerland”; plugin “org.knime.jsnippets” is installed)
2024-03-03 15:16:12,526 : ERROR : ModalContext : : LoadWorkflowRunnable : : : Status: Error: Node “String Manipulation” not available from extension “KNIME Javasnippet” (provided by “KNIME AG, Zurich, Switzerland”; plugin “org.knime.jsnippets” is installed)

Here is @R72 translation into english:

I have the same problem with the same node.
Sometimes it disappeared after reinstalling knime or packages.
But it still repeats itself after some time.
The error messages are:

Adding to this I happen to recall that there was also an error about Rule Engine Dictionary node. Just today, I noticed it underwent a change. I suspect, though, this might not be a coincidence.

После нескольких открытий и закрытий knime сейчас проблема исчезла - нода String Manipulation восстановилась как ни в чем не бывало.
Думаю это ненадолго.
Сейчас снова закрыл Knime и открыл его - ошибка повторилась - нода String Manipulation сломалась.

Такая же ошибка была с нодой вида regex.
Но пока больше она не повторяется и не воспроизводится - нода в наличии на рабочем пространстве.

@R72 пожалуйста, используйте Google Translate для ответа. Это увеличит ваши шансы на решение.

I wrote: Please use Google translate for you reply. This will increase your chances of a solution.

His two comments are:

After opening and closing knime several times, the problem has now disappeared - the String Manipulation node has recovered as if nothing had happened.
I think this won’t last long.
Now I closed Knime again and opened it - the error repeated - the String Manipulation node broke.

The same error occurred with a regex node.
But for now it is no longer repeated or reproduced - the node is available in the workspace.

1 Like

Эта тема всплывала 2 года назад и никак не решилась.

1 Like

Похоже проблему удалось решить или хотя бы уменьшить вероятность её до исправления производителем.
Надо сделать так:

  1. Установить Knine
  2. В File-Preferences-Install/Update-AvailableSoftwareSites установить расширение
    https://download.nodepit.com/5.2
  3. Сделать InstallKnimeExtensions - установить все составляющие без исключения
  4. Перезагрузить Knime
  5. В File-Preferences-Install/Update-AvailableSoftwareSites удалить расширение
    https://update.knime.com/analytics-platform/5.2
  6. Перезагрузить Knime
  7. У меня заработало - нода String Manipulation стала появляться нормально.
    Аналогично исчезла проблема с нодами Spark (Table to Spark и т.п.)

PS Нет, не помогло.
После нескольких перезагрузок проблема возобновилась.

Here is the english translation

It looks like the problem has been resolved, or at least the likelihood of it being reduced until the manufacturer fixes it.
You need to do this:

  1. Install Knine
  2. In File-Preferences-Install/Update-AvailableSoftwareSites install the extension
    https://download.nodepit.com/5.2
  3. Make InstallKnimeExtensions - install all components without exception
  4. Restart Knime
  5. In File-Preferences-Install/Update-AvailableSoftwareSites remove the extension
    https://update.knime.com/analytics-platform/5.2
  6. Restart Knime
  7. It worked for me - the String Manipulation node began to appear normally.
    Similarly, the problem with Spark nodes (Table to Spark, etc.) has disappeared.
    PS No, it didn’t help.
    After several reboots the problem returned.

The problem was solved in another way (for now):
After in Knime in File-Preferences-Install/Update-AvailableSoftwareSites extension
https://update.knime.com/analytics-platform/5.2 installed in version 5.3
After several reboots, knime installed all the other extensions himself in version 5.3 (Night).
After that, the problems with the disappearance of the nodes stopped.
Two days and a dozen restarts of knime are normal, the nodes do not go astray.

@CarlWitt in regards to the findings from R72 that using the nighty build seems to have resolve the issue, did you or a colleague of yours found anything?

No, the overnight build didn’t solve anything by itself.
Earlier, I put the night build on purpose - it helped for one reboot and knime broke down in the nodes again.
So far, the option has worked not just to install a nightly build, but to pre-delete the old java from the Liberika SDK, clean up all traces and install java from Oracle.

The issue appeared for me again today in a workflow that was flawlessly working in the past days. Attached the thread dump and console log.

240308 knime thread dump topic 77549.txt (67.7 KB)

240308 knime workflow log topic 77549.txt (41.8 KB)

I’ve made the same mistake again.
The String Manipulation node has flown off again. This happened after updating the Knime elements (I have set up an update check every day).
I fixed it by specifying files to download from version 5.3
I have nightly build installed
The Preferences-Install/Update-Available Software Sites list the sites for versions 5.2 and 5.3
Version 5.2 was disabled.
The node recovered and worked fine after several reboots.
After the next Knime update, the node disappeared again.
I fixed it again like this:
The Preferences-Install/Update-Available Software Sites list sites for version 5.3 made disable, and sites for version 5.2 enable.
Rebooted Knime.
The node has appeared again and everything is working fine.
Next time, I think switching to 5.3 will help again.

@CarlWitt I happen to notice a possible trigger of the issue. When starting Knime I very quickly opened a workflow and believe Knime was still running some startup processes like checking for updates. Hence, the issue can be resolved by giving Knime enough time to start and check for updated before opening a workflow.

Even after restarting knime the issue persisted. Worth to mention there are indeed updates (related to v5.2.3).

I was, with the approach of quickly opening a workflow, able to consistently reproduce the issue. Here is the most recent log where it appeared and the second I reproduced it:

240328 knime.log (230.0 KB)

240328 knime 2.log (528.2 KB)

I will refrain momentarily from updating to 5.2.3 in case you’d need more details.

Best
Mike

1 Like