

The Web Server and SuperContainer were still down – my web page showed nothing at the link, no webpage, just a broken link. I ran this command in Terminal to restart the Web Server (ignore admin$ – that is the terminal window prompt on my system):įmsadmin: really restart HTTPserver? (y, n) y
#Filemaker server 14 mac
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.
#Filemaker server 14 install
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.
