Administrator’s Guide (Mac OS)

A-6 FileMaker Pro Server Administrator’s Guide
Message Explanation
AppleTalk network initialization failed; an
unexpected error occurred (error number)
FileMaker Pro Server can’t initialize AppleTalk.
AppleTalk network initialization failed;
AppleTalk is not enabled
FileMaker Pro Server detects that AppleTalk isn’t enabled. Be sure that AppleTalk is
enabled in the Chooser.
AppleTalk network initialization failed; not
enough memory
There is insufficient memory to use AppleTalk. See “Mac OS system requirements”
on page 1-1 for RAM requirements.
Closing file filename due to a serious error
(error number)
Written when 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
FileMaker Pro User’s Guide for more 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 compressed, freeing x blocks Written when 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.
Written when 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.
File filename full, compression started When a FileMaker Pro file approaches the 2 GB file size limit, 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.
FileMaker Pro Server quitting!
(AppleTalk, MacIPX, or TCP/IP) network
communication failed (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; AppleTalk is not
enabled, MacIPX version 1.2.1 or greater is
not installed, and Open Transport is
not available.
FileMaker Pro Server detects that AppleTalk isn’t enabled and a compatible version of
MacIPX isn’t installed. Be sure that AppleTalk is enabled in the Chooser; use the
FileMaker Pro Server Installer to install the correct version of MacIPX; and be sure
that Open Transport has been installed correctly (see the Open Transport
documentation for more information).
FileMaker Pro Server quitting! Network
initialization failed; not enough memory
FileMaker Pro Server can’t use any network protocol due to insufficient memory. See
“Mac OS system requirements” on page 1-1 for RAM requirements.
FileMaker Pro Server quitting! This disk
is full
FileMaker Pro Server detects that the startup disk volume is full.
FileMaker Pro Server quitting! Thread
Manager system extension is required
(error number); FileMaker Pro Server
quitting! Network initialization failed
(error number)
Written when 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-1
for more information.
MacIPX network initialization failed; an
unexpected error occurred (error number)
FileMaker Pro Server can’t initialize MacIPX.