I am not enamored of FileMaker's choice to usurp full control of Apache but I am trying to move forward rather than rant. So we contacted FileMaker and following their recommendation that the WPE NOT be run on a 10.9 server, we installed it on a standard install of the 10.9 OS which is bound to our 10.9 Open Directory. I did that twice before I realized that the issue would not go away. There appears to be no way to reinstate the FileMaker precedence without reinstalling. On restart of the machine though, the Mac OS Server takes it back and, even though the websites section of the Mac 10.9 Server software is not on, presents the message that the websites are not on and to contact the admin for the server to enable them. On install FileMaker Server takes full control of Apache and runs FMS as expected. ![]() First discovery was of the issue that putting a FileMaker server on a 10.9 Server does not work after the first restart. ![]() We recently moved to FileMaker Server 13 on and discovered the following issues during production use on Mac 10.9.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |