Installing & Configuring FileMaker Server (FMS 17)

Uninstalling FMS 16

If you are installing FileMaker 17 on the same machine that hosted your FileMaker 16 databases, complete these steps. Otherwise, proceed to installing FMS 17.

  • Backup and archive your existing FileMaker databases:
    1. Log into the Admin Console.
    2. In the top-right of the Status screen, click the blue On/Off Switch to stop the server.
    3. Wait until the grayed-out On/Off Switch regains its color and appears in the 'off' (left) position. Do not start the server again; the server must be fully stopped so you can proceed.
    4. Navigate to the server's Data folder:
      • Mac — Macintosh HD/Library/FileMaker Server/Data/
      • PC — C:/Program Files/FileMaker/FileMaker Server/Data/
    5. Archive the entire Databases folder.
  • In the FMS 16 Admin Console, navigate to the Schedules, then review and document any custom server schedules in enough detail that you can recreate them precisely in FMS 17 (i.e. including every specification from "Schedule Type" to "Schedule Enabled”). "Custom" server schedules include any that are configured and enabled beside:
    • Automation Cycles A-D
    • Automation HALT
    • Daily
  • Uninstall FMS 16 using the FileMaker Server 16 uninstaller (Mac) or the Program Uninstaller (PC). (For details, see FileMaker’s guide on Uninstalling FMS 16.)
  • Quit FileMaker Pro.

Installing FMS 17

Once you have a 'clean' server, you are ready to begin the actual installation. (For additional details, review the FileMaker support documentation.)

Before starting the installation process, place your “LicenseCert.fmcert” file into the server’s default Downloads folder. This file will be used to enter your installation credentials.

  1. Start the installation, then at the Deployment Options screen select FileMaker Server master.
  2. On the User Account screen, specify the correct account:
    • Mac — Select the radial button for fmserver.
    • PC — Select the radial button for Local System.
      Note: If your implementation requires a different account, please note why and send that information to aACE Software.
  3. On the Customer Information screen, enter the exact Organization Name from your FMS 17 license key.
  4. On the Admin Console Account screen, enter the Admin Console credentials as follows (unless you have made different arrangements with aACE Software or your FileMaker developer). 
    1. User Name: "Administrator"
    2. Password: Use this password generation site to create a password using these settings:
      • Memorable Password
      • Length: 3
      • Capitalize: Checkbox cleared
      • Full Words: Checkbox cleared
    3. PIN: Any 4-digit number
      Note: We recommend basing the PIN on the installation date (e.g. April 2019 as “0419”).
    4. To facilitate support, document these credentials and send them to aACE Software or your FileMaker developer before proceeding.

Additional Tasks for PC

  • Port Errors — In some cases, you may receive an error indicating that ports 50003 and 50004 are in use. If you receive this error, please deactivate IPv6 and try again.
  • Bonjour — If you are prompted to install the device location service Bonjour, click Yes. 

FileMaker Server Folder

Note the location of the FileMaker Server folder created during the installation. It will be referenced multiple times throughout the remainder of this process.

  • Mac — Macintosh HD/Library/FileMaker Server/
  • PC — C:/Program Files/FileMaker/FileMaker Server/

Configuring FMS 17

After the installation, you will be prompted to launch the FMS 17 Admin Console. (Note: If the Admin Console does not open, you can launch it manually by navigating to: http://localhost:16001/)

  1. At the Admin Console login page, create a browser bookmark in the Favorites list with the name “FMS Admin Console”.
  2. Log into the Admin Console using the credentials you set up during the installation (see above).
  3. The console prompts you to install an SSL certificate.
    • If you are upgrading from FMS 16 and have a previously installed SSL certificate, you can re-install those certificate files at this point.
    • If you don't have SSL certificate files on hand, select Don’t Use SSL. (You will set up SSL in a later step.)
  4. In the Admin Console, configure these settings: 
    • Navigate to Configuration > General Settings and change the Server Name. We recommend using "aACE Server" or the fully-qualified domain name to the server computer.
    • Navigate to Connectors > Web Publishing and enable Master Machine.
      • To complete this connection, open the command line interface and enter this command:
        fmsadmin set cwpconfig enablexml=true
      • When prompted, enter the Admin Console credentials.
    • Navigate to Connectors > FileMaker Data API and enable FileMaker Data API.
    • Navigate to Connectors > Plug-Ins > Server Plug-ins section:
      • Enable FileMaker Script Engine Plug-ins
      • Enable Install Plug-in File Script Step
    • Remove the default Sample database from the Admin Console:
      1. Navigate to Databases.
      2. At the database named FMServer_Sample, click the drop-down arrow next the file name and select Close
      3. When the indicator turns gray, click the drop-down arrow again and select Remove, then click OK.
    • Remove the Sample database folder from the server:
      1. At the Admin Console, navigate to Configuration > General Settings > Server Information section and click the link to Stop Database Server.
      2. In Finder/Explorer, navigate to FileMaker Server/Data/Databases.
      3. Manually delete the Sample folder.
      4. At the Admin Console, click Start Database Server.

Java Updates

FileMaker Server installs a paired version of Java. This should not be updated to any other version. To prevent automatic updates:

  • Mac — Navigate to System Preferences > Java > Update and clear the flag for Check for Updates Automatically. At the prompt to check now, click Do not check. Click Apply. If prompted, enter the server Admin credentials to finish the change.
  • PC — Navigate to Control Panel > Java > Update and clear the flag for Check for Updates Automatically. At the prompt to check now, click Do not check. (Note: If the Control Panel does not display a link for Java, type “Java” into the Control Panel search bar.)