I don't know why you would want to upload a fuel this way instead of the recommended way, but nevertheless I just tried it for myself and it worked OK—Stopped FMS; dragged and dropped Test file into the FMS directory; restarted FMS, Test file opened; stopped FMS; removed Test file; restarted FMS, back to normal.
I suggest you try it again, stopping FMS first, and see if it still fails.
Hi, from your screen shots you're on Windows.
Unlike the Mac there are no file permission issues. Normally if you have the admin console open and drag files into the hosted folder the files will dynamically appear (or disappear if closed files are removed).
There is no reason to stop/start FMS. Just open the files once they appear (or should appear).
We have to use this method all the time to upgrade separated systems due to the way FM handles external container files.
Sorry, no answer, but it should work. By the way, we usually download Chrome for this.
I had a misunderstanding of how I was going to deploy a front end interface / back end date solution. I didn't need to go back and try what you suggested but thank you for testing this out.
Thanks for the information.
Did you manually reconfigure the file's Sharing settings for it to work via Server, or did it simply get "moved" as a client-run file?
Stephen I ended up using the tools built in FM to upload the front and backends. I was doing something wrong referencing files between the two.