Hi there! First, I'd like to say thank you for creating this fantastic tool
I'm hoping you can help me solve an issue I'm having with network output. I've attached the workflow I'm using for transcode, which works fine if I change the output folder to a local path on my machine, but fails with error "Destination unavailable or no more space left for delivery!" if I change the path to our SAN. I've made sure permissions and quota are good, and I can access the directory through Windows file explorer, so not sure what I'm doing wrong. Any ideas?
*Please note I've changed the actual path in the workflow to omit my company's server/path names.
As long as you're running the application with your own credential and are able to write to the exact same destination folder from windows, I really don't know what could be wrong. FFAStrans is using the windows api to write files so there really should not be any difference. I will check with the rest of the team and come back to you.
admin wrote: ↑Fri Feb 07, 2020 8:56 pm
Just want to ask you; did this use to work before but not any more?
-steinar
No, I'm new to FFAStrans. I've never got this workflow to work and assumed there was something I was doing wrong. It appears I'm the only one with this issue, so it must be something with my environment. I'll do some more investigating and report back if I find a fix.
The problem seems to be about getting the "free space" information for your SAN and NAS share, which is incredibly impossible. We don't seem to have a permission issue here but maybe some bug in ffastrans; this is our current believe. As you say it is more or less somehow dependent on your personal environment.
However, can you tell us what windows explorer shows about the free space on your san and NAS- how many space is free in opinion of windows explorer?
Please dont skip any of those. You complain about NAS and SAN, which should be 2 totally different problems but they end up with the same issue for you, so what do they have in common?
Could you please replace the attached file with your current processors.a3x file? Just rename your old to something else and the new from .xml to .a3x. Hopefully it should work now but if it does not, we (hopefully) will get a better more precise error message.
