
To use these steps, log into Terminal as admin on your Mac server, and follow these steps (copy and past the commands in italics into Terminal): The process I used to get the right sequence was simple: I kept careful notes of each step I took and it’s outcome, and a pattern started to develop.Īnd that pattern led me to this sequence of actions that finally solved the problem, without having to reinstall FileMaker Server and without having to restart the server. I needed both running for everything to work. And once that happened, getting FileMakers’ instance running again was not easy. I did find a way to manually install SuperContainer at 360Works support page, but SuperContainer still did not work.Īfter working the problem for a while, the issue seem to be that the Mac Apache instance was overriding FileMaker’s Apache instance. But no luck…the program would not run.Īnd since this was after hours and I needed the server working before the next day, reaching out to 360Works was not an option. That was not a problem: I had changed the security setting already. The most common advice I found: Make sure Apple Security is set to allow unpublished programs to run. My goal: Get SuperContainer and FileMaker Web Services working again.īut SuperContainer posed it’s own challenge: the Mac Installer would not run on the computer. Restart the server after everything you do (OK, not quite that often, but is seemed that way)Īnd untold numbers of combinations of the above.

There is a lot of well meaning advice out there, some good, some bad, some time wasting:

Perhaps it will save you substantial time in the future. I went through quite a bit of troubleshooting and research trying to fix the problem, learned quite a bit, and decided to share my findings. Instead, things went from bad to worse: FileMaker 14 Server web services stopped working entirely, affecting multiple clients on the server. I Immediately tried re-installing the latest version of SuperContainer, but that did not fix the problem.
/article-new/2015/05/FileMaker-14-Mac-iPad-iPhone.jpg)
Recently, SuperContainer, for reasons unknown, stopped working on my cloud server. Need help troubleshooting FileMaker 14 Server Web Services?
