Help
Table Of Contents
- FileMaker Server 9 Help
- About FileMaker Server
- New features in FileMaker Server 9
- Deploying FileMaker Server
- Starting Admin Console
- Hosting databases
- Hosting websites
- Starting and stopping FileMaker Server
- Configuring general settings
- Configuring Database Server settings
- Configuring web publishing settings
- Administering clients
- Administering databases
- Using ODBC and JDBC with FileMaker Server
- Monitoring FileMaker Server
- Managing plug-ins
- Securing your data
- Scheduling administrative tasks
- Troubleshooting
- Checking for updates
- About the license key
- Command line reference
- Glossary
- Registration
- Customer support and Knowledge Base
- Copyright information
Troubleshooting Problems on client computers
F
ILEMAKER SERVER 9 HELP 162
Problems on client computers
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. FileMaker Server 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.
The FileMaker Server name does not appear in the FileMaker Pro Open
Remote File dialog box
• Windows: Verify that the FileMaker Server service is started in the Services (Local) node.
• You may need to specify the host IP address
of the computer running FileMaker Server. In
the Open Remote File dialog box, type: fmnet:/[IP address].
Clients cannot see databases hosted by FileMaker Server
The firewall settings on the FileMaker Server machine may be blocking the display of databases to
clients
. See Ports used by FileMaker Server (page 161) for more information on which ports need to
be unblocked in firewalls.
Clients receive “Communication with the host was interrupted and could not
be re-established” message on client computer
FileMaker Server disconnected a client from a database because the client didn't comply with a
request from FileMaker Server to close a database. Communication between the host and client
may have been disrupted because of a hardware failure (lost network connection) or a software
connection time-out (no response from client for a given period of time). The latter could be
caused by a screen saver or processor-intensive operation.
Clients receive “servername is no longer available or the host capacity has
been exceeded” message on client computer
FileMaker Server has shut down or you reached the maximum allowable connections or clients
on FileMaker Server. Verify that FileMaker Server is running or increase the number of clients
allowed in the Database Server > FileMaker Pro Clients tab.
Clients receive “Host capacity exceeded” message on client computer
You reached the maximum allowable connections or clients on FileMaker Server. Increase the
number of clients allowed in the Database Server > FileMaker Pro Clients tab.
Clients receive “This action cannot be performed because the file is not
modifiable” message on client computer (FileMaker Pro databases hosted by
FileMaker Server on Mac OS)
Clients can’t modify the database file because the database file permissions are incorrectly set. The
operating-system-level group fmsadmin must own the database file and have read and write
access permissions. The Event.log
will report “Opened database [filename] read only”. (If the
database file is not owned by the group fmsadmin, FileMaker Server will not recognize the
database file and there will be no entry in the Event.log.)