Jump to content
View in the app

A better way to browse. Learn more.

FMForums.com

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Filemaker 14 Pro Server 14.0.4a on El Capitan Server 10.11.2

Featured Replies

  • Newbies

I installed from downloaded image v14.0.4 and then patched to 14.0.4a.

When I go to http://localhost:16001 - nothing happens. It just sits on the screen saying that "Admin Console is starting...".  I've not been able to deploy or setup anything yet.

During install, it is setup to use alternate ports, namely 8080 and 8081 (http, ssl) respectively.

5672cd980af23_ScreenShot2015-12-17at11.5

When I go to the Console logs, I see this error repeated: XPC_ERROR_CONNECTION_INTERRUPTED trying to map database

5672cd9985336_ScreenShot2015-12-17at11.5

No clue how to proceed, anyone else got a suggestion?

THANKS ahead!

Edited by 2b3pro

FileMaker Server is not compatible with El Capitan Server.   That could be causing the problem   There are a lot of issues with trying to run OS X Server and FileMaker Server on the same box.   

Most of the problems involve Apache but there are workarounds. Search the forum for info about this.

  • 1 month later...

I have the Apple Server software installed on the same machine as FM Server, but have not upgraded from 10.10 to 10.11. If I upgrade, would I just need to turn off all services in the Apple Server or would I need to completely remove the software?

I'm currently running FMServer 13 and would like to upgrade to 14.

tThanks

For your switch from FMS 13 to FMS 14 you should definitely you use the uninstaller for FMS 13, then do an install for FMS 14. As part of this procedure the correct Java version for will be installed (could be part of the problem). However, I would recommend to follow FileMaker's own recommendation and posts above: do a clean install of OS X first with NO SERVER. Current OS X Servers are no longer compatible with current FMS.

FMS14 and OS X 11 Server are not officially supported, but many folks are using them together, as noted here by a FileMaker Inc. rep. see https://community.filemaker.com/thread/84470?start=0&tstart=0

 

I have no experience with El Capitan, but am having good results with FMS 14 and OS X 10.10 with OS X Server installed.  

 

 

  • 3 weeks later...

Not sure why several posters here state the contrary, but FMS14 and OSX 11 is indeed an officially supported combination. If memory serves me right it has been that way for some time.

http://www.filemaker.com/products/filemaker-server/server-14-specifications.html

Also I assume the problem had already been solved by 2b3pro and I can't be sure, but those ports, especially 8080 could've been in use by the Server.app's internal proxy process. FMS setup usually warns about those but it's possible that they were closed during the setup process and got opened again after a reboot.

@Buckie  OS X 11 is supported but OS X 11 Server is not.   Using Alternate ports it is possible to get FM Server and OS X Server to run on the same machine, but it's a more complicated setup and can be more challenging when using web services because of the way OS X Server always runs a web server.

You mean Server v4 and Server v5 probably? I'm not sure if Server v4 was allowed to run on 10.11, I'm sure you could run Server v5 on 10.10 though... which makes the statement "OS X 11 Server" even less meaningful. Anyhow, where are the links/statements from FileMaker that prove said incompatibility? They always seemed to mention only the OS version number and I can't remember ever seeing them mentioning Server.app version requirements for FM server (before that they said you shouldn't have Server.app and FMS running on the same machine regardless of the version and later it was just compatible).

Create an account or sign in to comment

Important Information

By using this site, you agree to our Terms of Use.

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.