I have a workflow that uses the external tool node. The node run a vb script using cscript.exe. It works great when running it manually, however it doesn’t work when scheduling it.
Can we deploy cscript.exe to the server so the scheduler knows where to pick up the exe and run my script?
Just to see if I got it right what you are trying to achieve. You want to execute Refresh.vbs on your input file (data from KNIME) under cscript.exe? In order for it to work in your KNIME Server environment not only should you deploy your exe but also vbs and your paths to input and output files should be accessible from KNIME Server or modified.
If I misunderstood something give it another go and we’ll try to figure it out.
I see. I suggest you use relative paths in these cases. Create data folder within your workflow folder and there create text.csv file. Relative path to the file is then knime://knime.workflow/data/text.csv. This way transferring your workflow to Server or sending it to colleague doesn’t affect execution. Also you can create script folder in the same place and access Refresh.vbs and cscript.exe with relative paths. If the exe is too big and you will use it in multiple workflows having it with every workflow doesn’t make sense so find an adequate place on your KNIME Server and point your External Tool node to it.
I guess you KNIME Server is on Windows as your exe applies to Windows only?
My suggestion is to keep your files and scripts within your workflow folder and then deploying workflow to KNIME Server means transferring your files to Server as well. In that case using relative paths makes sense
If I use the csv reader node to read a csv (knime://knime.workflow/data/text.csv), KNIME doesn’t complain, however the external tool node throws the below error.
Put it in a network drive somewhere both the Server can see it and your PC. Preferable an absolute path.
To be absolutely sure log into the machine that knime server is on as the “service” account knime is running (if you don’t have the credentials get your system admin to do it for you) on to check if that user can see where you have put the files.
Just path the path of the executable and the like into windows explorer on the server machine.
I doubt the server will be able to “see” the c:\users\lava…" folder, hence the error message.
I’ve tried putting the file in a shared drive as you can see from the original post, and no luck.
I didn’t want to have to go through my system admins, but it looks like this may be the only option.
I’ll start the conversation with my sys admins and post my results.
I’ve recently been working with the External SSH Tool to see if it can help me achieve what I’m trying to do. From my understanding, it creates an SSH connection to remote host (KNIME server) which would run my .exe and .vbs. I’ve played around with the parameters, but I’m not sure how to configure it before the External Tool node. Can the External SSH Tool help my approach?