Hi @dirk,
Thanks for the additional information!
Can you send a diagnostic from the odrive tray menu?
Additionally, can you provide the name of the file and path that you are currently seeing this error with This may reveal some additional information.
What is strange is that odrive doesn’t get in the middle of anything once a file is downloaded locally. At that point it is like any other files on your desktop, so there shouldn’t be anything that is interfering with accessing the tmp file that is being created. The only thing I can think of is that this could possibly happen if odrive has the file open for uploading, but odrive ignores .tmp files by default, so shouldn’t even be looking at that file, much less trying to upload it.
Can you try an experiment and exit odrive so that it is no longer running (please send the diagnostic before doing this) and then see if you still encounter the same error?
EDIT
Something else that occurred to me is that there could be a path length issue. It may be that the full path to the tmp file is longer than the VB script can handle. Once the diagnostic is sent I should be able to see if this is a possibility.