How to resolve ERROR: TOOLKIT [be_file] Invalid filename for dowloaded file. Path must be relative to netprobe working directory

Problem Copied

• Having a problem in copying a file using toolkit sampler.

  Error message looks like below:

  ERROR: TOOLKIT [be_file] Invalid filename for dowloaded file: /tmp/fileoutput.sh. Path must be relative to netprobe working directory.
  

• Toolkit script has been defined like below

![Geneos - How to resolve ERROR: TOOLKIT [be_file] Invalid filename for dowloaded file. Path must be relative to netprobe working directory.](/faq/images/geneos/15785251281309-24753162741533-mceclip0.png)

![Geneos - How to resolve ERROR: TOOLKIT [be_file] Invalid filename for dowloaded file. Path must be relative to netprobe working directory.](/faq/images/geneos/15785251281309-24753187128861-mceclip1.png)

Possible Cause(s) Copied

• Root Cause: This error means that the filename parameter you defined is not correct as per the sampler definitions.

Possible Solution(s) Copied

• Solution Root Cause: If you want the netprobe to create the script, you will need to define the path to the script under the netprobe working directory. You can check this in the docs:

• script > filename Copied

  Name of the script that the Netprobe will write to. This must be in or under the Netprobe’s working directory. Absolute paths are not permitted in that paths must start with (./) or state the filename itself, denoting the Netprobe’s relative path. The subdirectories and filename in the path will then be created if they do not exist.

  For example, it can be any of the following:

  • ./<netprobe_directory>/<filename>
  • <netprobe_directory>/<filename>
  • ./filename
  • filename

• https://docs.itrsgroup.com/docs/geneos/current/collection/toolkit-plugin/index.html#script__filename

Related Articles Copied

• https://docs.itrsgroup.com/docs/geneos/current/collection/toolkit-plugin/index.html#script__filename