To safely restart the FileMaker server, follow these steps.
- Open up your FileMaker Admin Console.
- Stop your FileMaker Server. How to do this depends on which version of FileMaker you’re using; see FileMaker’s help guides for detailed instructions.
- Double check that your FileMaker server has stopped by attempting to log into aACE. If you’re able to log into your aACE solution, then Admin Console is not responding and the server has not stopped; see below for next steps. If you're not able to log into aACE, the FileMaker server has stopped and you can safely proceed to step 4.
- When the server has stopped, restart your machine.
- After the machine has restarted, your FileMaker server will most likely turn on automatically. If this default configuration has been changed, manually turn the FileMaker server back on.
If the Admin Console is not responding, you will have to stop the FileMaker server via the command line.
- Open the command line. In Mac, the default program is Terminal and can be found in Applications > Utilities. In Windows, this is called Command Prompt and can be found under the Windows System heading in the app screen in Windows 8, or in Start > All Programs > Accessories in earlier versions of Windows.
- Type “fmsadmin stop server” and press the Return (Mac) or Enter (Windows) key. You will be prompted for a confirmation; enter “y”. You will then be prompted to enter your username and password; these are the same credentials you used to log into the Admin Console. This will stop the server.
- Proceed to step 4 above.