if I try to read files from the server or write files to server using the Explorer Browser and Explorer Writer Nodes, then I get following error messages:
There are messages for workflow “02_Write_files_into_the_Server_Repository 2018-07-03 11.14.20”
URL to File Path (Variable) 0:6 - ERROR: Configure failed (IllegalArgumentException): URI is not absolute
CSV Writer 0:20 - ERROR: Configure failed (IllegalArgumentException): URI is not absolute
Explorer Writer 0:19 - ERROR: Execute failed: URI is not absolute
If the workflow runs on my local machine everything works fine, but if I run it on the server I get the errors.
In the nodes i use the knime protocol for the path. I tried knime://knime.mountpoint/test.csv and knime://knime-server-prod/test.csv.
which version of KNIME Analytics Platform are you running locally in conjunction with which KNIME Server version? It’s possible that this error is due an expired licensed (which should not happen with newer KNIME Analytics Platform/Server combinations).
The problem why the workflow doesn’t work on a server is the URL to file Path (Variable) node which currently does not work on a server. I’ve updated the workflow so that it also works on a server and it will be soon updated on the Examples server, for now please find attached the updated workflow.
That’s interesting. We can’t reproduce the error on our 4.4.2 test machine - which doesn’t have to mean anything. It could, however, be that this particular bug has been fixed between 4.4.0 and 4.4.2. Is it possible for you to update the installation to 4.4.2 to see if the issue persists?
Also, which operating system is the server running on?
No it’s not possible for me to update the installation on the server, because it is the server of the university of applied sciences. Maybe my professor can do something to update it. He already contacted you per email.
The operating system of the server is an Ubuntu 16.04.3.
If I’m using the absolute paths on the server like /home/knime/… then everything works as expected. Only if try accessing the files via knime protocol, I get the error messages.
If that’s the case it would be helpful to get the log files of the executor (there are instructions on that in the Server Administration Guide), since I can’t reproduce the issue on my KNIME Server 4.4.0 instance.