Page 1 of 1
Big problem with FFastrans and Farm
Posted: Wed Feb 13, 2019 4:51 pm
by momocampo
Hello,
Well, I changed recently my FFastrans configuration (local) to a farm with 3 workstations.
I Install FFastrans on a NAS and share the media cache(on NAS too). I installed FFastrans as service(administrator log on).
It worked fine but I had some problem of delivery and I really don't now why !
The error speaks about an account, which one? The administrator ?
Anyway, I had to reinstall my local FFastrans to delivery all my files correctly but I'm sad that my farm is unstable...
So, if someone can help me.
Thanks a lot.
Cheers
Benjamin
Re: Big problem with FFastrans and Farm
Posted: Wed Feb 13, 2019 5:37 pm
by emcodem
Hey Benjamin,
are you working with domain accounts or local accounts? ..to access the storage...
We will need steinars help about this account error message but i want to make sure when he reads it, all the infos to give a good answer are already there.
Re: Big problem with FFastrans and Farm
Posted: Wed Feb 13, 2019 7:00 pm
by momocampo
Hi emcodem,
Ok, all the workstations are on the same domain. Before I install each workstation, I create names in domain active directory. Then, I rename each machine with these names before enter on domain.
I switch in administrator domain session account (on each workstation)to give privileges(admin) to new sessions. I mount every Avid Isis Workspaces on this administrator session and check I can access to all paths (NAS and Isis). I used UNC path not letter.
At last, I switch again on new session machine name to run FFastrans and configure it : share media cache, install service with run as app check. I configure the rest service not on local but with administrator account(
administrator@domain.com). I restart the service and that's all.
Really don't understand why it works sometimes and sometimes not...Maybe I have to configure the rest service with log on local (admin rights) and use local cache. I only use administrator log with webinterface.
B.
Re: Big problem with FFastrans and Farm
Posted: Wed Feb 13, 2019 8:38 pm
by emcodem
Oh, i thought "specified user does not exist" is something relative to how ffastrans works in a farm but it looks like it is avid specific. Unfortunately i don't have experience with avid, i guess they use something like their own driver (minifilter) in order to simulate unc access.
The problem is, as far as i understand, pretty avid specific and not windows specific... i can ask some experienced folks about it but it will take 2 weeks until i see them again
As it is probably avid specific, maybe an avid related search in the internet helps... something like that?
http://avid.force.com/pkb/articles/en_U ... e/en276585
Re: Big problem with FFastrans and Farm
Posted: Thu Feb 14, 2019 11:57 am
by momocampo
Hello,
Thanks emcodem but I don't think Avid storage is bad, I have several others workflows ok with delivery on avid storage.
Anyway, I change my configuration : I change the media cache on each workstation from share to local. I change the credentials of ffastrans rest service from administrator to local but with local address (Workstation name is ws1 so log on = ws1@domain and password).
From now it works, I don't have error yet, I must check often.
Cheers.
Re: Big problem with FFastrans and Farm
Posted: Thu Feb 14, 2019 5:10 pm
by admin
Hi Benjamin,
The 1317 "The specified user does not exist" error code/message comes from Microsoft and is not particular to FFAStrans. So I'm not sure how much I can help with this but I just want you to confirm that you are able to use the same user and access the Isis shares without using FFAStrans, like just browsing the shares, reading and writing?
-steinar
Re: Big problem with FFastrans and Farm
Posted: Thu Feb 14, 2019 9:07 pm
by momocampo
Hi Steinar,
Thanks for your answer, maybe error because I'm not in the same session...Don't know.
The thing I can tell you about Avid it's the Isis workspaces were well mounted and in writing mode. Weird.
I test my new configuration from my last post and it works for now. Just be careful to use only UNC path and not letter.
My 3 workstations work alternatively and all is success. The only errors are delivery path issue with letters (c.\ or d:\ etc.) I have so much delivery node I forgot always 1 or 2
So, I must keep watching the log to check no errors appear.
Cheers.
Benjamin