Guide to Updating Plug-ins

C-2 FileMaker Server Administrator’s Guide
File filename compressed, freeing x blocks The specified file has been successfully compressed, leaving FileMaker Server enough room to continue
working with the file safely. (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 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 Server is now awake. All schedules will be
resumed.
This message is sent to the log by FileMaker Server when the server computer wakes up from hibernation
(Windows 2000) or system sleep mode (Mac OS). Files that were hosted by FileMaker Server before
hibernation or sleep occurred are now available for guest access once again.
FileMaker Server is going to sleep. The entire cache will be
flushed. All schedules will be suspended.
If the server computer is configured to sleep during periods of inactivity, before doing so the operating system
prompts each open service or application to find out if the service or application can accommodate sleep mode.
If any guests are currently connected to a hosted database, FileMaker Server denies the sleep request and the
server computer does not sleep. If no guests are connected, FileMaker Server writes any unsaved changes to
disk (flushes the cache) and allows the server computer to sleep. During sleep, all scheduled tasks are
suspended and do not run again until the next scheduled time when the server computer is awake.
FileMaker Server quitting! (error number) FileMaker Server detects a severe error during network use, due to a network failure or other causes. Check
network installation, settings, and the system error log (Windows).
FileMaker Server quitting! Network initialization failed; an
unexpected error occurred
FileMaker Server can’t use any network protocol because of an unexpected error. Check network installation,
settings, and the system error log (Windows).
FileMaker Server quitting! Network initialization failed; not
enough memory
FileMaker Server can’t use any network protocol due to insufficient memory. See “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) for
RAM requirements.
FileMaker Server quitting! This disk is full FileMaker Server detects that the disk volume is full. Free some space on the disk and restart
FileMaker Server.
FileMaker Server quitting! Network initialization failed
(error number)
FileMaker Server is unable to start because of missing required software or hardware. See “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) for
more information.
Quit forced; User username forced to close connection
(error number)
During a shutdown or disconnect operation, the named user didn’t close the file within the specified time. The
user’s connection was forcibly closed by FileMaker Server.
Registration with directory service failed. (error number) Registration with the directory service failed because Microsoft Active Directory is not installed on this
computer.
Remote administration has been disabled because the
databases could not be opened (error number)
The system’s storage area for temporary files might be full or set to read-only. Check the temporary storage
area on the server computer and try again.
Message Explanation