Hmm, seems like KNIME can’t properly connect to RServe. We can still try to narrow it down.
Can you still run R itself? cmd or RStudio shouldn’t make a difference, just want to know if it still works
What version of R and RServe do you have?
Did you update those as well, or just KNIME?
Do the KNIME preferences still point to the RServe.exe, or did the upgrade to 4.5.1 mess them up?
Which KNIME version did you upgrade from?
sessionInfo() for the R version (4.0.3 for me) packageVersion("RServe") for the RServe version (126.96.36.199 for me)
Well, this is weird. I was hoping for an attack point. If you didn’t touch R there’s no reason to look for the cause there.
Glad that @mlauber71 is joining the fray because I’m running out of ideas. Your IT department could just reinstall the current KNIME version, maybe something went wrong with the upgrade. If you can reinstall the R extension without them, I’d try that because it’s quick.
And also the obvious “have you tried turning it off and on again?”. I know how that sounds, but it actually worked for me once.
@Thyme from what I see there has been heavy editing in the specific parts of the R integration concerning the very path variables (to integrate the conda paths to an R installation) so I think it entirely possible that something went wrong under specific circumstances.
I was not immediately able to spot the problem. At a certain point the path gets replaced by something it should not … I see a removed blank and different PATH syntaxes …
For what it’s worth. I’ve migrated to 4.5.1 too an my R-nodes still work as before. I’m using Windows10, own specified path to my directories containing R-3.6.3 (which is not a conda environment) and using RServe package 1.8-7.
Sorry for joining the discussion so late. I am a bit puzzled how this issue only exists with 4.5.1 and not 4.5.0 because the commit in question was released with 4.5.0.
However, I would like to understand the problem to fix it. @salazachou, @schuppius, does one of you have a “stacktrace” of the error? You can find it in the KNIME log (View → Open KNIME log). I don’t see what could go wrong in this part of the code and a stacktrace would help me to locate the exact location.