I have just updated the RDKit collection and I get the "Could not load native RDKit Library" warning in a workflow that was working minutes before the update.
The machine on which the workflow is running is a 64 bit Windows. I read a few posts about an issue with x64 architecture. Did the wrong version of the library get installed? How do I revert back to the one that was working?
I would like to try to reproduce your issue. What KNIME version are you running? Also, could you please check what Java version is used by KNIME? Just enter the following in a command shell and replace %KNIME% with your install directory to find out the Java version:
The RDKit versions I have installed are shown in dialog Help => About KNIME => Installation Details:
Tab Installed Software (Feature):
RDKit KNIME Integration 2.1.0.210302211506.
Tab Plugins:
RDKit Chemistry Type Definition Plugin 2.1.0.201302041554
RDKit Nodes for Knime 2.1.0.201302211506
RDKit binaries for 64-bit Windows 2.1.0.201302061056
Please check your versions - I have the feeling that you may still have gotten an older version. There is a chance that the Community update site was not fully updated yet when I posted my announcement.
good to hear. You are right with the typo, you have the correct versions.
Just curious: Did you restart Eclipse after you updated the RDKit Nodes before running the failing workflow? As native DLLs are involved in the RDKit nodes this is crucial.
With "restart" I mean closing the Eclipse application and starting it again. Usually, it would ask you to do this anyway when you install a new plugin or update an existing one.
As it works now I do not think we need to pursue this any further.
Thanks for your reply. Unfortunately, it does not work. I was under the impression that it was working as the nodes were displaying a green traffic-light icon. However, trying to run the workflow yields the same error. Sorry for the confusion.
If by closing the Eclipse application you mean restarting KNIME, then yes, I restarted it.
Can you think of anything else I could try? It is a shame: thanks to the RDKit nodes, I was close to implementing an error-free solution and now, because of the update I performed, I cannot use this solution anymore.
This could be a java 1.7 problem. The nodes were definitely built for java 1.6 and I personally haven't tested them with 1.7.
I don't have a Mac with 1.7, so I can't test this out to see what's going on, but I should be able to do some testing later in the week when a colleague with a more up-to-date Mac gets back from vacation.
sorry that the issue is still not resolved. I am unable to reproduce it on Windows and have no Mac. Could you please send me more information in an email (with attachments)? Send it to manuel.schwarze(at)novartis.com.
Please send me your configuration: Open KNIME and select from the menu Help - About KNIME. Click the Configuration tab and copy and paste everything into a text file config.txt and send this to me.
Please prepare a knime.log file: Close KNIME. Go into your workspace folder and there remove the file .metadata/knime/knime.log. Then restart KNIME and try to use the RDKit nodes as you did before. Close down KNIME again after the failure and send me the new created file .metadata/knime/knime.log from your workspace.
I am experiencing the same problem with the update.
"Could not load native RDKit Library"
Attached to this post you will find the error stack trace (logs) + snapshot with the plugins installed in a _fresh_ KNIME 2.7.2 installation. Hope it helps to solve to problem.
Is this issue on MAC OSX, if so there is an immediate solution.
Unfortunately there was an error in the KNIME MAC build which results in RDKit not working when this extension is installed. This was rectified last night, and deleting your KNIME install and downloading afresh from KNIME.org will solve the problem with the RDKit native library errors. Thanks to Aaron for this quick fix.