FileMaker G0600 - Manual (Page 44)

44 FileMaker Server Getting Started Guide
Deployment assistant does not start after installation
If the Deployment assistant does not start immediately after you run the FileMaker Server installation
program, the most common solutions are:
1
On Mac OS, check whether your browser is configured to prevent files from opening after downloading.
If so, you can start the Deployment assistant by double-clicking admin_console_webstart.jnlp in your
download folder, or double-clicking the FMS 11 Start Page shortcut on the desktop.
1
On Mac OS and Windows, if the Admin Server process does not respond within 60 seconds to the
FileMaker Server installation program, the following message appears:
The FileMaker Server Admin Console Start page is not available.
If you see this message, do the following steps in the order shown:
1
Make sure the Admin Server process is running. On Mac OS, open the Activity Monitor and make sure a
Java process owned by FileMaker Server is running. On Windows, open the Task Manager and make sure
the fmadsminserver.exe process is running. If necessary, you can restart the Admin Server process by
entering the following command in a command prompt (Windows) or the Terminal application (Mac OS):
fmsadmin RESTART ADMINSERVER
1
On Windows, you can stop and the restart the FileMaker Server service in the Administrative Tools >
Services control panel.
1
If your server computer has a firewall, make sure all required ports are open in the firewall. (See
“Before you begin” on page 11.)
1
If your machine is running slowly, shut down any unnecessary applications.
1
Restart your machine. Open a web browser on the master machine and enter
http://localhost:16000
.
Admin Console doesn’t start after deployment on master machine
The most common solutions are:
1
On the Admin Console Start Page, click Click here to start Admin Console.
1
Open a web browser on the master machine and enter http://localhost:16000.
Admin Console Start Page says to install Java when it’s already installed
Internet Explorer may be configured to prevent add-ons from running. Click the Information Bar at the top
of the browser window and allow Internet Explorer to run the Java Web Start ActiveX Control add-on. Java
Web Start technology uses this add-on to detect whether the required version of Java is installed. After you
allow this add-on to run, click Start Admin Console.
Cannot start Admin Console from a remote machine
1
If the master machine has a firewall enabled, then you must open the ports required by FileMaker Server
to communicate with users and administrators. See “Before you begin” on page 25.
1
If you double-click an Admin Console shortcut and Admin Console doesn’t open, check whether the IP
address of the master machine has changed. Each shortcut starts Admin Console for a specific FileMaker
Server deployment. If the IP address of the master machine has changed, you must remove the shortcut
and start Admin Console again. See “Starting Admin Console” on page 49.