However, even after restarting the Windows Service, the R Node (R Source (Table)) workflow - when run on the server - fails to pick up the new directory or the R packages installed to that directory. I get the same error message as before - suggesting the default R home location is selected.
Am I missing something here? How can I check what preferences are picked up by the Server?
The directive ‘-profileList executor’ tells the executor to get the client-profiles\executor directory from the server via REST call, then it combines all pulled profiles into a single combined-preferences.epf, which it then uses.
It isn’t working now because it can’t find the client-profiles\executor directory, because it doesn’t exist.
Move your file
C:\knime_server\workflow_repository\config\client-profiles\executor.epf
to
C:\knime_server\workflow_repository\config\client-profiles\executor\executor.epf.
Then restart the executor to make it pull the profileList again, and it should work.
Thanks so much for responding to my issue! After going through the Administration document for about the sixth time, I finally realised that I had made a stupid error. The section on setting the preferences in the knime.ini file has a split sentence, separated by the code snippet that required insertion. The sentence goes on to say ‘before the line containing -vmargs’. I had failed to notice this on multiple reads. After adding the snippet to the correct position, the server was able to find the preferences and started to pick up the new R Home location. Many thanks for your assistance though on this - appreciate it!