1 of 1 people found this helpful
It looks like the permissions on the system are completely out of whack. Stop the FMS service after closing the files by using the "sudo launchctl stop com.filemaker.fms" command and then run a full system permissions repair.
thank you a lot for your answer. Do you mean the repair permission command of the system? to my knowledge this command only changes components installed by apple.
Since it runs on a company server, which runs flawlessly, not considering these problems, I would rather not apply such "systemwide commands.
To make at least the script engine run again, do you know what privileges I have to give to the fmsuser, which got created when I installed fms on the machine?
thanks for your help,
I did the permission repair, but to no avail.
I deleted the script schedule in question and tried to recreate it and it give me a "no scripts available for the specific account".
Even with a full access login, even on files that have a guest account open.
The error 757, which asked to restart the script engine was resolved like this:
I gave first the terminal command
fmsadmin stop fmse
which asked for y,n, and ran after "y"
THEN.... I gave
fmsadmin start fmse
and this time the command ran without problems. (So it seems to me, that the error 10006 was actually only because the script engine was still running, not permiting to start). Stopping AND starting did the trick.
The Error 685 was also resolved. I saw that only one of my backup schedules had this problem. So I deleted the one in question, deleted all folders relating to it and recreated it and now it runs without problems.
I must say, that inbetween I did a "repair permission" as Wim suggested... I might also have helped.
I just saw that the error 685 persists. It takes a day until the server starts to delete files.
Seeing from other posts I try to resetup my container fields because some people report this to be a solution.