* What exactly are you doing?
* Is the GUI not working?
* Is the CLI not working?
* Is FileBot not starting?
* Is FileBot starting normally but then shows this error message when you do perform some specific operation?
* Is not not renaming certain files located on a remote file system?

Please provide a lot more detail.

By default, logs are stored in
%USERPROFILE%\AppData\Local\Packages\PointPlanck.FileBot_*\LocalCache\Roaming\FileBot. Please read the FAQ for details. This applies go GUI logs, not CLI logs, where the location is up to you.

The amc script (assuming you're using the amc script) stores logs wherever you chose via the
--log-file option, e.g.
--log-file C:/Logs/amc.log and relative to
--output if you specify a relative log file. Make sure that the log file is writable.

If you are using the amc script, please post the command and console output:
viewtopic.php?f=3&t=1868

If you are using the amc script in an automated setup, what does the console say if you call it yourself?

The keywords in
Illegal Argument: java.nio.file.NoSuchFileExecption are
Illegal Argument and
NoSuchFile and
not java.
NoSuchFile indicates certain files don't exist (or appear as if they don't exist due to permissions).
Illegal Argument at the beginning of the amc script indicates that you're passing bad file paths as arguments, i.e. telling filebot to process files that don't exist.