Hello there,
My KNIME crashes after running a few hours of a workflow. And it shows many errors when opening that workflow file. Attached are the knime log file and Workspace Error log file as well as the screenshot of the errors when opening this workflow. How can I resolve these 2 issues? Thank you so much as always.
knimeLog.log (393.7 KB) Workspace Error Log.log (125.2 KB)
Hey @alabamian2,
it seems that the workflow you are opening was saved by an installation, which doesn’t allow to store passwords in workflows. The error basically says, that the login credentials were removed by saving the workflow and that the nodes that need these credentials need to be reconfigured. So you need to enter credentials in the Get Request node.
You might also need to install the Google BigQuery database driver. We are not allowed to ship the driver with the BigQuery extension, so you need to install it manually.
Here is a guide on how you can do it.
I can see some authentication errors in the log regarding the Send Email node as well, so this one might need to be configured properly.
Did you need to install some extensions after using the workflow for the very first time? It could be that you accidentally saved the workflow before restarting KNIME due to the installation so that some nodes went missing as well. I would try to reset your workflow and check every node configuration that needs some credentials and set the driver as mentioned above.
Best,
Julian
Hello @julian.bunzel,
Wow, I am going to address all these issues. Thank you so much for pointing these out. The workflow executes fully, but I’ll check those nodes and see what’s going on. Thank you for taking the time to review.
Hi @julian.bunzel,
Yes, that makes total sense. I installed KNIME on another PC and exported-imported the workflows so that must be when these errors occurred and yes that when I started seeing these errors now that you pointed out.
Regarding email, I was sending emails using gmail and it was working fine until sometime last week when it started generating this error. I checked everything and tried different gmail accounts but they all fail. I’m wondering if others are experiencing the same issue, but I haven’t seen any post in the forum about gmail stopped working.
ERROR Send Email 0:3484 Execute failed: Error while communicating with the smtp server: javax.mail.AuthenticationFailedException
Thank you again for all the help and support, @julian.bunzel. I really appreciate your time.
Hey @alabamian2,
sorry for the late response.
Did you update something in your Gmail preferences?
You need to enable access for “less secure apps” in your Gmail preferences. If you have enabled this already, I’d recommend checking the SMTP address.
Best,
Julian
Hi @julian.bunzel,
No, Gmail setup and the node used to work perfectly until Jan 16 Sat night and I didn’t change anything. The setting is
smtp.gmail.com
port 465
smtp host needs authentication checked
connection security SSL
connection timeout 200,000 ms (I upped it just in case)
read timeout 30,000 ms
There seem to be other setting used for gmail from different forum threads but this one used to work. I did enabled access to less secure apps for this gmail. And I tested this again using 3 different gmail accounts now, all failing with the same errors. and since this error is just 1 line, I’m not sure what to change.
I wonder if others are having the same issue. Thank you so much for your help kindly.
ERROR Send Email 4:103 Execute failed: Error while communicating with the smtp server: javax.mail.AuthenticationFailedException
Hello @julian.bunzel,
I re-did this again and it worked this time. Phew, maybe I should be more persistent and try the same attempts several times over a period of time. I did this step with 2 gmails a couple of weeks ago and both failed. Now it’s working!!! Yay, thank you for your help, @julian.bunzel!!
@julian.bunzel, thank you for being persistent and kindly following up with these threads. Without your kind reach out, I may not have tried it again for a while. Thank you!!
You’re welcome!
Great to hear that it’s working again 
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
