Never mind - the client had screwed up the permissions on the USERS directory. Fixed them and all is working properly....

Trying to set up SC on a client server - did a manual install of SC since it is Snow Leopard Server, server & clients are FM 10. Manually changed permissions using terminal to the correct permissions for the default folder Users/Shared/SuperContainer/Files & I am using the script from the sample file to upload a folder of files, and I get an error 500 every time on the first file to attempt upload.

I also get this error if I attempt to upload files using the web interface on server. But the permissions are set correctly.

Here are my error logs from the testing client. Please help!

Archive.zip

Edited June 8, 201015 yr by Guest

Error 500 means that permissions are not set correctly for the SuperContainer directory. If you have installed SuperContainer with FileMaker server you will need to give read/write access to the Users/Shared/SuperContainer directory to the fmsadmin and fmserver user and groups. You can also give "Everyone" read write permissions if you have trouble adding those users.

David, I see a very similar problem with error 500:

OSXServer 10.6.3 SC 2.748, FMS 10

Even with the permission to read/write Everyone on the folder /Shared/SuperContainer/ and all it's child folders, I get this error. Same result when I do it directly on the server via the SC page /on/my/filepath/

When I do a manual install and run as local host, it works correctly and I have access to the correct folder, so I assume it is a permission issue, but at a different level then the folder level.

It did work on an older version, not sure now what the previous installed version was, ca. 2.742

Let me know if you need more details on the way this server is configured.

If you are able to write to that directory when running in stand-alone mode but not from a server deployment then it is definitely a permissions issue. If you can't get the permissions to assign properly then I would recommend deleting the Users/Shared/SuperContainer/ directory and allowing SuperContainer deployed on FileMaker server to create the directory fresh, so that it has the correct permissions.

Thanks David, this did the trick.