Administrator’s Guide (Windows)

Technical specifications and optimization A-3
FileMaker Pro Server log file
The following is a list of some of the log file messages you might see
and an expanded explanation. Variables, like the name of the user or file,
are in italics.
Message Explanation
Closing file filename due to a serious error
(error number)
The specified file is closed by FileMaker Pro Server due to an error condition. The file
may need to be recovered in the FileMaker Pro application. See the FileMaker Pro
User’s Guide for information about recovering damaged files.
Could not pause file filename because of
outstanding database locks from guests
FileMaker Pro Server is trying to get exclusive use of the file to pause it for a backup
but can’t because a user is changing the file. You can try the backup later, or close the
file to force the guest(s) to disconnect.
File filename full, compression started When a FileMaker Pro file approaches the 2 GB file size limit or there is no longer
enough free space on the hard disk, FileMaker Pro Server attempts to compress it by
reclaiming unused space in the file. This process is automatic, and this message is
written to the log file when the process begins.
File filename compressed, freeing x blocks The specified file has been successfully compressed, leaving FileMaker Pro Server
enough room to continue safely working with the file. (One block equals 1,024 bytes.)
File filename compressed, but still nearly
full. Only x block(s) free
The specified file was compressed, but there isn’t enough room for FileMaker Pro
Server to continue safely working with the file. The administrator should close the file,
back it up, and take steps to reduce the size of the file and create more room on the hard
disk.
FileMaker Pro Server quitting!
(error number)
FileMaker Pro Server detects a severe error during network use, due to a network
failure or other causes.
FileMaker Pro Server quitting!
Network initialization failed; an
unexpected error occurred
FileMaker Pro Server can’t use any network protocol because of an unexpected error.
FileMaker Pro Server quitting! Network
initialization failed; not enough memory
FileMaker Pro Server can’t use any network protocol due to insufficient memory. See
“What you need” on page 1-4 for RAM requirements.
FileMaker Pro Server quitting! This disk
is full
FileMaker Pro Server detects that the disk volume is full.
FileMaker Pro Server quitting! Network
initialization failed
(error number)
FileMaker Pro Server is unable to start because of missing required software or
hardware. Check the requirements listed in “What you need” on page 1-4 for more
information.
Quit forced; User username forced to close
connection (error number)
These messages indicate that, during a shutdown or disconnect operation, the user didn’t
close the file within the specified time. The user’s connection was then forcibly closed.
TCP/IP network initialization failed; an
unexpected error occurred (error number)
FileMaker Pro Server can’t initialize TCP/IP.
TCP/IP network initialization failed; the
TCP/IP address is already in use or an
address could not be obtained
(error number)
FileMaker Pro Server can’t initialize TCP/IP, because the address specified isn’t
correctly configured or the address isn’t available. Verify the TCP/IP configuration in
the Windows NT Networks control panel. If FileMaker Pro is already running on the
same computer and is set to use TCP/IP, FileMaker Pro Server is prevented from using
the same TCP/IP address. Set FileMaker Pro to use IPX/SPX networking and relaunch
it, quit FileMaker Pro, or run FileMaker Pro Server on a dedicated machine.