FileBot

Hi,

I've been using Filebot for a few days now. Unfortunately I'm confronted quit often with the following error message while Filebot is transfering files to my NAS:

An unexpected error is keeping you from moving this file. If you continue to receive this error, you can use the error code to search for help with this problem.

Error 0x8007003B: An unexpected network error occurred.

Screenshot: http://imgur.com/a/vb6AT

At first I thought it was just another Windows thing. But after thoroughly testing it seems to appear only when using Filebot. Even more specifically: it only happend when files are being transferred by Filebot to a network drive while at the same time using Windows File Explorer (just starting File Explorer seems enough). Important to note: if I just leave Filebot running while having no File Explorer windows running everything seems to run smoothly.

Specs:
- Filebot Windows App (specifically chosen to support the dev).
- I only use GUI for now.
- Windows 10 pro all updates installed.
- Sysinfo: http://pastebin.com/raw/MEfGL69z

Any support is appreciated. If I can provide any more info, please let me know.

Have you tried to google "Error 0x8007003B" and whatever solution that might come up?


EDIT: Google results show that this is a common issue with a variety of tools and services: https://networkdefend.blogspot.tw/2016/ ... -when.html


You can try the FileBot (console) launcher instead and see if that works.

FileBot uses Windows to move/copy files. FileBot (console) uses Java to move/copy files. The latter might allow you to work around odd Windows issues like this.

Hi Rednoah, thanks for your reply.

Actually I have. I tried some stuff as well, but as the issue was only occurring with Filebot I eventually stopped my research.
I have now installed the non-app version of Filebot and it doesn't seem to have the issue. I did have to install the 64-bit version of Java besides the 32-bit (that is apparently standard) though.
Another issue with the app-version: Dragging files from a named network location (i.e. \\NAS\share\file.avi) didn't seem to work. But when using a direct IP address (i.e. \\192.168.0.123\share\file.avi) it worked fine.

Is there a difference between the Windows app and the standalone app?

There is no difference in how FileBot works. But the underlying Windows Bridge technologies that allow you to run Win32 applications as UWP applications might still be a bit rough on the edges.

That being said, what you think of proof is really just one single sample and most likely random noise, statistically speaking. Network share permissions on Windows have always been weird. For some users only mapped drive letters work. For others only UNC paths work. It's very finicky.

Same with SMB issues. That's an issue with the SMB software on your but for some unknown reason only the UWP version somehow runs in into that bug. Some OS or NAS software update will probably fix this at some point.