I can see that it is a Mac server.
The most obvious answer is that it is the privileges, the rights to the folder, that is causing you problems.
You need to make sure that the FM Server user has full read and write rights to the folder and all enclosed folders.
Which FileMaker version/revision are you using and which Mac OS X are you using?
Please see the enclosed file: This is how the fmserver user's permissions should be set up.
Thank you very much, its taken me ages to work this out. It would be helpful if they added this tip to their documentation
Thank you for the post.
“It would be helpful if they added this tip to their documentation”
We are always working to improve our documentation. The knowledge base article Specifying a valid backup or database folder path. currently states:
“(Mac OS) The folder must be owned by the user fmserver (or in the group fmsadmin).”
So that others are not confused in the future, what would you like to see added so we can make this more clear?
I remember reading that part but I didn't interpret it as having to do with the privilege/security of the folder.
Carsten explained it very well: "You need to make sure that the FM Server user has full read and write rights to the folder and all enclosed folders."
It is an interesting balance. The server is a product for specialists, while FileMaker Pro and Advanced is for all from the occasional user who have found that FileMaker is much stronger and safer to use than Excel and up to highly specialized professional developers building ERP systems.
And for some functions you even need the terminal and arcane commands when setting up or manipulating FileMaker server.
Therefore the question is how far FileMaker need to go when it come to user-friendlyness, i am not sure.
Since the paths to databases, backup, external files have to be hand typed and not choose by a dialog and since the permissions need to be set there are more than one possible cause for the path not being valid. Therefore the best solution would probably be one of two: The dialog that it is not valid could state what the problem is. Or the path could be set with a dialog and then when there are privilige problems this could come up in warning, maybe even preventing the selection until it is solved. Or even offering to "fix" it.
But am not sure about this. The documentation is fine and we are having more than 50 servers behind us at our own and at customers sites. Maybe it is OK with the documentation and the help here?
johndoe & CarstenLevin:
Thank you both for the feedback.
I submitted your comments to our Documentation department and we updated the article to read:
“(Mac OS) The specified folder and all parent folders must be owned by the user fmserver (or in the group fmsadmin). To set folder permissions on Mac OS X, control-click the folder and select "Get Info”.”