Skip to main content
A
Anonymous
December 6, 2006
Question

Using CIFS/NFS Mounted Drives for "streams" directory

  • December 6, 2006
  • 4 replies
  • 769 views
We have multiple FMS Origin server(s) . We plan to use a NAS device, where content is directly uploaded to it. This content will be shared across the FMS Origin server(s). I've been trying to get the FMS to see the content from the NAS device. I tried using the the <VirtualDirectory><Streams>... settings on the VHOST.XML It works fine for any drive/directory on the FMS servers. On a Windows FMS, I mounted a drive from the NAS device. I set the VHOST.XML to recognize some path on the URL to look for streams on these drive. And unfortunately it appears as if the FMS cannot find the streams. For testing I cloned the same directory structure and used the VirtualDirectory><Streams>.... options to define three locations :

t1; .. Local Server Directory under applications other than standard streams location.
t2; .. Local Server different hard drive than where FMS server is installed.
t3; .. Mounted Drive from location on NAS Device, accessible as Local drive on the FMS installed server.

I suspect some permissions issue? It works perfectly fine for t1 and t2 above.

Any suggestions will be greatly appreciated..
    This topic has been closed for replies.

    4 replies

    S
    sunwer
    Participating Frequently
    September 16, 2008
    It’s very useful, Thanks!
    A
    Anthony_Leonard
    Participating Frequently
    May 31, 2007
    Thanks a lot for posting the above. I am also getting "Failed to create process mutex." in the Windows 2003 server application log. I'm trying to do exactly the same thing - change FMS to run as a domain user which has access to CIFS mounted filestore. This domain user has local admin rights, but I haven't yet added any domain rights for this user.

    I know you're not sure which domain permissions worked but could you share more on what domain permissions you gave your user? Can anyone else? .. Thanks again.
    stoem
    stoem
    Known Participant
    December 8, 2006
    What's your synrax for specifying the drive? I don;t think it will work by share name or drive letter, instead use IP:
    <Streams>\\123.123.12.12\myfolder</Streams>

    Does that work?
    A
    Anonymous
    December 13, 2006
    Thanks for your replies. A combination of both answers worked.
    - I created a new User in the domain fms_user
    Modified the FMS service to run as the user, and after playing with the security assigned to the user it was finally able to run.

    - It's only able to access the NAS using a CIFS URL in the VHOST file. But not if I mount and use the drive letter.
    But I prefer the CIFS URL anyway.

    I ran into problem's when trying to make FMS run as a different user other than LocalService. It kept on complaining that it "Failed to create process mutex.". I had to add User permissions in the Local and Domain security for it to work. It was touch and go for a while, so I'm not sure what permissions ended up doing the trick.

    Is this documented somewhere. "How to run FMS Service as a custom user" . I would like to only allow the required permissions and nothing more. I couldn't find it in the documentation or the web.

    Thanks for your help again.
    A
    Anonymous
    December 8, 2006
    Check out which account is used to run the FMS server. that account has to have permissions to access and write the directory (of the NAS) you specifiied.

    It doesn't matter if you (as a user) can write on the NAS . Prolly user "local system" should have write permissions etc etc. This is a bit insecure so I'd suggest you'd change the user the FMS is running as. Create a new user. Limit it's access to the system, directories etc etc. When FMS starts up it will try to access the NAS as that configured user. That should be easy to test and debug.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices