I have seen this in Windows when copying a file from a CD. Go to the file in Windows and select Properties and insure the Read Only box is not checked.
Looks like the permissions for some files on your FileMaker server are incorrect.
On your FileMaker Server, you need to:
Pre: Make full bootable clone (SuperDuper), back-up files
1. close the databases on the FileMaker Server
2. close the FileMaker Server admin console
3. drag and copy the folder 'Data' from your folder 'FileMaker Server' (Volume/Library/FileMaker Server) to the desktop
4. copy the 'Data' folder back into the folder 'FileMaker Server'
5. set permissions to 'Data' (and enclosed items) to owner 'fmserver' and group 'fmsadmin'
6. to do step 5, use BatchMod (download from BatChmod)
If anybody knows a better way, please let us know.
HOw did You install the files in the Server (we're takling about FMS, right?)? With the new interface (introduced with FMS9), I strongly recommend to use the 'upload' function of FMServer (until FMS12) or from a client (FM13). Otherwise, the permissions won't be set correct in every case. Earlier, this was a windows-only issue (FM3..), today it's more a OSX issue.
YOu can set the permissione manually as well - but the easiest way is to use the upload function
are all files set to read/write for everyone? Looks good, so far.
IF You are running FM13, choose share from the FM client (and write a feature request for adding the old functionality back to have an upload feature _in_ the server admin). The browser should have pop-ups enabeled (worth another feature request..). There might be java issues as well )-:
YOu can also install a FM client on the server machine
Close the DBs in FM Server Admin
Open a terminal window and execute the following:
- cd /Library/FileMaker\ Server/Data/Databases/
- sudo chmod 666 *.fmp12
- sudo chown fmserver:fmsadmin *.fmp12
sudo will prompt for a password, just enter the login password for your username.
Using the finder 'get information' on the file and confirm that the fmserver and fmsadmin user/group have read/write access to the file
Open the DBs again and as long as the file has the permissions detailed above everything should be back to normal.