Restarting the aACE Server

It is of critical importance that all aACE files be safely closed via the FileMaker Server Admin Console prior to shutting down or restarting the aACE server. Please follow the steps below very carefully anytime you need to restart your aACE server for any reason. Shutting down the server while any aACE files are still open can result in corrupt files and permanent loss of data.

We recommend that you schedule periodic restarts of your aACE server to take place at least once every 30 days. FileMaker Server sometimes encounters issues with system performance or with the Admin Console interface if the server has not been restarted for a long time. Periodic restarts help prevent such issues. You can schedule automatic restarts to help with this.

You may also need to shut down and restart your aACE server in order to install OS / software updates or if aACE Software support personnel cannot access your server remotely. When scheduling a restart of your aACE server, select a convenient time (e.g. when user disruption will be minimal), then use these instructions to ensure your aACE server is restarted safely.

Shutting Down the Server

  1. Log in to your server's FileMaker Server Admin Console (manual launch: http://localhost:16001/)
  2. Navigate to the Databases tab.
  3. At the top of the list of Databases, click on the Database Options chevron and select Close All.
  4. At the prompt, enter a message to be sent to any users currently signed into your hosted system.
  5. Wait for the Status indicators for all hosted files to change from blue () to red () to gray ().
  6. Navigate to Configuration > General Settings, then at the Server Information section, click the blue Stop Database Server link.
    Note: FileMaker will again prompt you to broadcast a message to users. However, since you have shut down the system already, this second message would not be seen by any users.
  7. Click Stop Database Server.
  8. Wait for the Admin Console page to display the refreshed Database Server Status screen.

Restarting the Server and Verifying

At this point, it is safe to restart the machine and FileMaker Server will automatically restart. 

System Updates

If any system updates are needed, while FileMaker Server is offline, you can safely install them. After the updates have completed, restart the machine.

Verifying the Restart

Once the machine has finished restarting, FileMaker Server should automatically start up with all hosted files back online. Verify this by signing into the FileMaker Server Admin Console, navigating to the Databases tab, and confirming that all files have a blue Status indicator.