Guide to Updating Plug-ins

7-20 FileMaker Server Administrator’s Guide
For more information about the error conditions reported in the event
log, see appendix C, “Event log messages and troubleshooting.”
Keeping event data current (Windows)
You might want to configure the Event Viewer to overwrite event
information, because the default setting is to stop recording events
when the application log becomes full. If you have many databases
open with many users accessing them, and if you flush the cache
often, the log could fill up quickly and the information in the Event
Viewer could quickly become out of date.
To overwrite event information when the log is full:
1. Choose one of the following:
1 Windows NT: In the Event Viewer, choose Log menu >
Log Settings.
1 Windows 2000: In the Event Viewer, choose Action menu >
Properties.
2. For Event Log Wrapping, select Overwrite Events as Needed.
3. Click OK.
Tip You might want to increase the Maximum Log Size setting from
the default 512 KB to 4096 KB or more, depending on how much
FileMaker Server activity you anticipate on your server computer.
Viewing activities in the event log (Mac OS)
The Server Event Log (Mac OS 8.6 to 9.1) or Events.log (Mac OS X)
file is created in the FileMaker Server 5.5 folder. You can use any
application capable of opening plain text files or the Mac OS X
console application to view or print it.
Mac OS 8.6 to 9.1: You can have the log file open when
FileMaker Server is running, but you won’t see recent updates in the
file until you close the log file and reopen it. A new log file is created
each time you start FileMaker Server. The log from the previous
session is backed up in the FileMaker Server 5.5 folder and renamed
Server Last Event Log. Therefore, you always have the current log
file and the previous one available for review. To save a specific log
file, use the Finder to rename it before it is overwritten by
FileMaker Server.
Mac OS X: You can have the log file open in the OS X console
application when FileMaker Server is running. Events are logged
continuously, with the most recent log entry at the bottom of the
console application window. Events.log is created when FileMaker
Server starts, only if there is no existing Events.log. Activities are
added to Events.log until it reaches the maximum size, at which point
it is renamed Events-old.log, and a new Events.log is created.
You can set a maximum size for the log file to prevent it from taking
up too much space on your disk. For more information, see “Setting
a size limit for the event log (Mac OS)” on page 6-15.
For more information about the error conditions reported in the event
log, see appendix C, “Event log messages and troubleshooting.”
Recalculating the Today function
in hosted databases
The Today function in FileMaker Pro updates whenever a database
file is opened. If a database file you’re hosting with
FileMaker Server contains fields that use the Today function, you
must close that file and reopen it each day for this function to
recalculate correctly. See the FileMaker Pro 5 User’s Guide for
information about the Today function.