Guide to Updating Plug-ins

Table Of Contents
Event log messages and troubleshooting C-5
Troubleshooting
The following table lists some problems you may encounter when
using FileMaker Server.
Tip When FileMaker Server behaves unexpectedly, check the log
file to diagnose the problem. See “Using reported events to track
activities” on page 7-18 (Windows and Mac OS) or “Using reported
events and statistics to track activities” on page 9-13 (Red Hat
Linux) and “FileMaker Server event log messages” on page C-1 for
more information.
Problems installing or starting FileMaker Server
Network problems
Symptom Suggested solution or explanation
You’re unable to install FileMaker Server. Check the hardware and software requirements listed in “What you need” on page 2-1 (Windows), page 3-1
(Mac OS 8.6 to 9.1), page 4-1 (Mac OS X), or page 5-1 (Red Hat Linux) to ensure your equipment and software
are compatible.
Windows, Mac OS X, and Red Hat Linux: Be sure to log in with administrative privileges when checking for
compatibility.
You’re unable to start FileMaker Server. Check the hardware and software requirements listed in “What you need” on page 2-1 (Windows), page 3-1
(Mac OS 8.6 to 9.1), page 4-1 (Mac OS X), page 5-1 (Red Hat Linux) to ensure your equipment and software
are compatible. Also check the Windows Event Viewer, the Server Event Log (Mac OS 8.6 to 9.1) or
events.log (Mac OS X and Red Hat Linux) for a description of why FileMaker Server couldn’t start. For more
information about the Event Viewer, see “Using reported events to track activities” on page 7-18 (Windows
and Mac OS) or “Using reported events and statistics to track activities” on page 9-13 (Red Hat Linux).
Symptom Suggested solution or explanation
A FileMaker Pro guest using IPX can’t find
FileMaker Server databases on the network.
Windows: Verify that IPX networking software is properly installed. Verify that the host and guest are using
the same frame type. Verify that the IPX/SPX network protocol (or both TCP/IP and IPX/SPX) is selected in
the Networking tab of the Properties dialog box. Verify that the 250 simultaneous guest limit has not been
reached.