The installer for FileMaker Server 16 refuses to install on a Mac if Apache is running. It doesn’t check what ports Apache has grabbed, just the fact that Apache is running is enough for the installer to bail out.
If you have Server.app running on your Mac, even if all web services are turned off or disabled, you will still have Apache running.
This situation is laughable. Apple’s subsidiary, FileMaker Pro, is making software that with a few tweaks could co-exist perfectly with macOS Server.app and it’s Apache reverse proxy, but they don’t.
A quick hack to at least get you through the installer is to run the following command in the Terminal before running the installer, and then killing it when your’e done.
while sleep 5; do sudo killall -9 httpd; done
Just make sure you don’t then enable FileMaker Server’s web services, or if you do that you don’t use a port that Server.app uses (namely 80 and 443 and a few others) and you should be good to go.
https://community.filemaker.com/thread/156699
Very usefull 🙂 Thanks.
Keep in mind to run: “sudo killall -9 httpd” first. Than get promted for a password. After that run the loop.
I’ve also written another post just today that shows how to stop all Apache services in the latest versions of Server.app – I haven’t tested it, but I’d imagine this would get Apache out of the way for FileMaker to install.
http://automatica.com.au/2018/02/stop-apache-web-services-macos-server-app/
Thanks for this note – your loop helped me kill this so I could reinstall FMP 16 on our office server.