IOException when trying to Rename

[JesseMiller]

The title kind of explains the problem. When trying to rename/move files I get an error. I've tried moving the folders to a different location and can't really figure it out. After quite a bit of Googling I couldn't find anything about this issue so I'm hoping for a bit of help.

System Information:
Windows 7 64Bit
Java: Version 8 Update 31
FileBot Version: 4.5.6
I installed it by the Windows Installer.

Code: Select all

C:\Users\Anonymous>filebot -script fn:sysinfo
FileBot 4.5.6 (r2818)
JNA Native: 4.0.0
MediaInfo: MediaInfoLib - v0.7.69
7-Zip-JBinding: OK
chromaprint-tools: fpcalc version 1.1.0 (C:\Program Files\FileBot\fpcalc.exe)
Extended Attributes: OK
Groovy Engine: 2.3.9
JRE: Java(TM) SE Runtime Environment 1.8.0_40
JVM: 64-bit Java HotSpot(TM) 64-Bit Server VM
CPU/MEM: 4 Core / 1 GB Max Memory / 20 MB Used Memory
OS: Windows 7 (amd64)
Done ?(?????)?

I couldn't figure out how to copy the console log so here is a screen shot;


Edit: After posting this I was playing around with it some more and found it to only be certain files. Not sure what the problem is.

[rednoah]

So I assume Drive O is a network share? And the log say that it "can't create folders" which means you need to fix the permissions on your network share.

[JesseMiller]

Nope, it's in the same computer. And as I said, it is only some of the files, not all of them. I was also able to move a bunch of TV shows shortly before that.

[rednoah]

Somehow Windows does not allow filebot to create those folders. Unfortunately there's nothing filebot can do about Windows permission issues. I'm sure you'll find some answers on Google.

[JesseMiller]

I'm honestly not sure what the deal is, it started working after I moved some test files to a different folder, but now it won't work at all.


Edit: I am completely baffled, I reinstalled it and it didn't work, tried different files, and it didn't work. But then I decided to try with the CLI and cleared the cache/reset the settings. It works now. I'm honestly not sure what the problem was.